Problem - String TLO removed? 12/10/2018

[mxdog]

I have been off EQ for a couple months sick just got back today and a lot my downshits and holyshits are broke as of the 12/7 update.

Posts I've read around 2005 say String TLO was removed BUT I've been using these same ones for a long time i.e. years?
here is one example on my mage:

downshit1=/if (!${Me.Moving} && !${Me.Invis} && ${String[${Me.CombatState}].NotEqual[COMBAT]} && ${Me.AltAbilityReady[1169]} && !${Me.Buff[Rhyolitic Bodyguard].ID}) /alt act 1169

the String above is what kicks off the message "due to misuse String TLO was removed ..bleah bleah..."

So a double question here why was TLO String removed recently and if it ain't coming back how do I get a string value for conditions like the above i.e evaluate to true/false whithout having to waste time on targeting?

that String Function/TLO is kind of a staple in my holy/down catalog so very much a pain in the ass to have to change dozens and dozens of those on lord knows how many characters.

I don't compile Mq2 myself just use redguides to update (or could add StringTLO back into the cpp) ...so whats up guys ?

 

[eqmule]

Just use ${Me.CombatState.NotEqual[COMBAT]}

There is no reason at all to first convert that to a string...
And the example is a perfect example for why string isn’t needed to be used in that way.

But I’ll answer your question, it’s removed in MQ2 core and usually rg adds it back, the fact that it’s gone now is either just an oversight most likely, or maybe they decided that it’s easier to just leave it disabled, no idea. All I know it’s not needed anymore and if it’s working in the rg compile it’s just for backwards compatibility reasons.

What I can say for sure though, is that I’m 100% certain it will break again even if they add it back today because, the tlo is in a core file which changes a lot.
So u are much better of going forward and in the long run just biting the bullet and make the changes.

 

[mxdog]

Just use ${Me.CombatState.NotEqual[COMBAT]}

There is no reason at all to first convert that to a string...
And the example is a perfect example for why string isn’t needed to be used in that way.

But I’ll answer your question, it’s removed in MQ2 core and usually rg adds it back, the fact that it’s gone now is either just an oversight most likely, or maybe they decided that it’s easier to just leave it disabled, no idea. All I know it’s not needed anymore and if it’s working in the rg compile it’s just for backwards compatibility reasons.

What I can say for sure though, is that I’m 100% certain it will break again even if they add it back today because, the tlo is in a core file which changes a lot.
So u are much better off going forward and in the long run just biting the bullet and make the changes.

Thanks for the fast reply ....

the reason i went that route ....I was getting a "bleah bleah does not evaluate to a number" or something along those lines I must have had a error in the equation ..your solution seems to work fine ..

 

[mxdog]

Now i see another one i had problems with ..checking if i had a pet up

${String[${Me.Pet}].NotEqual[NO PET]}

that is probably where i started using the String TLO from when i got a non-numeric or non-member error

 

[eqmule]

Just use !${Me.Pet.ID} it’s much much faster anyway than first converting to a string

Or if u want to be pro: !${Pet.ID}

 

[mxdog]

Thanks again ..that works !
${Bool[${Me.Pet.ID}]} gives me true/false if pet is up/not up

as an aside if you read this again ..game is crashing if i unload mq2 and then refresh injections ( never has before) ..will watch it and bug it if it keeps up since we getting new expansion tomorrow ? i will wait on it