[BUG] Update the building commands to have less 'common' names
See original GitHub issueDescribe the bugs
After the @
became optional, there are builder commands like open
and lock
that regularly collide with commands that users may want to implement themselves (open/locking doors).
To Reproduce
- The
simpledoor
contrib uses anopen
command that collides with the builderopen
command.
Expected behavior
While we don’t want to go back to @
-prefixes, we can change the default builder commands to have less ‘common’ names.
Additional context
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Unable to install xcode command line developer tools
This prompts me to install the command line developer tools. When I click install I get the following error. Can't install the software...
Read more >go command - cmd/go - Go Packages
Go is a tool for managing Go source code. Usage: go <command> [arguments]. The commands are: bug start a bug report build compile...
Read more >Troubleshoot pipeline runs - Azure DevOps - Microsoft Learn
Learn how to troubleshoot pipeline runs in Azure Pipelines and Team Foundation Server.
Read more >Tasks in Visual Studio Code
This shows you a picker with the available build tasks. ... You can run your task through Quick Open (Ctrl+P) by typing 'task',...
Read more >Frequently Asked Questions — Ansible Documentation
Frequently Asked Questions . Here are some commonly asked questions and their answers. Where did all the modules go? . In...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for the discussions and suggestions in this issue, @fariparedes and @InspectorCaracal! I have now (in https://github.com/evennia/evennia/commit/4f57370bc98383ae1d379a89a813f3746060387f) extended the way the prefix-ignore works in Evennia 1.0. The system will transparently use the non-prefixed command-name where possible, but fall back to separating them when there are duplicates. In practice it means that the building open command is now again
@open
, but you can still use it asopen
and help files will also show it asopen
.Only if you actively add a new
open
command will the system separate the two (and the help will show both commands etc). So this basically allows the default command to fall back to a @-form only when it’s actually needed to differentiate with another command.You can read more about the feature here: https://www.evennia.com/docs/1.0-dev/Components/Commands.html#command-prefixes
One can of course still just replace & rename the default if one prefers. 😁
All that said:
If you want suggestions for less common-English command names, you’ll probably want to get away from the more IF roots of MUD commands entirely and make the command names more explicitly connected to their mechanical function. For instance, instead of
dig
, something likemkroom
ormakeroom
,open
could bemkexit
,lock
could besetlock
orlockstring
,search
could bedbsearch
, etc.edit: The
setlock
example already has precedence in thedesc
versussetdesc
command structure. (Although personally I feel likedesc
andsetdesc
are backwards -desc
should be the player version, whilesetdesc
should be the builder version.)