It is currently Fri Dec 13, 2019 4:52 pm


Post a new topicPost a reply Page 1 of 1   [ 7 posts ]
Author Message
 Post subject: Familiar Error List
PostPosted: Wed Jun 22, 2011 10:24 am 
Gauntlet Captain
User avatar

Joined: Mon Jun 20, 2011 10:10 pm
Posts: 4995
Location: USA
Just thought I'd list the errors we're already aware of, so we don't end up filling this section with answered questions.

1. The Title Error: This bug is nothing big, it happens whenever you join a match. All it does is confuse your title with someone who's higher up on the list. It has no effect on gameplay and fixes itself as soon as you score a frag. (RETIRED)

2. No Avatar Error: This tends to happen when you're wearing a skin that's not supported by the server. Selecting a default skin easily fixes the problem. (RETIRED)

3. Boss Health Error: Sometimes you end up kicking too much ass (Usually with a Shotgun) and a Bosses health goes below 0. They're still dead, but need to be shot again to clear them from the map. Failing to do so results in them "Totally Whomping" you, as they are "alive" enough to continue attacking.

4. Infinite Queen Flash Error: This bug is exclusive to SX3M. (Monster Siege) This is a Queen's default response to being alerted to an enemy presence. Normally, a Queen flashes about 3 times before facing you and attacking. When a Queen is attacked by say, a Protector, she tries to face the enemy, but since she's not programmed to interact with Protectors, she continues flashing, confused, looking for a human opponent to blame for the damage. Even with players in range, so long as the Protector is active the Queen will not attack. Even after the Protector is removed the Queen may remain confused for some time, preventing you from clearing her from the map. EDIT: Attempting to remove her/awaken her with Teleporters has been know to cause Server Crashes. I like to go by Domination Standards as much as the next guy, but I prefer not to forfeit a successful mission by using this method as a Shorcut to get her out of her Stun Coma. Just know what you're getting into when you try it!

5. MAX And Angel "Ghost" Error: I'm not 100% clear on why this happens exactly, but I'm told they have a unique death that has them teleport out of existence instead of leaving a corpse. My experience says that Ghosts happen when you kill them, but die before their death animation finishes. It's kind of like an annoying rebirth that restores their Hit Points and allows them to torture you a little longer.

6. Multiple Boss Summon Error: Now THIS, is a BAD ONE. In that it can be abused to squeeze more points out of a map. The origin of this error has been found, but explaining how or why it happens still eludes us. Sometimes, for whatever reason, the game thinks you destroyed 2 gates when you only took out 1. You'll know the error has occurred when you see this message: "____ Has Destroyed The Gateway!" Now the game thinks there are 2 less gates, meaning you can end the game faster. Once you destroy the "Final" Gate, the game summons your bosses, but once the true final gate is destroyed, the game thinks it's time to summon more, so the counter is reset and the map is repopulated with bosses. Occasionally, this error happens several times in the same game, bringing in far more bosses than a map should ever have at any one time. (AT LARGE)

7. Assorted Weapon Errors: While this is broader territory, this post doesn't need more bullet points so I'll group them all here. Shotgun Lock: This is what happens when, for whatever reason, you decided to use Alt Fire and hold the fire button down. Stupidly enough, your gun no longer fires. You can fix the problem by using a throw command, or better yet, don't use the Damn Alt Fire! IT'S EXACTLY THE SAME AS PRIMARY. General Weapon Lock: EXU weapons tend to use multiple ammo for one attack, and sometimes without noticing it you end up running out of ammo while still engaging an enemy. Assuming you kept firing after it was tapped out, the weapon no longer fires and refuses to switch weapons, even when you pick up more ammo. Fixing any locked gun is the same story as for the Shotgun, use a throw command. A good way to prevent the problem is just to keep an eye on how many shots you have left; it's a Hell of a lot easier than having to toss your gun with a MAX bearing down on ya. (RETIRED)

8. Random Crash Error: This problem has to do with projectiles fired by MAX and select Angels. Apparently this is an issue that deals with Screen Flash. When a "_____" fires a BFG (That big exploding green ball) it illuminates too many surfaces at once, which makes the game sad. UT crashes at that point, robbing you of potential points and possibly even victory. This error has a come and go attitude, rearing it's ugly head more frequently at specific maps, like JunkyardWar, while more seldomly appearing outside of that map. (But still showing up from time to time.) A good way to prevent this from happening is to eliminate all offending monsters and their gates as soon as possible. At times the crashes are so serious they can bring the whole server down with it! The Bug's severity doesn't stop there! At times it won't even afford you the release of a crash, AND COMPLETELY FREEZES YOUR PC. Sometimes, if you wait it out long enough, Task Manager will EVENTUALLY show up. Other times it gets stuck behind the UT Window and becomes completely out of your reach. Dr. Wildcard's prescription to this malady is to invoke Windows+L, to lock your PC which forces UT to take the backseat so Task Manager can do its job.

9. No Boss Error: This bug is somewhat uncommon and is a mystery to us. Sometimes, right after you take out the last gate the game summons the bosses, but for some reason it also thinks the game ended and vote pops up soon after that. Even if it was CLEAR the game wasn't over and the bosses are visible AND attacking you. This is one of those hard to predict errors in that it happens whenever and wherever it Damn pleases, even at maps where Boss summons are "always" successful.

10. Suicidal Boss Error: Bosses usually go down hard and fast, so it's hard to say if this error is frequent or rare. Have you ever seen a boss standing still, attacking nothing but damaging itself? That's what this bug is. My (New) theory on why this happens is this: Sometimes when you are fighting a boss, you fire a shot at them, but die before it connects. The boss no longer sees a target, so it resumes passive behavior, when your projectile connects, it perceives a threat but at the same time, can't find one. With it being the only pawn in the area, it does the only thing it can think of, it attacks itself. I can't say for sure, but this error may or may not be affected by the attackers "Living" presence in the map. In English, whether you've already respawned before the attack collides may determine if the error occurs. This bug shares similarities with the Infinite Queen Flash Error above. That is, the idea of bosses getting confused it they take damage but can't see you.

11. Blue Team Error: This is a relatively new error, most likely awakened by the surge in server popularity.
This bug is limited to SX3M, and it is a BAD one! It forces players to be on the Blue team, even though the game type is set up for players to be on Red ONLY. There are 2 big problems with this: The first is that players switched to the Blue Team can't even see. They're stuck in a spawning loop where the camera jerks around and they're more or less paralyzed, while spamming the log with spawn messages. The second big issue is that the game is still running under SX3M rules, which means that any damage suffered by the unwilling Blue team is reflected on their core, cheapening games for the Hard-Working Red Team. How does this error happen in the first place? Well, It's a long shot, but I'll make a guess. I believe it has something to do with how the server keeps track of team balance. For every player that joins, (even if they quit) it logs a player. When it reaches 10, it thinks that the Blue Team needs players, and sends every new player to the opposing side according to the team balance it THINKS it needs. (ACTIVE)

12. Crippling Lag Error: This is arguably the most familiar and complained about problem on this whole list. Most won't even acknowledge or realize half of these errors, but this one never misses. The reason for this lag is quite varied, and has no one source. Reason 1. Monster Overload: Scripted Pawns eat up a lot of memory, and the errors built into each one only make it worse. When monsters overrun a map, the game has to keep track of a LOT of code, for a LOT of monsters, and this isn't even counting the projectiles some of them fire! Reason 2. Popularity: This didn't use to be a problem, back when we were happy and small, the most players on the server at a time would be 6. Now, WHY would Human Players trigger lag? The server has to work hard to syncronize everything for everyone, and when the game becomes a full house, the server struggles to keep things going PERIOD. Reason 3. Hosting: Not everyone who runs a server has deep pockets, we can't all be Mr. Moneybags. And cheaper hosting packages means that some benefits are lost. With less priority set to it, it basically means that the server's not working as hard as it could be, resulting in a below "Light Speed" experience for all involved. This Unholy Tryst can slow the server to an absolute crawl, and when this happens, it's not uncommon for the server to go so slow that it doesn't even recognize your existence as a player, kicking you out of the server if not crashing you entirely. Players who complain the most loudly are often players who've been spoiled rotten by Bank-Breaking Servers, who would forget Lag existed entirely if they never ventured out of their happy places. The Million Dollar Question is how does this get solved? Nothing simpler! You can either make consistent donations to upgrade hosting and keep it running, OR, you can take the Penny-Pincher route and stop bitching like children. We Aren't The Grant-A-Wish Foundation. We can't make everyone happy, and as the saying goes; "If you can't take the heat, stay out of the kitchen." Or, in more modern terms, "If you can't handle the lag, you can get the fuck out!" Nothing is forcing you to play here, if you don't like it, there's the door ->. It's wide open, and we'll kick you right the fuck out and lock the door behind you!

And Finally...

