Stand up for Blade's Edge bugs
by Mike Schramm 
Jan 21st 2008 at 6:00PM
This is the best bug I've heard about in the game yet so far-- Drysc has confirmed that there is a known bug in the Blade's Edge plateau area which will cause everyone, when someone starts up the Bombing Run quest, to stop eating and drinking and stand up. It's a respect thing, you know? Stand up for the cause!No, it's just a really, really weird bug, and a fix is on the way in an upcoming patch (I'm a little surprised they don't aim to fix it earlier, but apparently all that will be lost is the food anyone sits down to eat at the wrong time in Blade's Edge). Once again, I am dumbfounded at trying to figure out just how Blizzard's code works-- seems like they have the absolute weirdest bugs happen to them sometimes.
Filed under: Analysis / Opinion, Bugs, Odds and ends, Blizzard, Humor
Reader Comments (Page 1 of 2)
DanKOzz Jan 25th 2008 5:21PM
I'm more concerned about the bug/expliot with the hunters snake trap.
Michel Jan 21st 2008 6:10PM
I could be mistaken but I think wow create some "automate" (an auto-generated program) on the server (but also in your client) in answer to players actions.
this automate control what the software will show on the screen of players.
among the myriad of actions, possibilities, reaction and movements availables to quest writers, it surely easy to ask the wrong action instead of a proper one
or to ask an action upon everyone only the one character involved.
the automate is generated in answer to quest taken by players and it creates havoc :)
Tridus Jan 21st 2008 6:18PM
Actually they were supposed to have fixed it in a previous patch, but failed.
matt Jan 21st 2008 7:18PM
I seen Drysc comment a few days ago and thought the same thing
Katsuya Kaiba Jan 21st 2008 6:23PM
I guess they were too busy with the Ghost Wolf problem.
Mike Schramm Jan 21st 2008 6:40PM
I lol'ed. and then cried.
Eleazar Jan 21st 2008 8:58PM
srsly.
I love that they can't fix this fairly noticeable and annoying, and yet find time to stealth hot-fix the "OMG hunatr goest wulf problem"....Logic defies this.
Eleazar Jan 21st 2008 8:58PM
srsly.
I love that they can't fix this fairly noticeable and annoying, and yet find time to stealth hot-fix the "OMG hunatr goest wulf problem"....Logic defies this.
klink-o Jan 21st 2008 6:43PM
I've noticed the problem at Alliance flight point too.
Varshak Jan 21st 2008 7:00PM
Hah! That explains that, then... I initially thought I'd accidentally moved or something, but it kept happening. There you go.
Xioyn Jan 21st 2008 6:45PM
did they fix anything in 2.3.2 I thought they said they would fix the boats but they didn't get fixed said they would fix this they didn't what else didn't they fix but said they did?
Baluki Jan 21st 2008 6:58PM
I bet Blizzard is starting to regret hiring Rube Goldberg as Lead Programmer.
Saiforune Jan 21st 2008 7:09PM
Omg that was good lol! But this is an old bug, Mike is Slow xD!
Icepuck Jan 21st 2008 7:05PM
I am just amazed at how strange the errors get on the logs... "butterfly effect", blizzard tweaks something and all hell breaks lose on the other side of the world.
My favourite error was the Onyxia Breath Bug were she would constantly deep breath... funny thing being they didnt do anything to the event, or add new dragon bosses, or even new instances in that patch... so how the hell did a Dragon go mental from a patch that didnt even go near her.
I think Blizzard in the initial design didnt think they would be required to make so many changes over time and since the code is not as solid stable for patch changing...
It also breeds the issue that if it is so problematic, it must be difficult to change... what if the code was cleaner and easier to change with less bugs, there would be more content and faster patching.
Wake up Blizzard, the norm is not cutting it, time to look at the drawing board and see what you can do to improve the basic model of game data within WoW.
theRaptor Jan 21st 2008 7:29PM
It is to late. Standard software engineering maxims would say that changing fundamentals at this stage would be more expensive then designing a new MMO. It is like re-doing the foundations after the building is built.
Icepuck Jan 21st 2008 7:51PM
Well they have to do something to strengthen the foundations of the game data coding or it will continue to get worse and worse in relation to errors, delays, and crashes.
3 months of PTR for 1 patch is a joke, only to see it still get released with errors... what chance does WotLK has in those odds.
Its like a big Jenga block tower at this point... the errors are just getting more and more obscure and unrelated to patches.
Amanda Jan 22nd 2008 6:28AM
lol, Like the other repliers said, it's too costly and such...
WHich is why the are making a new MMO in the Warcraft line.
Eternalpayn Jan 22nd 2008 7:40AM
If they were to alter the way that a somewhat generic NPC script works somewhere, that was also used by Ony, it would cause this bug.
Now, this is an interesting bug. My guess is that it was actually a typo. When you talk to an NPC, I believe it most likely runs something like stand(), just to create a name quick. Stand() probably has a variable of either 0, 1, or 2 in the parentheses. If it is 0, it causes the NPC to go into the standing position. If it is 1, it causes the person who interacts. If it is 2, it is an AOE effect. They would need another variable in here to define the area. What they probably did here was make a typo in the name of the variable they were trying to set when they fixed it. This would cause the variable still to be unset, and they probably have something in the script where if the variable is unset, it works for the whole zone. This would be to avoid people getting an error message for accepting the quest.
That is all just a possibility, of course. There are many ways of doing things when coding something this massive.
Verit Jan 22nd 2008 11:42AM
So what happens is Blizzard updates a function or some other shared resource that the onxyia event relies on. When that function is called - the wrong data is sent back (or unexpected data) thats not handled properly in the onxyia program.
The other explanation is that - they don't always document all changes. Also in some organizations (especially smaller software companies) engineers are famous for making changes without approval as well - although I'm sure by this point Blizzard has cracked down on that.
Daryl Jan 22nd 2008 6:11AM
Didn't have stand up bug for months until yesterday when doing Consortium quests in the Etherium
Rydolomo