Poll

Want?

/Yes
8 (80%)
/No
2 (20%)

Total Members Voted: 10

Author Topic: More Flexible Command Events  (Read 1151 times)

Anyone remember Prompt events?  Command Events?

I just want something simple so that you don't have to type /word yes or /word no.  Just an event that takes /yes and /no as inputs with onPlayerAccept, onPlayerDecline and onPlayerVote.

Thanks.
« Last Edit: April 20, 2014, 11:14:36 PM by SWAT One »

How about onCommandCalled and then a parameter so that people could make their own event-activating commands.

How bout somebody just fix the Prompt Events?
They worked fine and /commands suck.

Ideally that would be better, but there's also stuff like OnCommandCalled >> Self >> ifCommand "ClearSpamBricks" "1 2"
OnCommandTrue >> Self >> VCEmodVariable Client "earbleed" Set "1"
OnCommandTrue >> Self >> fireRelay
OnRelay >> Self >> fireRelay
OnRelay >> Self >> VCEifValue "<var:cl:earbleed>" == "1" "5 5"
onVariableTrue >> Client >> "Spam my stuff here."

But then again, /Cancelallevents

and /commands suck.
Why do you have this crusade against any add-on that involves /commands?




http://forum.blockland.us/index.php?topic=202440.75

Download links to RTB, so its busted.

It can be found here.  Just search "Command" and its the 5th result on the page.

Heh, i actually made those command events. I was working on a new version where you could bind a unique command (like /yes or /no or /doadminstuff) to a specific brick but I never got it done because I could not decide how to do that in a user friendly way. Ideas?

Download links to RTB, so its busted.

It can be found here.  Just search "Command" and its the 5th result on the page.
I have that.  I addressed that issue in the OP.  This mod requires a word for all commands triggered by a customizable root word.

For instance, I usually set my command name to "do" so that it remains fairly neutral.  With admin commands, such as joining a Server Maintenance team, I would say "/do sm join".  For granting additional SM tools, I might say "/do sm granttools".  But suppose I need in-game events like buying a spear, "/do shop buy spear".  There are so many types of things you can do, all controlled by the base, "/do".

This is unnecessary and annoying, and there should be a better way where you don't have to do that.

Read what I said above

How is it handled?

(%client, %command, %cmdname, %param1, %param2, etc...)?

Can commands be registered safely when sending events, and unregistered when is is canceled or removed, and is no longer present?

I can dynamically create those commands and link them to bricks, but why and when that should happen is what i ask you ._.

I'm afraid I don't know what you're asking.  Are you asking when the commands should be created, or for what purpose the custom commands would serve?