Leveling both my warrior and my warlock (still low level) on Barthilas I came across a few botters. Well actually like 10 or 15.
But there were a few that really pissed me off.
As a bot, they have to regard for other players, and will commonly pull something just before you do, and then it gets trained onto you and you gain nothing. There were a few, which i added to friends and monitored, who seemed to bot wherever I happened to be.
A few spots that are prone to botters are;
-Just south of Camp T. (Barrens)
-Felmusk Saytrs in ashenvale
-1k needles salt lake
-Tanaris Ogres (south west ruins)
-Ungoro Tar Lurkers
-Winterspring ghosts
-winterspring yetis
-Carrion Birds just South of Honor Hold (Hellfire)
-Nagrand Neutral mobs around Nessingwarys.
The best way that I found to deal with them, is to /follow. Depending on the bot, it will usually log out in about 5 min.
There has been a lot of talk going around the Rogue forums of a macro exploit that allows a person to see all the stealthed characters.
I have been randomly knocked out of stealth from people outside by path or at a good range in BGs, but its happening to Rogues in Arena too.
Someone made a post about it on the CS forums and Blizzard pretty much acknowledged it, but no clue on when they plan to fix it. Good news is that the macro is not widely available.
In Arena it is probably easier to report people who use it, in BGs its a bit difficult as sometimes you just get swarmed by them.
Well, there's an obvious one, which isn't really an exploit at all, that just involves targetting your nearest enemy and casting an instant cast. It requires you to already be able to see the stealther though, so it's really not different than click-targetting a stealthed player next to you and immediately casting an ice lance or w/e.
The real exploit floating around seems to involve target-of-target, and only seems to work if the stealther is targetting the exploiting player. It could also entirely be a bug in the targettarget system that shows someone as targetting you when they really have no target, coupled with people's paranoia of hacks (i.e. coincidental targettarget bug + "exploiting" player running around casting rank1 aoes because they think a stealther is there).
However, that scenario doesn't explain the "Warrior runs straight to me at the beginning of an arena and charges me while I was stealthed the whole time" scenario. However, again, this involves the stealther targetting the other player. Some players have reported that simply untargetting the "exploiter" causes them to lose their target as well, and run around just as blindly as everyone else.
There's 2 different "macro hacks" at work right now for stealthed units.
The first uses the command targetenemy to target a player that has you targeted, and you can then cast an instant at that player.
The second involves, based on my understanding of it, changing a small section of the client's code to expand your "in melee range" flag from 5 yrds out to 99 yrds. This causes any stealthed units within 99yrds to become semi-visible as if they had just wandered into melee range.
The first will likely be fixed soon, and the second will quickly bring down the wrath of Warden now that Blizzard is aware of it.
There's not some hidden "but he tries really hard" variable built into the game. -Slake
I always love the "it doesn't fit my style of play" line. There are only two styles of play; Correct, and Incorrect. The only people that ever use this line are people with the incorrect style of play. -Sebudai
The first will likely be fixed soon, and the second will quickly bring down the wrath of Warden now that Blizzard is aware of it.
I am curious about that second as this would have to be done on the fly. Any modification to the exe should result in failure to open the client as it would be detected. As for Warden catching it, doubtful as they admissions to what it wasn't catching in the case of glider were telling.
I haven't seen it in arena but I have seen quite a few speed demons recently, basically the old move at warp speed location hacks I thought had been dealt with. Specifically with classes that have no super speed buff.
The second involves, based on my understanding of it, changing a small section of the client's code to expand your "in melee range" flag from 5 yrds out to 99 yrds. This causes any stealthed units within 99yrds to become semi-visible as if they had just wandered into melee range.
I highly doubt this is true. From what I know, the server is not supposed to be sending data on units invisible to the player at all, so there must be something more going on and affecting the server side logic.
--
Originally Posted by ZeroWashu
I am curious about that second as this would have to be done on the fly. Any modification to the exe should result in failure to open the client as it would be detected. As for Warden catching it, doubtful as they admissions to what it wasn't catching in the case of glider were telling.
Warden is generaly useless for catching anything but the simplest, publicly available hacks. In the modern state of PCs there is nothing (outside the realm of trusted computing) you can do to catch client-side modification of anything. It is an arms-race lost from the start.
I have a sneaking suspicion that some of my guildies might be using a hack for SWstats and Recount in order to boots their damage done.
If anybody have any information on this I'd be happe to hear about it - especially if there is a way to catch people doing this.
I use WWS stats myself - and as that is only my combatlog I don't see any way of tampering with that.
They can't fool your combat log. If yours says they are doing 2000dps and theirs says they are doing considerably more; its likely they are altering their combat log. Check if max/average damage is some % higher. As for recount, turn off syncing in recount (sorry don't remember the command) and again check if theres large differences. Especially with the average damage on their abilities.
Your combatlog can easily be editted to produce a fake WWS if you are so inclined.
WWS and Recount calculate dps rather differently though should be close on total damage done. The best way to check on your guild mates is to run Recount yourself and compare with their reports.
I'm well aware that I can change my combatlog, but as long as I run WWS myself I guess I should be safe. About Recount I'll try to turn syncing off.
If anybody has an relatively easy way to catch people cheating with the meters I'd like to know.
But thanks for the answers guys
This may be terribly obvious, but also keep in mind that the default range for the combat log is rather low. Make sure to increase it to maximum (200 yards I think) to reduce the disparity among the information. This could also explain why others information is off - they probably have the combat log range set too low. I see it way too often to not mention it
This may be terribly obvious, but also keep in mind that the default range for the combat log is rather low. Make sure to increase it to maximum (200 yards I think) to reduce the disparity among the information. This could also explain why others information is off - they probably have the combat log range set too low. I see it way too often to not mention it
Combat log range is always set to maximum since the 2.4 patch, the old methods of changing it's range have no effect whatsoever any more.
Today in the Gurubashi Arena I noticed something very strange. An enemy alliance player suddenly wasn't attackable and could so loot the chest before I could do anything. He is a retribution paladin, that activated his Divine shield and then turn from red (enemy) to green (ally). Is this a bug or a reproduceable exploit ?
Hildegard Sprigglespruxx - Wissenschaftlerin am Institut für Pfuschkunde
04/02/08, 1:29 PM
Similar Threads