13. Necrosis Is A Fucking Cheater Error!: I can't quite say for sure why this error happens, but I have a theory. It generally occurs when someone is unhappy about their score, and looks for a reason for it. Surely a lack of skill or luck couldn't be to blame for this tragedy! The best way to avoid this problem is to embrace the Good Sportsmanship Counter-Hack, which allows you to enjoy the game despite finishing a match with a lower score than preferred. Another good preventative measure is to complain LOUDLY about it to administrators and generally anyone who'll listen to you. That way it'll be clear to everyone what a big baby you are so we all can enjoy a good laugh at your expense. Continued whining is not recommended as you may stir the wrath of admins who just want to play the Damn game, forcing them to employ unsavory methods of dispatching you and restoring silence. The FINAL option is to go screw yourself and play elsewhere if you don't like it. (RETIRED)

That's all the errors I can think of to address for now, but I'll keep you posted if I think of anymore.

_________________
The Short Fuse +
Magnificent Bastard +
Glorious Douchebag +
Lord Of The Lols +
The Green Guy =
Necrosis MHS

Necrosis' Greatest Hits!

"You Don't Want To Do That."
"Do You Want Shit To Get Real?"
"These Errors, They Don't Make Any Sense!" "Your Face Doesn't Make Any Sense!"


Last edited by Necrosis MHS on Wed Jul 19, 2017 5:46 am, edited 3 times in total.

Top
 Profile  
 
 Post subject: Re: Familiar Error List
PostPosted: Mon Jun 25, 2012 7:33 am 
Cougar
User avatar

Joined: Fri Jun 01, 2012 4:23 am
Posts: 437
A possible workaround for the "flashing queen" error.

Put a Poison Guardian right under & in contact with her.

If she doesn't die right away, level it up...

It works for me about 2/3's of the time


Top
 Profile  
 
 Post subject: Re: Familiar Error List
PostPosted: Mon Jun 25, 2012 8:31 am 
Gauntlet Scout
User avatar

Joined: Sun Apr 29, 2012 3:24 am
Posts: 75
"We can't make everyone happy, and as the saying goes; "If you can't take the heat, stay out of the kitchen." Or, in more modern terms, "If you can't handle the lag, you can get the fuck out!" Nothing is forcing you to play here, if you don't like it, there's the door ->. It's wide open, and we'll kick you right the fuck out and lock the door behind you!"

You are the very soul of diplomacy, sir.

:-)


Top
 Profile  
 
 Post subject: Re: Familiar Error List
PostPosted: Mon Jun 25, 2012 3:15 pm 
Gauntlet Captain
User avatar

Joined: Tue May 15, 2012 8:38 am
Posts: 567
Varyag wrote:
A possible workaround for the "flashing queen" error.

Put a Poison Guardian right under & in contact with her.

If she doesn't die right away, level it up...

It works for me about 2/3's of the time


Didn't work last night on Chapel nights...:(

_________________
Image


Top
 Profile  
 
 Post subject: Re: Familiar Error List
PostPosted: Mon Jun 25, 2012 5:23 pm 
Gauntlet Captain
User avatar

Joined: Mon Jun 20, 2011 10:10 pm
Posts: 4995
Location: USA
I pride myself on it, Swamp Rat.

_________________
The Short Fuse +
Magnificent Bastard +
Glorious Douchebag +
Lord Of The Lols +
The Green Guy =
Necrosis MHS

Necrosis' Greatest Hits!

"You Don't Want To Do That."
"Do You Want Shit To Get Real?"
"These Errors, They Don't Make Any Sense!" "Your Face Doesn't Make Any Sense!"


Top
 Profile  
 
 Post subject: Re: Familiar Error List
PostPosted: Tue Jun 26, 2012 8:16 am 
Cougar
User avatar

Joined: Fri Jun 01, 2012 4:23 am
Posts: 437
cadaverjuice wrote:
Varyag wrote:
A possible workaround for the "flashing queen" error.

Put a Poison Guardian right under & in contact with her.

If she doesn't die right away, level it up...

It works for me about 2/3's of the time


Didn't work last night on Chapel nights...:(


Doesn't work 100%...


Top
 Profile  
 
 Post subject: Re: Familiar Error List
PostPosted: Tue Jun 26, 2012 9:08 am 
Admin Wizard
User avatar

Joined: Mon Jun 20, 2011 5:40 am
Posts: 2967
You could try telefragging her with a translocator its what I do she usualy wakes up but for somme reason you willl lose all your health and have only 1 health. She wakes up as a ghost and disapears in one shot no rewards gems or points but it gets rid of the queen

_________________
Image
The administration of "GateWays" "gauntletwarriors.com" reserves the right to be unfair.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post a new topicPost a reply Page 1 of 1   [ 7 posts ]


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron


Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
twilightBB Style by Daniel St. Jules of Gamexe.net