milkmanjack/Anam — Issue #1: Commands need to be revamped -- the current setup is disgusting.
Author: milkmanjack
Created: 2012-01-30 11:09:29+00:00
State: open
Labels: feature

{Anam / src / struct / commands / get.dm} demonstrates the problem with this structure. Errors are commands, which is a huge problem for querying information as a user. Not only that, rules need to be ordered based on complexity, to make sure more intricate rules are handled first. This is because if we attempt to evaluate the rule "'get'", any extra arguments after 'get' are considered inconsequential, since we have our word match, but if we have another rule, let's say "'get'; obj in room", it will never get to it if it's not set to be handled first.

Another weird thing is that, if I want to add an error for when, say, you put in the wrong word, or the object you're searching for isn't found, I have to do something like "'get'; word", which has to be parsed AFTER "'get'; obj in room". to ensure that object isn't actually in the room. Then I can say "there is no item like '[word'[ here."

It's quite... tedious, I guess.

Need to come up with a game plan for a new command system design.