Post all your /dump stuff here

[Rikeku]

/beg rogue macros

[Notmywownameyo]

IF you do the exploit to be able to use dump macros again, but use the dump macro to only use wind shear and dont automacro it into moves and use it manually yourself, is it still traceable by blizzard ? ( this is what i meant from my first post but i didnt make it clear, sorry)

[jt12852]

If Blizzard wants to find out, they will find out. Neither of the workarounds (archive removal or injection) are particularly difficult for Blizzard to detect if they want to.

I doubt they will evaluate people abusing these exploits and hacks on a case-by-case basis. Usually they just take a week or two to find all the accounts that are using an exploit, then take action on all of them at the same time.

So if you're going to use it, go all out.

[Notmywownameyo]

So its not really a case of if your caught but when ?

[pkaa4eva_jr]

Honestly, i don't think you will be caught if you do everything the right way meaning doing /console synchronizeMacros 0

In my opinion the only way you will get caught is by player reports.

[Notmywownameyo]

Honestly, i don't think you will be caught if you do everything the right way meaning doing /console synchronizeMacros 0

In my opinion the only way you will get caught is by player reports.

people have said that they can autoscan for edited files and stuff so they wouldnt even have to put effort into banning people? any confirmation on it?
the way im thinking of using dump macros would be near undetectable by other players only

[dirdir207]

The cleanse macro one page back doesnt appear to work, atleast when changing polymorph to fear. I haven't been able to test it with polymorph yet. Any idea on how to fix this? As well as having it cleanse on sheep OR fear?

[jt12852]

Yes, they can quite easily determine if you're using the previous version of Blizzard's DevTools addon (which is what is technically happening when you delete the patch archive file), since a list of addon names and checksums gets sent to the server when you log in. It would require updating Warden for them to detect the injection method, but that isn't terribly difficult for them to do either.

The real question is, whether Blizzard wants to devote time and resources to do this, especially with BlizzCon going on right now. The easier solution for them is to simply use a new code signing key for their addons in the next patch, invalidating previous versions of their addons. This would not prevent the injection hack, but there are plenty of other injection hacks going around and this one is not particularly any more serious.

Yes, using this exploit or any other exploit can cost you your account. For some people, it may be a worthwhile risk. For others, it isn't. You just need to decide what your tolerance for risk is.

[dirdir207]

So I made a working cleanse macro for debuff fear, however it seems you have to be targeting the person being feared which defeats the purpose.

/dump loadstring("if(UnitDebuff('party','Fear'))==exists then CastSpellByName('Cleanse') end") ()

Anyone know how to perhaps have it target the individual that has the debuff fear on them?

[Soiidus]

OI cant get the arcane rotation working it just gives me a lua error

[rimalah]

ah well, it was fun as long as it lasted.

today I started to get DCs, and the cause seemed to be renamed patch-2.mpq -file, so if you bypass the "hotfix" then prepare to dc a lot >:

[Estima]

ah well, it was fun as long as it lasted.

today I started to get DCs, and the cause seemed to be renamed patch-2.mpq -file, so if you bypass the "hotfix" then prepare to dc a lot >:

Confirmed.I get DC roughly every 10 minutes.

[Soiidus]

i dont. my internet sucks though

[Apoc]

See the first post for a detection warning.

[pkaa4eva_jr]

Confirmed.I get DC roughly every 10 minutes.

Yeah same, to fix that all we would have to do is re-name the file back to the original name right?

And for those people who changed the file and are now having second thoughts do you think that re-naming the file back to its original name will fix this and running the blizzard repair?

EDIT:

Updated, Iv re-named the file back to it's original name and the Dc'ing seems to have stopped.