| Blockland Forums > Suggestions & Requests |
| Improved Event System |
| << < (4/7) > >> |
| Crispy_:
--- Quote from: Mr.Noßody on February 28, 2014, 10:30:24 PM ---"Onplayertouch" "ifplayertouch" "whileplayertouch" ...what would "elseplayertouch" do? As a sentence, it doesn't even make grammatical sense... --- End quote --- Of course, it would not allow you to select some things. Like On Player Touch would be pretty much the same thing as If Player Touch, so player touch would not be listed when you select 'if', etc. |
| blueblur121:
Else would go directly to an output event. If would check for a variable to be true or false (variables should be added to this new system as well). While would be constantly activated every few ticks as long as the input is being activated. And then it would go back after the input isn't being activated. EXAMPLES: text box = [] dropdown list = <> IF/ELSE: --- Code: ---<on> <playerTouch> <self> <IF/ELSE_EVENT> <if> <BL_ID> <==> [1] <client> <centerPrint> [Hello, Badspot!] <else if> <BL_ID> <==> [27046] <client> <centerPrint> [Hello, Blueblur!] <else> <client> [Unrecognized BL ID.] <end> --- End code --- This checks the BL ID of the person touching the brick and gives them a specific message based on who they are. WHILE: --- Code: ---<while> <playerTouch> <self> <setColor> <blue> --- End code --- This makes it so that if a player touches the brick it turns blue. When the player stops touching the brick it turns back to how it was. If this new system was in place then a ton more things could be possible with events. Such as a capture point TDM sort of minigame. --- Code: ---<while> <playerTouch> <self> <IF/ELSE_EVENT> <if> <team> <==> [red] <self> <setColor> <red> <if> <team> <==> [red] <minigame> <chatMessageAll> [Red team has taken base 1!] <if> <team> <==> [red] <player> <addScore> [1] <if> <team> <==> [red] <client> <bottomPrint> [Holding base: +1 point] <if> <team> <==> [blue] <self> <setColor> <blue> <if> <team> <==> [blue] <minigame> <chatMessageAll> [Blue team has taken base 1!] <if> <team> <==> [blue] <player> <addScore> [1] <if> <team> <==> [blue] <client> <bottomPrint> [Holding base: +1 point] --- End code --- While is activated every few ticks unless the player stops touching the brick. |
| cocoaTHEhotdog:
This just seems like it's to confuse you. |
| Peejster:
--- Quote from: Crispy_ on February 28, 2014, 10:55:34 PM ---Of course, it would not allow you to select some things. Like On Player Touch would be pretty much the same thing as If Player Touch, so player touch would not be listed when you select 'if', etc. --- End quote --- If you want to really differentiate between "on" and "if", have "on" apply only the first time it happens, but have "if" activate continuously. you're right that was stupid |
| Threule:
--- Quote from: cocoaTHEhotdog on March 02, 2014, 11:14:57 AM ---This just seems like it's to confuse you. --- End quote --- Well this leads to easier non-scripting events |
| Navigation |
| Message Index |
| Next page |
| Previous page |