IfPlayerDead?

[Badspot]

All of these hack events for variables and logic completely break the grammar of the events and make it impossible to understand.  All of the default events read like this:

Hi I'm a brick, when X happens, I'm going to wait X milliseconds, then find target X and do X to it. 

Anything that doesn't read like that is forgeted up. 

[Ad Bot]

[bobblehat]

All of these hack events for variables and logic completely break the grammar of the events and make it impossible to understand.  All of the default events read like this:Anything that doesn't read like that is forgeted up. 

Yes

[.::Taboo::.]

Yes

Olol, suck-up.

Through other add-ons, it's possible to make a kill message, for example.

Code: [Select]

0 | X | 0 | onPlayer Touch| self   | fireRelay   |                      |
 1 | X | 0 | onRelay       | self   | ifPlayerID  | doSub                |
 3 | X | 0 | onsub         | self   | sub         |                      |
 4 | 0 | 0 | onPlayerDeath | client | centerPrint | You have been killed!|
 5 | 0 | 0 | onRelay       | self   | fireRelay   |                      |
These events could be put into say, a player spawn, so they are immediately ready.

[Chrono]

All of these hack events for variables and logic completely break the grammar of the events and make it impossible to understand.  All of the default events read like this:

Hi I'm a brick, when X happens, I'm going to wait X milliseconds, then find target X and do X to it.

Anything that doesn't read like that is forgeted up.

The main reason I do not support this mod, and even my own variables mod.
Another reason is the fact that variables can be abused.
I pretty well gave the mod to Destiny so he can forget it up rather than I. I only contributed to V1-V2 of the mod.

[Destiny/Zack0Wack0]

Eh version 5 is alot better. It gets rid of all those millions of "ifBlah" clogging up the events list. The new way they work does make more grammatical/logical sense.
The current variable event system:

Hi I'm a brick, when X happens, I'm going to wait X milliseconds, and trigger variabletrue or variablefalse inputs regarding values that have absolutely nothing to do with me.

The new way:

Hi I'm a brick, when X happens, I'm going to wait X milliseconds, and trigger variabletrue or variablefalse regarding whether this value is logic to that value.