Me.PctAAExp

Gnits · Post by **Gnits** » Sun Jul 10, 2005 12:53 pm

i just noticed on my HUD, that the reference to ${Me.PctAAExp} reports 0 and ${Me.PctExp} returns a proper value.

Is this a bug or did the reference change?

fice · Post by **fice** » Sun Jul 10, 2005 3:17 pm

either not using latest zip or you're testing on a char with no aa exp cause it works for me

Teh_Hidden · Post by **Teh_Hidden** » Mon Jul 11, 2005 11:18 pm

When you have something like that which should be working, the first test to try is to just exchange ${Me.PctExp} for ${Me.PctAAExp}.

If it doesn't work, then your other code is broke. If it does, then the ${Me.PctAAExp} is, for some reason. Trying the same in reverse (PctAA for PctExp) can be a different test that gives good results, as well.

CodeCaster · Post by **CodeCaster** » Tue Aug 09, 2005 9:01 pm

It's broken for me as well. Swapped for ${Me.PctExp} to make sure code was good and it is. Even did a /echo ${Me.PctAAExp} in the console and it returns zero every time even tho I have about 21% aaxp.

fearless · Post by **fearless** » Tue Aug 09, 2005 9:28 pm

Code: Select all

/echo ${Me.PctAAExp}
[MQ2] 0.30

CodeCaster · Post by **CodeCaster** » Tue Aug 09, 2005 10:09 pm

Code: Select all

/echo ${Me.PctAAExp}
[MQ2] 0.00

I just changed the <EQType>9999</EQType> to type 27 in my hud... At least it works, but it's not displayed as a float which kinda sucks for accuracy.

I am using WinEQ... Not sure if that would bork it up for some reason, but I am fairly sure it didn't work in the native client window either. I am using latest release of MQ, but this has been broken for the last 2-3 releases at least.

gimp · Post by **gimp** » Wed Aug 10, 2005 3:41 am

In some release i think this variable was broken because of a incorrect offset, but it certainly isn't with latest release. I used to compile with VC6 and at times i got perfectly loading & "working" versions of MQ, but some things wouldn't just work. Switching to VS 2003, i never had such problems again. I believe VC6 is a shitty compiler.
Anyway, what are you using to compile with?

CodeCaster · Post by **CodeCaster** » Thu Aug 11, 2005 1:35 am

I'm using .NET 2003...

gimp · Post by **gimp** » Thu Aug 11, 2005 4:44 am

Okay, do a proper compile and you won't have this problem.

CodeCaster · Post by **CodeCaster** » Thu Aug 11, 2005 8:13 pm

"Proper" compile complete. Problem persists. Interesting that I am not the only one having this problem...

TheUnholy · Post by **TheUnholy** » Sun Aug 14, 2005 2:09 am

CodeCaster wrote:"Proper" compile complete. Problem persists. Interesting that I am not the only one having this problem...

Should tell you something. PEBKAC