Question - Script efficiency vs. readability

[Drallin]

Should I care about efficiency vs. readability in macros?

Example... one could do:

/if (${Me.Casting.ID} && !${Me.Class.Name.Equal[Bard]} ) {

or somewhere in initialization phase set a boolean based on class and instead do something like

/if (${Me.Casting.ID} && !${ignoreCastingCheck} ) {

Does stuff like that even matter? Is checking bools vs. a string compare actually faster in whatever language the macros are using or is it all string compares under the hood?


(Yeah at some point I'll probably switch to using someone's fully set up scripts... but making my own stuff work is at least 13.7% of the fun at this point.)

 

[Sic]

Should I care about efficiency vs. readability in macros?

Example... one could do:



or somewhere in initialization phase set a boolean based on class and instead do something like



Does stuff like that even matter? Is checking bools vs. a string compare actually faster in whatever language the macros are using or is it all string compares under the hood?


(Yeah at some point I'll probably switch to using someone's fully set up scripts... but making my own stuff work is at least 13.7% of the fun at this point.)

if you really care about either of those things, readability and efficiency, you'd move over to Lua instead of macro language

Lua is a #real fully formed language with a bunch of goodies available for vs-code

MQ Vs Code Lua Defs Extension
Convert macro stuff to lua stuff?

 

[boxbuddy]

I'm not sure exactly how the mq2 scripting language is written, but theoretically, it would be slightly more efficient to store it as a Boolean, since you wouldn't have to make a game-check call every time.

With that said, you will NEVER notice the difference.