(adsbygoogle = window.adsbygoogle || []).push({}); Just a thread about some World at War bugs:

1) AFTER ACTION REPORT: is blank after match, no data is loaded into the client window.

2) MIGRATING HOSTS: usually times out after first attempt, despite multiple potential hosts in lobby.

3) CASTLE MAP: Under and out of map, players can get out of the normal game arena.

4) CASTLE MAP: Elevator glitch, players can glitch and end up hovering many feet in the air giving them a suprise advantage and view across much of the map.

5) CASTLE MAP: Out of map glitch, it is possible for a player to be able to climb onto the top of the main (RED) castle roof and be hidden from other players below in the normal game arena, whilst being able to still attack people despite being clipped into various areas of the castle roof.

6) CASTLE MAP: Out of map glitch, using a bazooka exploit, it is possible for a player to be able to climb onto the top of the main castle roof and be hidden from other players below in the normal game arena, whilst being able to still attack people despite being clipped into various areas of the castle roof.

7) CLIFFSIDE MAP: Elevator glitch, players can elevate in the air and gain a suprise and height advantage giving them a view unintended by the map design.

MAKIN MAP: Clipping / Map glitch: there is scenery on the map where players can clip into, where they can then crouch and be invisible to other players, yet still be able to attack others.

9) INVITE FRIENDS: Non functional, and has been for the majority of players since approx Friday 26th Dec 2008. Inviting other people results in error messages such as "game session is no longer available" to the invitee. A small minorty seem unafected by the bug. This still affects people even when both clients are open to the internet and not behind a firewall or NAT.

10) PORTS: The list of ports used by this PS3 client have not been released to the public by Treyarch, it would be good if you could in order that we can put our firewalls back on and our PS3's back onto our internal networks, and/or forward the ports needed to make features such as the friends list work properly. Previous to friday 26th (see bug 9) it was necassary to make the client machine open to the internet in order to get this to work properly.

11) MATCH QUALITY: When joining games, the client checks to see if the host is good enough quality for a game to be played on, then it joins if conditions are met. This needs to be more stringent, or allow the user to set options in the client to ONLY connect to servers with ping states acceptable to them, location, and possibly even other factors such as maps etc. EX: 3 Bar ping or better, maps makin [x] cliffside [x] castle [ ] etc etc.

12) JOINING HOST ON INITIALISE: If the client joins a host right at the second the counter reaches 0 and is initialising the loading screens, the client will hang in an unrecoverable state, requiring a hard reset of the client machine.

13) MUTE PLAYER: Muting a player only lasts till the end of the round, then you are unable to mute a player when in the lobby, when map changes you have to remute people all over again, muted player should stay muted for the duration of being in the same game lobby (even after migrating hosts) if not be permanent until client unmutes (cross servers and game sessions)

14) SAVE GAME: Single player, saved games often dont load and report that the save is not compatible with the current version - though the version has not changed. This usually happens if the player has exited game and/or restarted their machine between loading saves.

15) SETTING UP GAME: When clients joins a host of poor quality and the game progresses through the loading screens, the clients can become stuck on or just after the "Setting up game..." screen, this usually only shows on screen for a second or less, yet will hang there for minutes on end with clients still able to chat via coms. The timeout should be much faster, or allow the client to still quit out during this stage, as currently you have to sit and wait 5 minutes for it to timeout, OR restart your machine.

16) STATS RESET: At the end of a public game, if clients exit by hard shutting down their system and not exiting using the in game menus, then their stats data can become corrupted and end up with the majority of their statistical information, including level, being lost. This is due to them interrupting the data save process while the game is communicating with the stats server.

17) BOOT CAMP: Under certain conditions, the option to join boot camp game mode still remains available, and high level players can still join and play on a bootcamp server, despite him and his party mates being too high a level to normally join the game mode.

1 BOOT CAMP: If a player stays in boot camp and doesent leave, they can remain there indefinately, despite their rank. The game should at some have a cut off point make them "pass out" as you should do after boot camp, and force them out of the game (not mid match obviously!) this could be done with a "Congratulations!" type message and perhaps a little fanfare or whatever, maybe some text explainign how its time to go out into the battlefield and fight for victory blah blah.

19) DOMINATION BOOSTING: Teams of players are exploiting the game mode for domination. Suggested fix: make B uncapturable until the other flag points have been taken at least once by both teams. IE: each team should have to capture their "home" flag at least once before being able to get B, this will then mean that even if players collaborate and capture home flags and then B, the ticket system will be unbalanced and thus stop them gaining so much from doing this. It wont however stop them completely, but will reduce the affect of what they do.

