Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Generalize names of default permission levels #1175

Closed
Griatch opened this issue Jan 24, 2017 · 1 comment
Closed

Feature Request: Generalize names of default permission levels #1175

Griatch opened this issue Jan 24, 2017 · 1 comment
Labels
devel-implemented Already finished, usually in a branch not yet merged. feature-request A suggestion for new functionality.

Comments

@Griatch
Copy link
Member

Griatch commented Jan 24, 2017

Description of requested feature:

Rename the default permission levels to names that better describe their function in the context of Evennia. The current permission levels are:

  • Immortals
  • Wizards
  • Builders
  • Player Helpers
  • Players

The suggested new default permission hierarchy would be:

  • Developers
  • Admins
  • Builders
  • Helpers
  • Players

Reasons for adding feature:

The Immortals/Wizard levels are highly steeped in MUD history but just what they do is not obvious to someone from outside Evennia. For example, "Wizard" is the highest-level permission for many game servers and Immortals/Wizards are used interchangeably for others. In (default) Evennia, the Immortals are those with server control and Python access (Devs) while Wizards can kick people and manage the user base (Admins). the new names reflect this more naturally. Changing Player Helpers to just Helpers also makes this tier more generic as a mid-point between Players and a full-on Builder.

Extra information

This change requires data migrations and belongs in a dev branch leading up to Evennia 0.7.

@Griatch Griatch added the feature-request A suggestion for new functionality. label Jan 24, 2017
@Griatch Griatch added this to TODO in Evennia 0.7 Feb 10, 2017
@Griatch Griatch added the devel label Feb 10, 2017
@Griatch Griatch moved this from TODO to In progress on devel branch in Evennia 0.7 Feb 18, 2017
@Griatch Griatch moved this from In progress on devel branch to Done on devel branch in Evennia 0.7 Feb 18, 2017
@Griatch Griatch added the devel-implemented Already finished, usually in a branch not yet merged. label Feb 19, 2017
@Griatch Griatch moved this from Todo to In progress in API expansion milestone Jul 21, 2017
@Griatch
Copy link
Member Author

Griatch commented Sep 20, 2017

Closed with the merger of devel branch.

@Griatch Griatch closed this as completed Sep 20, 2017
@Griatch Griatch moved this from In progress to Finished in API expansion milestone Sep 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devel-implemented Already finished, usually in a branch not yet merged. feature-request A suggestion for new functionality.
Projects
No open projects
Evennia 0.7
Done on devel branch
Development

No branches or pull requests

1 participant