But the keywords would be all lowercase :P
1st question is why, what's wrong with the current system. And in my opinion, that would add alot of directives to the mix, it would just cause more confusion and less flexibility. Also, trigger is meant for inputs, it should not be used for keywords, that would exclude the possibility of having those keywods as inputs.
What OmicroN said and would it be logical to have things like "tick", "chat", etc. as keywords in the trigger directive in E2, instead of calling functions to make the expression execute?
Hey, curious to see if you are aware that when you Adv Dupe a contraption that has materials/colors set by using E:setColor() and E:setMaterial() the color/material will not save.
Do you think you could commit http://www.wiremod.com/forum/wiremod...and-input.html ?
Here a post I made about a function I need in E2 http://www.wiremod.com/forum/ideas-s...-function.html
Why don't you ever hang out in IRC? #wiremod @ gamesurge
Hi, would it be possible to talk with you ? About that : http://www.wiremod.com/forum/contrap...rain-ever.html, if yes, I hope you add my steam id : toncompte122. thanks !
Would it be possible to have an @Constants at the start of an E2, so that values used many times could be easily changed, or values intended to be calibrated could be easily identified? The way I would see this working is the E2 parser/compiler would simply inline the constant before the expression is sent to the server. This would be awesome because then you could have constants that don't take any ops!
Both I and Tomy has replied to that thread with our thoughts and reasons.
Wire Sofaking
Wire Dev - Lazy