Merlin
Grandfathered
same case for mineThat makes complete sense. Alot of my OG twinks have more XP than I remember them having (though none are at that 1 point away spot)
same case for mineThat makes complete sense. Alot of my OG twinks have more XP than I remember them having (though none are at that 1 point away spot)
There was a Guy in cata who used this exploit macro wich ended Up with a gm stalked him tru full bg, at the end of scoreboard he levled 61. He had His XP blocked.
Not sure IF gms work like this today but of they get triggered it could possibly happen
[doublepost=1556881609,1556881456][/doublepost]So dont risk any Twink wich is 90 procent in XP bar.
most trash bags dont readily admit to exploiting. good for you. is this for transparency or are you on the autism scale?this happened a few days ago when i was farming for belt of the fang with a 120 so that it could be enchanted with bfa belt engineering
as i was exiting the dungeon my 120 friend was outside waiting for me so he could reset but instead of me exiting i was ported in front of Slahtz the xp eliminator npc
at that point i got scared of a gm watching over me lol
but i just said fuck it and play around with it
as i hearthed out 1 sec before the cast time i said in /s "thanks for the 5k loser lmfao"
my friend pick me up to go to the dungeon and go back to what we were doing
while we were flying to the dungeon my friend and i joked around being watched
he was scared since he doesnt know if this bug trade would get him banned
told him its fine
its been a few days now and hes still playing
maybe i wasnt watched or they couldnt care less about us lol
That makes complete sense. Alot of my OG twinks have more XP than I remember them having (though none are at that 1 point away spot)
What is the static pop xp off macro? can't seem to find it
apparently right click reporting is not working and is bugged
maybe i wasnt watched or they couldnt care less about us lol
if you are so worried you wont be enjoying your game .. its like you know you did something wrong and the punishment is gonna come anytime lolol .. dont worry too much about it, if you want to do it then expect the worst .. what could be the worst ? just a ban which is unlikely, prob a short suspension for 1st offence, but still its not the end of the world .. you can always start a new account .. then again, if you dont think you can take the worst then dont do it
I'm curious how does this file rework work. Share if u don't mindthe exploits im doing are on a 2ed account, not risky main. basically egging blizzard to do something as im intentionally opening tickets of me doing the so called exploit of getting into a bg with xpoff ;same with the trade bug and other known exploits
and im still playing
at this point im even doing file rework that friends are telling me that can bypass blizzards watch *copying achievement points from characters in armory* so i can use any mount in the game and people can see the mount im using
im out here flexing the mythic end tier mount that i earned all by myself : )
I don't think you understand what I said. Right now, there are 2 queues for each bracket, one for those who've turned off their XP (twinks) and one for those who have XP on (levelers). Right now, there are some twinks who are exploiting a race condition which is allowing them to enter XPON battle grounds. What I'm saying is simply have a bit of code that's executed relatively late (long past the window available for the race condition, but early enough that it doesn't impact latency when actually fighting in the battle ground) that enforces the XP on/off criteria for that particular battle ground. So if you enter an XPON battleground and exploited the race condition so that you entered it with your XP turned off, it automatically turns your XP back on (and conveniently causes you to have wasted the 10 gold you spent in turning it off). Net result is that you're still in the queue you desired, and you're still gonna face stomp the levelers in the battle ground, but you're also going to be gaining XP and as such will be leveling out of the bracket. In a nutshell, if you're honest and don't exploit the race condition, then you'll never see the change. But if you do exploit the race condition, you will eventually level out of bracket and will stop being a problem.Blizzard would never do this. They introduced the xp eliminator mob for twinks. And blizzard knows that twinks BG. So they would lose tons of subs as a result.
I don't think you understand what I said. Right now, there are 2 queues for each bracket, one for those who've turned off their XP (twinks) and one for those who have XP on (levelers). Right now, there are some twinks who are exploiting a race condition which is allowing them to enter XPON battle grounds. What I'm saying is simply have a bit of code that's executed relatively late (long past the window available for the race condition, but early enough that it doesn't impact latency when actually fighting in the battle ground) that enforces the XP on/off criteria for that particular battle ground. So if you enter an XPON battleground and exploited the race condition so that you entered it with your XP turned off, it automatically turns your XP back on (and conveniently causes you to have wasted the 10 gold you spent in turning it off). Net result is that you're still in the queue you desired, and you're still gonna face stomp the levelers in the battle ground, but you're also going to be gaining XP and as such will be leveling out of the bracket. In a nutshell, if you're honest and don't exploit the race condition, then you'll never see the change. But if you do exploit the race condition, you will eventually level out of bracket and will stop being a problem.
I understand what’s you were saying perfectly. I don’t think you understand what I’m saying. Blizzard is aware people do XPoff bgs as twinks, after all, the xpoff npc was put in place by them. What you are suggesting won’t be done when they know twinks organize xpoff games. And a lot of the time, the twink is subbed and doesn’t play mains. If they knew they couldn’t do xpoff bgs because they would auto get their xp turned on, they would let their sub run out and quit
You STILL don't understand.I understand what’s you were saying perfectly. I don’t think you understand what I’m saying. Blizzard is aware people do XPoff bgs as twinks, after all, the xpoff npc was put in place by them. What you are suggesting won’t be done when they know twinks organize xpoff games. And a lot of the time, the twink is subbed and doesn’t play mains. If they knew they couldn’t do xpoff bgs because they would auto get their xp turned on, they would let their sub run out and quit
Actually, I'm a bit surprised that Blizzard doesn't just add a bit of code to execute against everyone who enters an XPON battleground. Namely, just automatically turn XPON for every character in the battleground regardless of their XPON/XPOFF status. And leave the XPON status alone when they eventually exit the battleground. Wouldn't increase the latency since the action would happen at the time they enter the battleground and prior to the combat actually starting. And would totally bypass any race conditions being taken advantage of by the macro since it would happen long after the macro has finished executing.
I understand what’s you were saying perfectly. I don’t think you understand what I’m saying. Blizzard is aware people do XPoff bgs as twinks, after all, the xpoff npc was put in place by them. What you are suggesting won’t be done when they know twinks organize xpoff games. And a lot of the time, the twink is subbed and doesn’t play mains. If they knew they couldn’t do xpoff bgs because they would auto get their xp turned on, they would let their sub run out and quit
Possibly. But race condition errors are one of the hardest issues to solve in programming. And for performance reasons, it's not uncommon to use non ACID compliant data bases for systems having real time performance constraints. I think your approach might work, but there's still the latency issue which can be abused (think unplugging network cable for a few seconds or the like). The method I mentioned would work, but not solve the underlying race condition. And it would be one of the milder approaches. A more draconian approach would be to have the server compare the XPON/XPOFF status of the players against the status of the battle ground and flag those with mismatches for closer examination/banning. My approach simply renders the exploit ineffective and provides a minor punishment in that it causes the abuser to waste their gold.
Not really, that would just mean a 48 hour cooldown on the twink entering the XPON battleground.A 24 hour cooldown on the npc option would suffice, the only reason to toggle it so often is to exploit this bug.