Plants vs. Zombies: Battle for Neighborville/Glitches

From Plants vs. Zombies Wiki
Jump to navigation Jump to search
HD Bug Zombie.png
Bug Zombie and Bug make a great team.
The content in this page is either bugged, glitched, or broken. A further update may fix these issues at a later date.

This is a list of glitches in Plants vs. Zombies: Battle for Neighborville.

"Host ended game session" Glitch

A session of a gamemode that doesn't have a specific host, such as Team Vanquish or Turf Takeover, will sometimes shutdown seemingly at random. Once spawned in the Giddy Park after getting kicked, the game will say that the host ended the session, despite having no host. This glitch is likely caused by the game internally referring every player of gamemodes without hosts are technically all the host, and when someone leaves the game during the match, the game sometimes thinks that the host has left the game, and therefore ended the game session. This glitch is also in Plants vs. Zombies: Garden Warfare 2 and is likely caused by the same reason.

Preserve Pastures Final Objective Crash Glitch

A variant of this glitch occasionally happens in Preserve Pastures where if the plants win the final objective, there's a chance that the lobby will crash when the game tries to load the endgame cutscene, forcing everyone back to Giddy Park. Unlike the above glitch however, this one does not result in the "host ended the game session" error to pop up upon returning to Giddy Park.

Rate of Fire Buff Glitch

If you play on a multiplayer lobby with a high ping, usually above 100 ms, there is a glitch where having a weapon with a slow rate of fire buffed will cause it to fire slower instead, while still consuming ammo. This can be easily observed with Engineer next to a Heavy Helper, Peashooter with the Pea Suped ability active, or Scientist with the Dolphin Blasting upgrade, though this also affects other slow-firing characters such as Electric Slide.

Loud Noise Glitch

On some occasions the game may unexpectedly produce some loud noise. One of the causes of this is having voice chat turned on, so disabling it might partially solve this problem. Another variant of this glitch exists where your character may glitch out and the game will then produce either a loud pop or a very loud bang, which might scare you off if you don't expect it. There is currently no known solution to fix it.

Multiplayer Portal Reloads Giddy Park

If you exit a multiplayer game mode and reenter it too quickly, there's a chance that the portal will reload the Giddy Park instead of loading the correct map. It could either display the Giddy Park loading screen, or it would display the correct loading screen for the map/game mode but then return you to Giddy Park after it finishes loading.

Unable to Join Group

If the game takes too long to join a group, or if it fails and you immediately retry to join it, it may result in the game not allowing you to join, albeit with no error message being displayed. The only solution is to restart the game.

Bot Building Glitch

Sometimes above the bot building station you will see a hammer symbol glowing yellow even when the station is occupied. You can hold the build button, until build menu appears. When you choose the bot you want to build, it will not be built because the bot building station is already occupied as stated earlier, however you will still get 10 XP for building a bot. Proof

Blank Private Play Menu

If your connection is unstable or slow enough, there's a chance that the private play menu will be briefly blank. You can open the private play portal during this state, but attempting to enter it will simply crash the game. Therefore, you shouldn't open the portal until the menu shows up.

Player Character Disappearing

This glitch seems to occur only on the Switch version. On some occasions, your player character will suddenly disappear along with the HUD, leaving you with nothing but a non-interactable camera. This appears to be caused by the server removing you instead of the backfilling AIs from the lobby, although its exact mechanism is unknown. You will need to restart the game once this happens.