MacroQuest64

moved to help forum

so i dont get banned from boards

Not misuse as in hacking.

misuse as in the syntax where 'sting' was used was incorrect.

I get the same thing.

#error: you dont have the spell 0 or AA isnt ready!
Due to complete misuse of the String Top-Level object, it has been removed

Fix your macro's.

MoMom wrote:#error: you dont have the spell 0 or AA isnt ready!
Due to complete misuse of the String Top-Level object, it has been removed

Are two different problems. The first is problem in the CHARINFO structure affecting AAs and other things. My guess is this will be in a patched .zip sometime soon.

The second is the 'string' TLO problem. You need to fix your macros to not use 'string'.

Monster

First one fixed, will fix 2nd one later. :)

"Due to complete misuse of the String Top-Level Object, it has been removed"

I am getting this message on all three of the macros I use now. I have changed nothing in the macros and I was using them right before the last patch.

Clueless wrote:"Due to complete misuse of the String Top-Level Object, it has been removed"

I am getting this message on all three of the macros I use now. I have changed nothing in the macros and I was using them right before the last patch.

Fix your macro's.

I would love to. Please let me know what was changed and I will update my code.

I understand that you assume we are all programmers and you look with distain at anyone here that doesn't understand this code as well as you do.

Keep in mind we all have our areas of specialization and I look upon the programmers I work with in the same distain when they don't know how to program a layer 3 6513 with integrated FWSM and IDSM2 with 23 fully fire walled and dynamically routed VLANs spanning 40 sites with over 6000 devices.

Haha, they even think unmanaged Gb/s switches from DLink are faster then the managed 100Mb/s switches from Cisco are. Kind of like all those Ford Pintos that came with speedometers that went up to 140MPH. Dumbasses! (Yes, this was sarcasm)

In the time it took you to post your repetitive, degrading and sarcastic remark you could have just posted the correction to be made in the macro’s to fix this, if you are all that good at this.

Have a nice day and I hope life treats you as well as you treat it.

monster69 wrote:

MoMom wrote:#error: you dont have the spell 0 or AA isnt ready!
Due to complete misuse of the String Top-Level object, it has been removed

Are two different problems. The first is problem in the CHARINFO structure affecting AAs and other things. My guess is this will be in a patched .zip sometime soon.

The second is the 'string' TLO problem. You need to fix your macros to not use 'string'.

Monster

loadingpleasewait wrote:why not change it to use the string .Name?

example..
Change

Code: Select all

 /if (${String[${Me.Gem[6]}].NotEqual["${Yaulp}"]}) { 

to

Code: Select all

 /if (${Me.Gem[6].Name.NotEqual["${Yaulp}"]}) { 

People are making way to big of a deal out of this change..

My understanding of this at this point in time from reading various threads is if I replace all "${String[" with nothing the errors I am seeing will be corrected?

Kind of like the group reference a while back?

Or is this fix in reference to the specific macro Loadingpleasewait is posting in?

Clueless wrote:I would love to. Please let me know what was changed and I will update my code.

I understand that you assume we are all programmers and you look with distain at anyone here that doesn't understand this code as well as you do.

Keep in mind we all have our areas of specialization and I look upon the programmers I work with in the same distain when they don't know how to program a layer 3 6513 with integrated FWSM and IDSM2 with 23 fully fire walled and dynamically routed VLANs spanning 40 sites with over 6000 devices.

Haha, they even think unmanaged Gb/s switches from DLink are faster then the managed 100Mb/s switches from Cisco are. Kind of like all those Ford Pintos that came with speedometers that went up to 140MPH. Dumbasses! (Yes, this was sarcasm)

In the time it took you to post your repetitive, degrading and sarcastic remark you could have just posted the correction to be made in the macro’s to fix this, if you are all that good at this.

Have a nice day and I hope life treats you as well as you treat it.

Clueless, please understand me when I say that you gave us an error message but we don't know what macro it came from or even an example of the code that it came from. If you would read through several of the other posts around, you would see that many people are having the same issues as you because of a change in the source. Some macros have been updated, some have not. If you are not able to fix it yourself, wait for somebody else to do so. Don't start whining because you feel I took a high and mighty approach. Fix it yourself or wait for somebody to do it. It is that simple.

I hope this does not get me banned, I have the same problem and have been in numerous screens with lots of help.

and a member in another group told me what was below

I am using genbot and this was the help that was given to me
as it was told to me

a user wrote:

Basically they removed the ability to do ${String[something]}

I don't know what part of genbot you posted, but you need to go into all the genbot .inc's and .mac's and change anything that says ${String[${var}]} to just ${var}. It's really simple, but if it's too much for you wait for the code to be updated.

If you see no more post from me you know why..
the BIG B word

noob
tagger