Disable the plugin demand while doing a corpse run. No wonder ppl gets banned when bot tries to dismount over and over and over while doing corpse runs in Hyjal !!!!
I died in mount Hyjal and corpse run is mounted. As we all know This site requires you to pay to be able to use fly-mounts. Thus Honorbuddy tried to dismount during the whole corpse run. Making the corpse run stutter the whole way to place of death. Please disable mount check while you're dead.
You do realize that you can't be seen while your dead, right? Except by other dead players ... To state that people get banned because of this is a little far-fetched. Someone would have to in the same exact spot as you, and be dead at the same exact time as you in order to see you stuttering. The percentage of that must be very low.
LOL not only do I agree with the above, BUT who in their right mind would corpse run on the ground in hyjal? Any real player dead will fly to their corpse so that makes it even less of a chance to get detected.
My point exactly, Hb should be allowed to fly when doing a corpse run. now it takes a detour running on that spirit-mount. hawker. I'll post a log next time it happens.
If a GM backtracks can't he see you've tried 200 times to dismount that spirit-mount ? Even if the chance is low. The chance exists and should be eliminated.
I dont know what the argument is, having your corpse stutter and backtrack across the landscape no matter if you can be seen or not is just plain stupid, end of story. What the hell are all you guys rambling about?
Hb doesnt support flying yet... Yes it allows you too have flying up while hb is running but thats a different thing..
If it's a bug then it should be logged in the bugtracker, etc. to be fixed. I was simply stating that there are probably not a whole lot of player reports happening because of this issue, which was the OPs point. The post title indicating that they didn't think it through or didn't care was a little rude/uncalled for so I was giving a logical explanation about the chances of being reported for it. Again, if it's a valid bug then it should be submitted properly instead of calling out the devs in the post title.
Dont you know its more constructive to throw vitriol around than give useful information in the requested fashion to help improve the product. Thats just obvious.
oic, wasnt sure why - was happening to me today with Mr. Autofight. You'll find an instance of it occurring at 2:42 in attached log.
