I keep seeing people make add-ons that are room or channel specific. People use several different methods to track channel specific add-ons whether it be tokens, hashes, ini files, or some other crazy method. In my quest to minimalize code spam i use an alias to handle all of that for me. Are there any downfalls in using something like this? (It sure makes code a lot cleaner).



Using this, each channel add-on becomes



which is much prettier than the alternative.

That's a pretty cool idea.

The only thing I have to say about that is using an alias, custom identifier, doubles the time it takes to process the script. Also $iif is slower than using a normal if statement.

That is why I didn't make a bunch of aliases for these things and the reason you don't see $iif used in SoulFly unless it is required.

The performance difference is negligible if you seperate each instance, but when you add up all the instances in the script it makes a difference. That is one of the reasons SoulFly is faster and more stable than other connections even though it seems larger.

Thanks for posting.

On an event command or high usage area, i could definitely relate to the performance issue. However, on a submenu pop-up, i will take the less code over performance. There will always be a fine line between efficiency and speed.

Good info on the slow iif's.