Trigger Events with commands!
If you say /eventcmd [CommandName], the event onCmd gets triggered on all bricks.
If you don't like this command, open up RTB preferences and change the name.
(For the 'advanced' peeps, this requires use of eval function and some other stuff. It does several checks to prevent overwriting of other functions and removes the old function before creating the new. 100% safe.)To prevent lag while looping through all bricks to trigger the event, bricks are added to a list when the event is added and removed when the event is removed.
Then, you can choose
onCmd - Self - ifCmd [CmName] [Restriction] [IDs for restrict] [Which events to trigger]
to make different stuff happen with different commands.
You have the following restrictions:
Unrestricted (Everyone)
Same Minigame
Only Me
BL_ID Allow
BL_ID Deny
No Trust
Build Trust
Full Trust
DistanceifCmd triggers onCmdCalled if the command is the same as what you chose...
And onCmdRestricted if the restriction fails.
Ah I fail to explain this. Look at the picture.
Introducing in V2.5:
Additional parameters.
Instead of /ec [Command]
You can now also say
/ec [Command] [Param] [Param] [Param] [Param] [Param].
Those parameters get saved to client variables which you can access with VCE_ifValue.
They are
<var:cl:ceparam1> | First parameter
<var:cl:ceparam2> | Next parameter
<var:cl:ceparam3> | Next parameter
<var:cl:ceparam4> | Next parameter
<var:cl:ceparam5> | Last paramter
You can now make awesome things like shops with this!
Example of use:
Poll