- Joined
- Jan 30, 2013
- Messages
- 12,759
Yeah, a generic title gg.
Okay, direct to case with all seriousness.
I have been observing, within these 2 years I have seen modifying Conditional Blocks (setting the allowed targets) in GUI Spells have been very ridiculously annoying, especially those with LONG GUI Codes. Ones that run on Init are the main ones, having condition blocks spread over the main spell triggers (cast and loop) causing some difficulty to modify them.
So, Hivers, especially GUI Coders, I want your opinion.
Should we keep it or we add a new rule :
The Configuration Trigger must be executed from the spell cast/loop trigger as necessity, with pointers such as units being available.
Okay, direct to case with all seriousness.
I have been observing, within these 2 years I have seen modifying Conditional Blocks (setting the allowed targets) in GUI Spells have been very ridiculously annoying, especially those with LONG GUI Codes. Ones that run on Init are the main ones, having condition blocks spread over the main spell triggers (cast and loop) causing some difficulty to modify them.
So, Hivers, especially GUI Coders, I want your opinion.
Should we keep it or we add a new rule :
The Configuration Trigger must be executed from the spell cast/loop trigger as necessity, with pointers such as units being available.