We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Module Information
Describe the bug All users have sysop level access in the game "sys" commands. E.g., SYS GOTO, SYS UPDATE, SYS BECOME, etc...
To Reproduce Steps to reproduce the behavior:
Expected behavior Only users with "sysop" keys or role should have the ability to run sysop commands.
Screenshots N/A
Software Information:
The text was updated successfully, but these errors were encountered:
Currently both haskey() and hasmkey() Ordinals return true for every key, regardless if the user has it.
haskey()
hasmkey()
true
I'm working on a Branch right now which sets default keys for new users and properly evaluates the keys assigned to a user.
PR pending.
Sorry, something went wrong.
Excellent. As soon as this is implemented, I'm ready to replace by BBS. :)
BTW: incredible work!
I'm happy to test.
enusbaum
Successfully merging a pull request may close this issue.
Module Information
Describe the bug
All users have sysop level access in the game "sys" commands. E.g., SYS GOTO, SYS UPDATE, SYS BECOME, etc...
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Only users with "sysop" keys or role should have the ability to run sysop commands.
Screenshots
N/A
Software Information:
The text was updated successfully, but these errors were encountered: