Battlezone Universe

Battlezone Universe => Battlezone 2 => Maps and Modding => Topic started by: General BlackDragon on July 25, 2008, 03:01:49 AM

Title: Most horrific Bugs Ever Thread
Post by: General BlackDragon on July 25, 2008, 03:01:49 AM
I decided to start a little thread where modders can share their most emberressing/biggest/worst bugs they've ever made.

I think I automatically win this one...with a Bug I accidnely introduced into BZC for the past year. I'm fairly sure I've fixed it just now, the 3rd time...

In 1.3, there is a chat lobby, much like BZ1's lobby. For BZC, I made this in the main multiplayer page and not hidden like in stock BZ2.

Basic Description of Bug: When Ever a player hit the "multiplayer" button, or was in the multiplayer screen and then left, all BZC games in progress would AV.

Yes. I made a bug that kills multiplayer for an entire game at the touch of one button.

So, who's next?

Title: Re: Most horrific Bugs Ever Thread
Post by: Steeveeo on July 25, 2008, 10:14:15 AM
Not...quite as extreme as THAT, but...

I was making a custom bomber bay for SRV, ibbomb_st, and I thought I had it all setup correctly, however, whenever it was placed (in the editor or by constructor), the game would AV with a very long an undecipherable AV log.

Two days of scrambling around my assets, looking for the problem (and finding none that were in plain sight) later, I had found the cause.

Turns out, I had told it to spawn iBbomb_st instead of iVbomb!_st! So, basically, it AV'd because it was trying to spawn a building on top of itself, and that building (if successfully spawned), would try to spawn ANOTHER building on top of it!

Needless to say I did a combination *facepalm*/*headdesk* for the next 15 minutes...

I know it doesnt SOUND like much, its just how long I searched for the PROBLEM that was embarrasing. :P
Title: Re: Most horrific Bugs Ever Thread
Post by: bigbadbogie on July 25, 2008, 10:24:25 AM
Oh god.. where can I start??

Ok. A few days ago I was testing a QF mission and ran into a dll problem ingame. I looked through the entire section of script and couldn't seem to find what the hell was wrong. I ended up redoing over 200 lines of script in a completely different way with the same result as before; it still didn't bloody work!!!

It turned out that a variable that was supposed to be increased by a variety of routines was set to 1, instead of 0. And that was the entire f**king problem!!!!
Title: Re: Most horrific Bugs Ever Thread
Post by: shane ward on July 25, 2008, 10:58:15 AM
Me, Making a mission that overwrites the stock assets and causes people to leave multiplayer with bad assets!. Must be the worst one out therere  :evil:

shane
Title: Re: Most horrific Bugs Ever Thread
Post by: Steeveeo on July 25, 2008, 11:07:48 AM
Quote from: shane ward on July 25, 2008, 10:58:15 AM
Me, Making a mission that overwrites the stock assets and causes people to leave multiplayer with bad assets!. Must be the worst one out therere  :evil:

shane
I think GBDs was a bit worse :P
Title: Re: Most horrific Bugs Ever Thread
Post by: General BlackDragon on July 25, 2008, 09:42:17 PM
Quote from: General BlackDragon on July 25, 2008, 03:01:49 AM
I'm fairly sure I've fixed it just now, the 3rd time...

Okay, NOW I'm fairly sure i've fixed it. (Yes, It came back a 4th time)

So, 4th time's the charm?
Title: Re: Most horrific Bugs Ever Thread
Post by: General BlackDragon on July 26, 2008, 02:32:14 AM
Nope...

Screw it, I'm smacking it with a big hammer.
Title: Re: Most horrific Bugs Ever Thread
Post by: Feared_1 on July 26, 2008, 06:34:23 AM
Man that would be horrible (GBD). At least people can figure how many times Multiplayer is clicked throughout the day. :)
Title: Re: Most horrific Bugs Ever Thread
Post by: General BlackDragon on July 26, 2008, 03:46:14 PM
I hope people don't like the "Next" button in the end game scores screen too much. :)