Blockland Forums > Help
VCE help
Gsterman:
--- Quote from: Kill All on August 15, 2012, 04:46:50 PM ---OnActivate-player-VCEModVariable-VariableName-Add-1
--- End quote ---
Thats what I did.
But I want it to that one time for each player, then stop.
K9 Kid:
cant you
0-onactivate>player>vcemodvariable>variablename>add>1
1-onactivate>self>seteventenabled>0 (disabled)
or am i missing something
Kill All:
--- Quote from: Gsterman on August 15, 2012, 05:02:33 PM ---Thats what I did.
But I want it to that one time for each player, then stop.
--- End quote ---
Then try this
--- Quote from: Kill All on August 15, 2012, 04:46:50 PM ---OnActivate-player-VCEModVariable-VariableName-Set-1
--- End quote ---
Gen. Hothauser:
If you want us to help to the fullest, then tell us what you are making.
Also, if you want this done right, to what you have described, look at the below.
[x] [0] [0] [onactivate] [client] [VCE_Ifvariable] [count] [==] [1] [1 4]
[x] [1] [0] [onvariablefalse] [client] [VCE_Modvariable] [count] [set] [1]
[x] [2] [0] [onvariablefalse] [self] [VCE_Savevariable] [client] [count]
[x] [3] [0] [onvariablefalse] [client] [centerprint] [You clicked this brick and have a thing] [3]
[x] [4] [0] [onvariabletrue] [client] [centerprint] [You already clicked this brick and have a thing] [3]
Use client for variables where you don't want them to be lost when someone dies. Use savevariable for variables that need to be recalled from earlier sessions. Always include center/bottom/chat print events so people know something happened, this way they don't spam up the brick. This was not the example i used for explaining how a duckhunt can work, it is simplified with all additions that make a duckhunt, a duckhunt, thrown out.