I know he is. SortaCore was correct for build 17, and in build 18 the interactive/passive stuff is removed altogether.
Printable View
I know he is. SortaCore was correct for build 17, and in build 18 the interactive/passive stuff is removed altogether.
Oh, OK, I guess I misunderstood all of this. Sorry.
Okay, a few questions (isn't it always the case when you get answers? =p)
1. What sort of situations would arise where you'd want to intercept and block these conditions? Like what would be crucial enough to want to sacrifice speed? For example, what would you do with "on channel join request" that would require it to be interactive?
2. If the interactive/passive stuff is removed altogether... what is taking its place? Is every condition passive now? or interactive? What does that mean for future builds?
3. Right now I'm using build 17... because I tend to try to use the most stable builds... Should I be using 18 anyway? I mean eventually I'll have to use it, but I'm wondering this because I'm just starting out with Lacewing, and I don't want to run into broken/experimental stuff just yet and not even realize it's broken/expiremental. I want to be able to learn from the most stable build so that I don't get any more confused than I already am. So... am I just being too safe or should I just go with build 18?
Also, thanks very much for the help and thanks for this extension Jamie! I appreciate it.
3. Stay with build 17. 18 is alpha. You will always run into broken things.
Marv