commands in config.txt do not catch and cancel a command as the first arguement (needs verification) about commandhelper HOT 5 CLOSED

Comment by PseudoKnight

Cannot replicate. More details? Like, why would you expect the first argument to be run at all as a command? It would never do that unless you're telling it to.

from commandhelper.

Comment by LadyCailin

I'm going to go ahead and close this, since it can't be duplicated. Provide more code and re-open if you're still having problems with it.

from commandhelper.

Comment by VergilPrime

"why would you expect the first argument to be run at all as a command? It would never do that unless you're telling it to."
No that's exactly what I am saying. I didn't tell it to do that, and I don't WANT it to do that, but it's doing that.

from commandhelper.

Comment by VergilPrime

http://paste.thezomg.com/9281/42873136/

I tested with '*:/helpy $ = msg($)' and typing '/help /spawn' and it didn't cause a problem, but in the code I just posted above, running '/help /spawn' both displays info on /spawn AND teleports me to spawn.

from commandhelper.

Comment by LadyCailin

The problem is the assign at the top. It returns whatever the argument is (in this case /home) and so it runs it as though it were a simple alias. I unfortunately don't have a perfect solution for this, since this design is deeply ingrained in the system, until I get support for ";". In the meantime, wrap all that code in g(), which is a special undocumented function, which should solve this problem in the meantime.

from commandhelper.