20) SPAWNING ISSUES: Due to the way the game currently spawns you near team mates, for various reasons including avoiding spawn rape, players can end up being spawned right in the middle of an artillery strike, spawned ontop of bouncing betties, spawned next to team mates who are currently in last stand and get shot along with their dying team member, spawned in a corner with your camera looking up in the air, spawned with your back to several enemies, etc etc. This bad game spoiling bug needs a priority above all but game stopping bugs.

21) UNLIMITED AMMO: If a player mounts a machine gun using a bi-pod, it is possible to fire the weapon constantly without needing to reload or having the gun overheat.

22) BOUNCING BETTIES: When placing a Bouncing Betty mine, the mine can self trigger and detonate in the players face killing them. This seems to happen when the player is being viewed in spectator cam, but can also happen doe to the "bubble" trigger surrounding the Mine clipping through walls and ceilings. A mine can be placed on the 1st floor of a boulding and depending where it is, if a player walks under it or is stood on the floor below the mine will trigger. Mines can also be placed next to walls and if an enemy player is on the other side of the wall the mine will trigger killing the planter and not injuring the enemy in any way.

23) VOICE COMS: Frequently when in parties, voice coms will stop working, sometimes for the whole party, but more often for one or two people - who wont be able to hear each other, but everyone else can hear each of them. The other bugged players coms light will not even appear to "light up" if you are in this state with them. Leaving the party and re-joining it can cure the problem, as can sometimes adding another person to the party - suddenly coms become functional again.

24) ROUNDHOUSE MAP: Under and out of map, players can get out/under the map. players can then move around much of the map without being attacked, whilst still being able to attack others.

25) ROUNDHOUSE MAP: Clipping glitch, players can climb under the crane adjacent to bomb site A, unlike the other railroad models whose wheel bases are solid. the Crane allows players to clip into the model, the player can still be attacked however.

26) ROUNDHOUSE MAP: Glitch, an invisible walkway exists that allows players to get ontop of train carriages and enabling them to jump from train to train, gaining access to unintended areas of the map.

27) SEELOW MAP: Under and out of map, players can get out/under the map, players can then move around approx 85% of the map without being attacked, whilst still being able to attack others running around above them.

2 D-PAD UNRESPONSIVE: Sometimes the Dpad can become unresponsive mid game, meaning a player is unable to call artillery or open the map, or give orders to squad. Intermittent bug that rarely happens, unable to reproduce reliably. Bug confirmed with several other users.

29) "BLANK" SHOTS: Sometimes when firing pistols or bolt action rifles multiple shots can be fired as if by a semi automatic weapon, the amunition is still deducted from the players cache, however any of these extra shots that occur do no damage to the intended target. This annoying delay can often result in the death of the person it occured to - due to the valuable seconds wasted reloading. This bug tends to happen when being shot at by an enemy, and is possibly affected by bad latency.

30) I HEAR DEAD PEOPLE: During search and destroy matches it is sometimes possible to hear the (dead) enemy team over voice coms, sometimes they can hear you but usually it is only one way. Enabling you to "spy" on their team by listening to conversation. One way to replicate this seems to be if a player goes into last stand and is then recovered - the game counts them as dead. You can still talk with teammates over voice as normal. Players could potentially exploit this and deliberately put themselves into last stand in order to spy.

31) MAN LEFT BEHIND!: When a party leader selects "find game" and takes his party to a server, sometimes players can get left behind in the lobby, this can happen even if the server has slots free. Sometimes the party leader will end up dropping into a new game lobby only to find his party hasnt joined him.

32) DROPPED PARTY: When a party leader selects "find game" and takes his party to a server, sometimes the game will have a hard time finding a server to go to (even with 100,000 people online) and players get dropped from the party, or the whole party will end up disolved unless the party leader presses O and backs out of it after a few seconds (this can still result in one or two people dropped)

this is a really good guide for new pople on this site

I agree. there sure seems like there are more errors on W@W than COD4

Thanks for the postive comments

If you gonna make this you probably gonna have to update this frequently from every bug.

-Whitey

Yeah, i will try and keep up to date.

nice guide. i've had all of these but i didn't know there were this many. good job

Thanks, for the comments. People always ask what;s wrong etc, so i thought i would post this.