Follow TV Tropes

Following

Darth Wiki / Idiot Programming Video Games

Go To

There’s a word for games where the code is barely hanging together, with stupid layout, utterly unscaleable fixes and workarounds on top of workarounds. "Shipped"

There are times when even a Core i9 or Ryzen 9 processor will meet its match, and when even an amateur programmer will shake their head in disgust.

Note: Before adding any entries, consider if it would fit better as an Obvious Beta or a Game-Breaking Bug.

Advertisement:

    open/close all folders 

    Individual examples that run across various games 
  • As mentioned on the front page, computers do not have pure RNG, but instead they use something called PRNG (pseudo-random number generator). What they do instead is that they take a preset string of numbers as a "seed" and use that to generate a stream of random-looking numbers. This is not Idiot Programming because computers can't do real RNG without an outside source. While many video games rely on PRNG, there are some that use this really badly:
    • For a specific example, at least one poker site was cracked this way. Someone wrote a program that, using the programmer's knowledge of the RNG and the player's own pocket cards, could tell the player everyone else's cards as well as the future cards that would come off the deck, completely breaking the game.
    • Another example was found in a keno machine that would always roll the same sequence of numbers after each reboot since it used the same seed every time it booted up. This allowed one clever guy to win big three games in a row. Slot and keno machines nowadays prevent this by constantly advancing the seed even while it's not being played, by either incrementing the seed number or just rolling and throwing away the outcomes note .
    • RANDU, the infamous random number generator included on IBM computers in the 60s. How bad is it? Aside from the fact that every number is odd (which is bad on its own, yet easy to work around), any three adjacently generated numbers can be mathematically related into a plane (which looks like 15 planes when plotted due to modulo arithmetic).
      • And because the computer it was included with, System/360 mainframe, is widely regarded as their greatest work and was the computer of The '60s and The '70s, the generator became so widespread that the traces of it periodically surface even now, over 50 years past.
    • Sega's 1988 arcade version of Tetris uses the exact same RNG seed every time it boots up, resulting in the infamous "power-on pattern". This goes against a major concept of Tetris (randomized pieces) and allows the player to simply use the pattern to plot out their piece placements to max out the score counter in as few pieces as possible, rather than playing against an RNG seed they don't know and dealing with whatever it throws out. Of course, you need to have machine-resetting privileges or be playing on an emulator to take advantage of this.
    • Generally speaking, using the RNG to advance the RNG makes it less random, as multiple positions will end up having the same result. This mistake is common enough to have its own name - "RNG jitter". One of the programs guilty of it is NetHack, as constantly mentioned in this April Fools' Day TAS submission.
    • Spectrum computers will always generate the random number .0011291504 the first time a random number is called after booting up. This can be avoided by coding RANDOMIZE to reroll before calling a random number, but the poor quality control of the Spectrum's output means many, many programs do not bother to avoid it. It is such a cliche to see .0011291504 appear in bad Spectrum games that there are Deconstruction Games referencing it, such as RANDOMIZE RANDOMIZE RANDOMIZE RANDOMIZE RANDOMIZE RANDOMIZE RANDOMIZE RANDOMIZE RANDOMIZE RANDOMIZE.
  • Many video games tend to have unused assets, functional but otherwise dead code among other things that can only be found by data mining. Websites like The Cutting Room Floor are made to document their findings, but the question some would have is: why would developers leave them in instead of taking them out if they aren't going to be used? The answer is because it can potentially wreck the game, especially if these assets were linked to somewhere else. As a result, developers choose to leave them alone at the cost of the game being slightly larger than usual. This is not Idiot Programming by itself; there's no guarantee that everything put in the game would be used for one reason or another. Often than not, this is excused because the size of the game with unused assets packed in is often a non-issue. However, considering how fragile coding is, how removing assets can destroy a program outright and how managing space is super important, any developer who doesn't take this into account IS Idiot Programming.
  • While more of a lack of foresight than outright Idiot Programming, some games can't run properly above the assigned 30fps limit/cap to maintain the stability of a console game, especially when ported to newer systems or PC. Examples are as follows:
    • Little King's Story was made in a custom engine for the Wii, without maintainability or future usage in mind, and random parts of it relying on the game running at 30 FPS. This came back to bite XSEED in the ass when they wanted to port it to PC in 2016, resulting in a massive case of Porting Disaster. It was so bad that they had to bring in Durante, the guy responsible for putting out a Dark Souls fix patch within 24 hours of that game's release, to try and fix it. While Durante managed to make the game much more stable and optimized, he had to admit defeat when it came to making the game run perfectly at 60 FPS and praised the people responsible for the original porting for managing to simply make it run. Durante made a post about his time fixing the game here.
    • At launch, Vanquish doubled the damage players received when run above the original 30fps cap. The problem is that the PC version had no cap unless the graphics settings were raised, it was played on a low-end PC, or the FPS was intentionally capped with an external application such as Nvidia Inspector or AMD FRTC. Thankfully, this was fixed soon after launch.
    • Dark Souls II, prior to the Scholar of the First Sin edition, doubles the degradation rate of the weapon when run above the original 30fps cap.
    • Sword Art Online Fatal Bullet becomes incredibly glitchy (e.g. the friendly AI becomes less sophisticated) when not run at the assigned 30fps. Thankfully, there are in-game FPS cap settings.
    • Halo: Reach (specifically the Master Chief Collection) has stutters in cutscenes that get worse the higher the fps is. When it's capped to 60 it's barely noticeable, but when it's uncapped...
    • The PC port of Red Dead Redemption 2, while not an outright Porting Disaster by any means, contains a bizarre glitch where the time of the day and night cycle is tied to the 30fps cap of the console original. On high-end PCs, the game can run at significantly higher frame rates, meaning that the cycle can be 2x-3x faster... which means that stat-boosting items are effective for a correspondingly shorter amount of time, weapons degrade faster than normal, etc. Averted by the later patches by Rockstar, though.
    • It's very clear that the developers of Snake Pass had no idea what they were doing when attempting to make the game run on other platforms. All they did was pile on the anti-aliasing until they got it to run at least halfway decently. And the game caps at 30 FPS.
    • While Warriors Orochi 4's Jiggle Physics being reduced on the PS4 and Xbox One was initially blamed on censorship, it was later discovered that this was because they were tied to the framerate. While the Switch version runs at the intended 30 FPS, the PS4 and Xbox One versions run at 60 FPS, causing the physics to not behave properly. Thankfully, the PC version allows the player to lock the framerate to 30 FPS, making the jiggle physics behave as intended.
    • The PS2-era Grand Theft Auto games are programmed to function properly at either 24 or 30 FPS, and if you go significantly above that the physics and several other game aspects go haywire. Nevertheless, many people are unaware of this and keep asking why they can't swim properly in San Andreas. Mods exist to alleviate this, but they only fix it partially.
  • Older PC games are always programmed to base the speed they ran at from the computer's processor, with no upper limit. In most cases, this is less due to incompetence and more due to Technology Marching On due to older computers having slower processing speeds than modern ones. However, some programs run too fast on computers that were available when the game was released. In fact, this is the reason why some older computers have a "turbo" button on them - it artificially limits the computer's processor speed so these programs are playable. Here are some examples of games that somehow managed to break that:
    • The DOS versions of Mega Man 1 and 3 managed to run too fast to play on computers on the market at the time of their release due to the framerate being based on the processor of the computer playing it.
    • The PC port of Sonic 3 & Knuckles had the same issue. When it ran in windowed mode, the game's framerate was based on the speed of the processor running it, which resulted in a ridiculously-fast, unplayable game - even when the port was first released. Fortunately, playing the game in fullscreen bases the framerate on the refresh rate of the monitor, which will still usually be around the same framerate it was meant to run at over two decades later.


Game series with several examples

    Final Fantasy 
While the Final Fantasy series is lauded for its polished production values, the games are often coded in bizarre, idiotic ways.
  • There are several issues in the original Final Fantasy:
    • The intelligence stat doesn't work, running from battles (which is supposed to be based on both Luck and Level) is controlled by a combination of unrelated factors (specifically Luck, the status of the 3rd and 4th player character slots, whoever attacks 3rd, and the health of the 4th character slot), and most equipment buffs & spell debuffs don't even work. The only one that wasn't fixed in subsequent re-releases was the critical hit rate being tied to the weapon's index in the database.
    • Each character has several stats, three of which are useless. One of those stats is INT, which is supposed to be linked to Magic Power. Instead, Magic Power depends entirely on the STR stat, because the game treats all damage as... well, damage. On a similar note, the game also treats all Healing abilities as having negative damage, which means that it's entirely possible for your HP-critical party member to block the CUR3 you cast on them!
    • Elemental gear is supposed to have bonus effects depending on what they're used on: flame and ice swords would deal bonus damage to ice and fire enemies respectively, and armor would reduce the damage done by an enemy that it's strong against. This doesn't happen at all, meaning that there's nothing that sets them apart from regular gear.
    • There are also other mistakes in the code, which result in spells that should halve the enemy's evasion doubling it, spells that should increase your accuracy doubling your evasion instead, and the status-healing spell VOX (which cures Silence) can only be cast on the caster - and a character with Silence can't cast spells, rendering it useless in that scenario.
  • Final Fantasy II is almost as bad as the first game:
    • Instead of a traditional leveling and experience point system, the game has characters gain higher maximum health whenever they lose a significant amount of health in battle, and become more skilled with weapons and spells the more they use them. However, glitches in how said mechanics are implemented meant that it ends up being more efficient for players to get their characters to attack each other to gain extra health, while weapon and spell skill is determined by how many times the "attack" and "magic" commands were selected (as opposed to how many times they were carried out), meaning players can rapidly achieve Disc-One Nuke status by repeatedly selecting and then canceling attack and spell commands.
    • The ability to flee from battles is tied into the characters' "evade" stat, which has to be either reasonably close to or higher than the "evade" stat of whatever enemies they're facing in order to successfully flee. When this is combined with the game designers closing off sections of the map by populating them with enemies vastly stronger than their party, however, the end result is that, if a player ever strays into a section of the map they aren't supposed to be in, they have to sit and watch helplessly as their party is rapidly obliterated with no hope of escape.
    • Ultima is supposed to be the game's most powerful spell. However, it ends up being essentially useless due to a glitch in how the spell's damage is calculated, which results in a fully-powered Ultima almost never causing much more damage than a low-to-mid powered elemental attack.
    • While the programmers remembered to enforce Contractual Boss Immunity where the Death spell is concerned, they forgot to do the same with the Toad and Imp spells, which also act as insta-death spells in this game. This means that, once you've acquired said spells, it's possible to kill nearly every boss in the game in just a single turn. And even if you come across a boss immune to them, you can just off them with the Blood Sword, thanks to a damage-calculation glitch that causes it to be able to kill the strongest bosses in just 2-3 turns, including the final boss.
  • Final Fantasy VI is a hot mess of Game-Breaking Bug content, Good Bad Bugs that chop down the difficulty, and otherwise ignores a few key faults in its code.
    • Thanks to a programming error, the Evasion stat does not work at all, and all attack evasion is instead regulated by the Magic Block/MBlock stat. This makes the Blind/Dark debuff useless, as they work by greatly increasing a target's Evasion.
    • Relm's Sketch command is so unbelievably buggy that it can have any number of effects on your game, which include filling your inventory with items, turning a party member into a Guest-Star Party Member you're only supposed to use once, or even completely corrupting your save.
    • Sending a character into the coliseum makes them computer-controlled in a one-on-one fight against a monster, and it's a one-way ticket to Artificial Stupidity. Characters will frequently cast spells like Antidote and Remedy despite not being under a bad status effect, Mog will try to Dance even though it will never work, Terra will morph into her Esper form (if she's able) and then proceed to stand completely still until she dies or the effect wears off, and Sabin will use the Soul Spiral/Spiraler Blitz technique if he has it, which will instantly kill him and lose the match.
    • The "Vanish" spell gives a target the Clear status, which makes physical attacks always miss in exchange for making magical attacks always hit, which is what it's supposed to do. However, the line of code that says this was given higher precedence than the Contractual Boss Immunity to instant death spells, which means that almost every enemy in the game can be instantly killed by casting Vanish and then casting either Doom or X-Zone/Banish.
    • It's possible to make a party with no one in it, usually if it only has a Guest-Star Party Member in it. If you do, all you can do is open the menu to see no one's there, and as soon as you close the menu the game explosively glitches into oblivion.
    • Due to the way save points are coded, whenever the player has to control multiple parties, as long as one party is standing on a Save Point, a player can save and use Tents anywhere they want.
    • The Final Boss' ultimate attack, Forsaken, was supposed to deal its full damage to each of the party members, but was incorrectly programmed to divide its damage among all party members instead, resulting in a visually-impressive but pitifully weak attack.
  • Final Fantasy VII has multiple scenes that never play as they should because they were erroneously linked to arbitrary flags. This includes how the ability to see Aerith's ghost after her death is switched off by talking to an unrelated innkeeper in a flashback, and how a scene with Cloud and Barret discussing politics is locked away entirely by a flag that triggers when going to the back of the church with Aerith. There are also scenes that can only be accessed by having more Love Points than exist in the game, locking those out.
  • Final Fantasy XII's Scrappy Mechanic, treasure chests that generate loot based on whether or not you have a certain piece of armor equipped, is actually the result of an RNG that happened to be dependent on both which other chests had been opened by the player and the position of the Diamond Armlet item. Strategy guide writers soon figured out how the RNG functioned, which lead many to assume this was a deliberate game mechanic and making it a deliberate Ascended Glitch in the Zodiac Age remaster.
  • The PC ports of Final Fantasy XIII and XIII-2 released in 2014 are downright abysmal, likely as a result of being handled by a team that had never developed for or played games on PC.
    • Controller support is handled through a custom API rather than using the standard xinput.dll that most games do. This approach not only fails to take controller vibration into account but also hurts the game's performance if there isn't a controller connected, due to the API scanning for controllers constantly.
    • Both games perform abysmally on most hardware configurations, for multiple reasons. The main reason is that the engine handles all of its logic on a single thread, severely bottlenecking itself. Additionally, there are other issues which include but are not limited to: broken resource management that fails to take full advantage of the one CPU core running the game, poor memory allocation for HUD elements to the point that simply bringing up the minimap can cause a 20% performance hit, and a custom frame pacer that causes the game to stutter and run even worse if it can't maintain a stable 60 FPS (which it most likely won't).
    • XIII initially shipped with no graphics options, which was eventually addressed by modder Durante. XIII-2 released with graphics options, alongside a patch to add the same setup to XIII, but there weren't any more options besides the few that Durante was able to inject despite not having access to the game's codebase. Said options didn't even work as well as his mod; Playing in any resolution other than 720p would make the descriptions of scanned enemies fail to render, something multiple modders had discovered and found ways to work around well before Square Enix could've started working on a patch.
  • The 1.0 version of Final Fantasy XIV was filled to the brim with idiot programming. On launch, most computers could barely run the game at a stable framerate, much less a smooth one. Because the game engine used was optimized for single-player games and not an MMO, performance chugged heavily. There were other strange quirks like a flower pot which had as many polygons and shader codes as a player character model because the design team prioritized graphical quality over absolutely everything else. The game would lag quite often since, at the time, the servers were only located in Japan and the developers also decided to have almost everything in the game being done server-side. Simple tasks such as going through a menu, selecting a skill, or opening the map were programmed to run on the server's end. Naturally, whenever anything was affecting the server's performance, the player would feel it.
  • From about July 2018 to February 2019, Final Fantasy Brave Exvius saw heavy criticism for an increase in bugs and a slow pace to fix them. While the game ran solidly during its launch, its programming quality steeply declined as it got older. The game's coding for updates was copied and pasted from the first patch of the Japanese version, bugs and all, and these major glitches usually stayed on the Global side for up to months on end with no acknowledgment from the team, despite present solutions already existing. Daily quests were broken for a week, raid damage was bugged for a month, and the friends list, one of the most integral parts of any gacha game, stayed broken for somewhere between five months to a year. In contrast, any Good Bad Bug got fixed within the day, most infamously when the game was shut down for emergency maintenance because they accidentally made certain units redeemable a week early. The final straw was a new bug that caused players to lose all progress in multi-tiered events whenever the game crashed or was shut down in the middle of a stage, which stayed in the game for a full month. The programming (and priority on what to fix) was so shoddy that multiple popular content creators made videos calling out the developers for prioritizing money and gacha over making the game actually playable, and Gumi and Square Enix spent their monthly Q+A session in their update apologizing for it.

    Pokémon 
Pokémon may be an iconic franchise with the original games being huge in scope and put Game Freak on the map for good, the titles can still dip into the other side of the spectrum:
  • While the first game is impressive from a technical standpoint, the code of the original Pokémon Red and Green was so fragile that the games couldn't be localized into other languages. That's why the Updated Re-release Pokémon Blue was used for the international Pokémon Red and Blue, as the code is much more stable.
  • While many of the technical shortcomings and glitches of the early games can be attributed to the strict limitations of the Game Boy or oversights,note  there are some that are just plain egregious errors. Most notable of these is the 1/256 glitch that makes moves slightly less accurate than they should be. To determine if a move hits or not, the game randomly generates a number between 0 and 255. It then compares that number to a predetermined number based on the game's accuracy rate, i.e. 255 for 100%-accurate moves; if the randomly-generated number is less than the predetermined number, the move hits, and if it isn't, it misses. The mistake is in using "less than" rather than "less than or equal to", and because of that moves have 1/256 lower odds of hitting than they should. For instance, moves that are supposed to be 100% accurate have a 1 in 256 chance of missing due to the chance of rolling a 255, which is now known as a "Gen I miss".
    • The Game Boy games have several typos in the code which causes things to not work properly. In Gen I, Focus Energy is meant to multiply the Critical Hit ratio by 4, but it instead divides it by 4. In Gen II, the Love Ball is meant to catch Pokémon at the opposite gender of your current sent monster, but it instead works if the Pokémon is the same gender, and the Fast Ball is supposed to be more effective at catching any Pokémon with a chance of fleeing from battle, but only works on three of them (none of which are from the Legendary trio with a 100% chance of fleeing). A particularly amusing example resulted in the Moon Ball being exactly as useful as a normal Poké Ball in Gen II. It's supposed to be more effective when used on Pokémon species that evolve by using a Moon Stone, but because of an oversight in the code, it instead is more effective on species that evolve with a Burn Heal, which is a consumable status effect-healing item, not an evolution item.Why? 
  • The enemy trainer AI in Gen 1 has a major flaw: if it has a move that is super effective against the Pokémon it is fighting, it will always use it, regardless of whether or not the move damaged the opponent. The most infamous case of this is Lorelei's Dewgong, which will constantly use Restmove explanation  if put up against a Fighting or Poison type, which could render the game Unwinnable if you don't have any way to attack it. Yellow fixed this by creating a special check for this specific fight to prevent this from happening. Another case less likely to cause an Unwinnable state is Lance's last Dragonite, who will spam Barrier and Agility (which are also both Psychic-type moves, the former of which it shouldn't even be able to use) in a futile attempt to exploit weaknesses, which can result in a Poison-type Pokémon such as an underleveled Venomoth or even a level 3 Weedle poison-stalling the Dragon Pokémon until it faints.
  • Game Freak is infamous for their poor optimization and data management.
    • During development on Pokémon Gold and Silver, they managed to fill up all of the space on the Game Boy's cartridge without finishing most of Johto. They had to get the late Satoru Iwata's help with a data compression tool in order to complete the game. To Iwata's credit, his efforts fall under Genius Programming, slimming the game down so much that there was enough leftover space to add the majority of Kanto.
    • Battles in the 3DS games tend to lag because the console cannot handle the very high-poly models, which is handled by Creatures Inc. and not Game Freak. This issue still persists in the Switch games if you play them online, which was partly due to Nintendo's poor netcode.
    • Tons of visual assets and coding/scripts, as well as items from older Generations, remain in the code of newer games, even ones that are not or never were available in-game. When creating a game in general, reusing the same code base is a double-edged sword. From a development standpoint, it helps to speed up game creation because remaking the code from scratch takes time, especially if the game keeps the core gameplay intact (such as the Pokémon series). From a programming standpoint, however, it's jarring to see this code base be reused for several games with tons of unused content left behind.
    • Another head-scratching decision was to embed assets into the map files, meaning that each map that uses the same asset has its own duplicate of it. For example, major storyline NPCs like Lillie have multiple models in the game, each used for a certain part of the game. This is intended to improve performance (at the cost of hard drive space) on consoles with slow disk drives or slow hard drive access, but given that the 3DS uses flash memory and loads fairly quickly (and Sun and Moon are constantly reloading from the cartridge regardless), this only serves to bloat the file size.
    • Sword and Shield clocks at a staggering size of 9.5 GB (for comparison, the Let's Go games were only 4.2 GB each). While this isn't an issue if you bought the game physically, the Isle of Armor and the Crown of Tundra expansions are about the same size as the base game if purchased digitally and/or separately from the base game.
  • Starting with Gen III, the games introduced a bunch of complex algorithms and checksums that ensure things like save data aren't corrupted. It wasn't a problem when first introduced in Gen III, as the games run fine and take about five seconds to save. Furthermore, this is meant to confuse cheating devices like GameShark, with which it's possible to give Pokémon illegal moves and other things that can let the player break the game. When this was brought over to Pokémon Diamond and Pearl, however, making doing anything with the PC storage system (which includes merely opening it up) will triple the save time due to an overly secure encryption system that makes sure that every slot in the storage system isn't corrupted through a hefty checksum review.
    • For some reason, the 3DS games use these same checksums on game assets like textures, despite it being completely unnecessary. This isn't an issue in Pokémon X and Y and Pokémon Omega Ruby and Alpha Sapphire, since those games still use loading screens; the worst you'll get is a slightly longer loading screen than necessary. However, it became a major issue when Pokémon Sun and Moon rewrote parts of the engine to use asset streaming, meaning that new game assets are constantly being loaded in. This, along with the aforementioned duplicate models, is believed to be one of the major reasons why Sun and Moon is much laggier than previous games.
  • Pokémon Emerald has a flaw in its RNG system where it always starts at the value 0 due to a coding error. This causes each "frame" from the start of the game to be exactly the same. The end result: the player is left with a predictable sequence of personality values and therefore exactly what stats and nature they will get per time waiting in-game. For example, if the player encounters a Pokémon exactly 100 seconds from starting their cartridge, they will always receive this spread: Relaxed 22/12/10/10/29. Similarly, if a Ruby or Sapphire cartridge has a dead or removed battery, the game will always start its RNG at 0x5a0.
  • Replacing a dead internal battery in a Gen III game will not re-allow most time-based events to occur, since instead of assigning those events to occur after a certain amount of time has passed, they instead assign them to occur when the total time since the save started reaches a certain point, and this counter is reset every time the battery is replaced. For example, a berry planted at an internal time of 2,400 hours may take 12 hours to reach the next stage of its development, but the game measures the time passing by marking the time it is set to grow to 2,412 hours. Hacking the games is the only way to rectify this error.
  • The profanity filter introduced in Pokémon Black and White is notoriously arbitrary, blocking innocent nicknames because they contain profanity in other languages (e.g. "Violet" because "viol" means "rape" in French). This is particularly bad because some of the censored words become legal under certain circumstances (e.g. having any other character attached to either end of the word) while others don't have that distinction. In terms of it affecting the actual Pokémon, a Cofagrigus or Marshtomp, for example, couldn't be traded in English versions of Black & White unless you'd nicknamed it, and you can't revert it back to its original name unless you raise another one. X and Y made it worse by completely preventing words blocked by the filter to be used for the player's name or for the nicknames of Pokémon (there's even a Steelix available from one of their in-game trades named Thumper, and people will have issues trying to trade it online because they shouldn't be able to name one that), a problem that has yet to be rectified more than four years after their release with the debut of Ultra Sun and Ultra Moon.
  • While this has been long patched out, Pokémon X and Y had some problems when they were first released. Prior to the 1.1 patch, players saving their games in certain areas of Lumiose City (the major hub city of the games) risked booting into a completely frozen game, with all inputs rejected and various textures failing to load. A nastier example is that Game Freak forgot to encrypt the Wi-Fi communications. When this was discovered, hackers created a program to identify what moves their opponent is using each turn in a match, which some unscrupulous players promptly took advantage of. Fortunately, Game Freak caught wind of this and released the 1.2 patch to block the exploit, as well as making the patch mandatory for future online communication.
  • The companion app Pokémon Bank's anti-hacking measures are also notorious for letting through hacked Pokémon (which it's supposed to block) while rejecting legitimate ones (Pokémon from events, legendary/mythical or not, are some of the more common victims due to their movepools or special ribbons), and updates released to make it compatible with newly-released games generally don't work as intended since they don't update the existing games' databases to take into account newly-legalized species and movepool/ability combinations. When the Generation I games were released for the eShop and become compatible with Bank shortly after Sun & Moon were released in late 2016, the app would usually not correct the names of Pokémon to match the post-Gen V normal capitalization standard or add diacritics when necessary, and having a glitch Pokémon in the box would cause the nicknames of all Pokémon afterward to be shifted; and the games themselves would deem Pokémon transferred from the games and evolved into species introduced after Gen I as illegal and unable to be traded or used in battles online, along with Pokémon from older Generations caught in Safari or Dream Balls or those with their Hidden Abilities that can only be found through Island Scan in Sun & Moon despite those ones being perfectly legal in all of the Gen VI. A similar situation occurred when Gold & Silver were made compatible in late 2017, and as of February 2018, the evolved forms of Pokémon obtainable from the Odd Egg in Crystal cannot be transferred while they still know Dizzy Punch.
  • Even the spin-off games that Game Freak had no part of aren't immune to poor programming. The original Japanese release of Pokémon Mystery Dungeon: Blue Rescue Team had a really nasty bug that wiped the save data of any GBA game in the DS slot if it wasn't a copy of Pokémon Mystery Dungeon: Red Rescue Team. Since this was at the time when Nintendo hadn't yet introduced the option to offer downloadable patches to DS games, a recall had to be issued and a patched version of the game was released. The international versions thankfully carried this fix.
  • Pokémon Masters can be rendered entirely unplayable for those with a poor internet connection. If the game needs a large data download and the internet connection is slow, the game will eventually lose its download progress and start over before giving up and exiting to the title screen. There is no way to play the game without completing the download.
Advertisement:


Individual games with several examples

    Hunt Down the Freeman 
Hunt Down the Freeman is a colossal failure on every level, and the programming design is no exception.
  • When it was released, 60 GB of storage space was required to play a game that, compared to its contemporaries like DOOM (2016) and The Witcher 3: Wild Hunt, is not graphically impressive. A lot of that space is taken up by unused assets, uncompressed textures upscaled for 4K resolutions, SFM cutscenes, and the entire Source Engine SDK. Even the demo released in 2016 was included, and it's not even playable in-game. The developers later rectified this and cut down the required space to 40 GB, which is still far too much.
  • The loading times for when the game loads another part of a level can take up to two minutes. Not too bad, until you realize that the game it's based on, Half-Life 2, rarely took more than 10 seconds to load.
  • The saving system is broken and has the potential to corrupt your saves. At the time of release, the most consistent way is by quicksaving in a vehicle, which always produces broken saves.
  • The AI is a spectacular case of Artificial Stupidity. The pathfinding for allies is broken and often leads to them being stuck trying to enter the same door.
  • The developers didn't make critical allies immortal, yet also failed to take into account what would happen if one of them dies while in battle. The result is critical allies going into a T-pose and the following message appearing on-screen.
    #HL2_GameOver_Ally
  • The parkour system is already finicky to begin with, but the highlight is that, despite it being required to progress at points in the game, the prerequisite action required to do parkour (holstering your weapon) is not mapped to any keys by default.
  • And all of this doesn't include the state of the game on release, which had critical bugs like missing textures for many models, cutscenes not triggering, and requiring the console to be used just to progress.

    Jan Ryu Mon 
Jan Ryu Mon, an online Mahjong game by PlayNC, has plenty of evidence suggesting it was programmed by drunken monkeys.
  • If a cookie gets blocked from the site (most notably on the registration page), the server gives a "Fatal Error" page with a stack trace - no indication whatsoever that the problem is a blocked cookie.
  • The login only works in Internet Explorer - attempting to log in on any other browser will result in a "Please use Internet Explorer 6.0 or higher to log in" pop-up message as soon as you clicked on the username or password fields, and then repeat the pop-up every time you try to type a letter, click on one of the fields, or click the "Login" button.
  • Even though the game ran in a separate .exe file, it would give an error message on startup if the game executable was launched directly. The only way to launch it is to download the ActiveX extension from the game's site, log in, then use a button on the site to launch the extension for the sole purpose of launching the game - the extension would pass along your login information to the game, and they apparently didn't think to make the game executable ask for a login.
    • This is actually becoming a concerningly common way to handle log in "securely". Even Final Fantasy XIV and Counter-Strike Online (which uses a separate Nexon client on top of Steam itself) use a variation with an embedded IE session in a "login client" window. Try loading quite a few MMOs with your Internet connection offline and watch the fun.
  • When you log in, the game is ridiculously slow because of the eye-candy animations for every single turn. This was further exacerbated by the graphics engine, which was so inefficiently programmed that the game experienced more lag and frame-skip to show a Mahjong table with one hand moving one Mahjong tile than Touhou Project games do trying to animate 2,000 bullets simultaneously. This is often caused by graphics engines that cache nothing or very little, instead opting to re-render most or all of the screen from scratch on every single frame.
  • To add insult to injury, their server had major routing issues during the beta (and still have some as of this writing), forcing many players to go through a proxy just to connect, which also meant a lot of lag - one round could be easily half an hour, even though many other online Mahjong games can finish a round in 10-15 minutes.
  • And then there's a plethora of random crazy Game Breaking Bugs.
  • Plus the game occasionally deals a hand of 13 Haku tiles, even though there's only 4 of each tile in a set.

    Sqij! (ZX Spectrum port) 
The ZX Spectrum port of Sqij! has been described by Stuart Ashen as the worst game ever made, even worse than the usual contenders like Big Rigs: Over the Road Racing, and you won't be surprised after seeing how it's coded. This coding horror show is literally unplayable by default, and even if you do manage to get it working, the game is a constant stream of collateral damage.
  • We'd be remiss to start with anything other than the reason it's literally unplayable by default: the game's code forces Caps Lock to be on, but the game only accepts lowercase inputs, meaning you can't do anything without manually exiting the game to switch Caps Lock off.
  • The game is riddled with severe graphical glitches such as afterimages and tearing bits off the sprites. The game does not properly track the locations of enemies, so you are deemed to not only have hit them if you go anywhere near them, but also to have shot them if you fire anywhere near them.
  • The code to collect objects doesn't work at all; if you collect more than one piece of the "Enertree" (the goal of the game), the game believes you have collected zero pieces and won't let you drop any off. Technically you could still beat the game by collecting and delivering one piece at a time, but only if you have nothing else to do with your life.
  • If you enter a room with a locked door from the right, the game teleports you through the door, because it's programmed to always move you to the left when you enter such a room. Due to incorrectly reused variable names, two of the game's doors open and close constantly every time an enemy moves up or down. To add insult to injury, if you attempt to leave any room without being in the lower half of the passageway, the game crashes.
  • The game is extremely slow because it was written in Laser Basic, which uses standard ZX Spectrum BASIC for most processing. There are also some peculiar decisions made as to what should be done every frame. While there are good games written with Laser Basic, the real kicker is that the developer forgot to encrypt the game. This means that loading the game also loads the full binaries for Laser Basic. By quitting the game, you can then use this yourself and get a £14.99 software utility for free. Despite this massive hiccup, its publisher didn't take notice and released it twice - once on its own, once as part of a compilation. Due to this, distributing or owning a physical copy of Sqij! is technically illegal. The only reason a lawsuit didn't happen is because the game itself was so obscure it took several years until people finally discovered the oversight.
  • Unlike other examples on the page, Sqij! was badly coded on purpose and likely wasn't playtested. Jason Creighton, who was 15 when he was asked to port the game, was contractually obligated to make a game for publisher The Power House. After a falling out with the higher-ups (apparently due to not being given a copy of the original Commodore 64 game to work from, based on this Eurogamer article), he lazily threw together a game so bad he figured The Power House would reject it on the spot. They then published the game without looking. The game became notorious in the ZX Spectrum community, and comp.sys.sinclair's "bad game contest" used to be hosted at sqij.co.uk in tribute to it. The programmer in question later admitted the game was bad and took the whole thing in stride.

    Yandere Simulator 
Yandere Simulator is infamous for many things, and the code itself is one of them.
  • Much of the framerate issues are caused by a ridiculous overuse of if/else statements (due to YandereDev's lack of professional training in coding), resulting in very messy and hard-to-read code with almost no commenting and lots of redundanciesnote . For example, one function has a 12-line if/else block for a simple "divide by 25" calculation that should only require one or two lines of code. This leads to the game having to labor through many unnecessary instructions every time something happens, causing even high-end PCs to have ridiculously low framerates whenever many characters are in the same place.
  • Another infamous example of amateur coding in Yandere Simulator: the game has a large number of different states that the player can be in. Instead of using a state machine or set of state machines to manage this, which is commonly used in other games that have a large number of states, the game instead has separate variables for every single state the player could be in. This means that the program has to allow for any combination of states, even combinations that are impossible to happen in-game without modding. For example, in order to check if the player character can start an action, instead of checking if the player's merely in an idle state, the game has to check that every "non-idle" variable is false.
  • Additionally, instead of calling the GetComponent function once and storing the component data in variables, the code calls it every time the game retrieves a piece of data that should already be in memory. As you can imagine, this is absolutely terrible for performance.
  • In general, the code is needlessly complicated because of a lack of more advanced programming methods. Abstracting the code would greatly reduce the number of calculations the game makes — especially in its update function that gets checked every frame — and thus improve the game's framerate and performance.
  • Many of the files aren't optimized well for their size. For example, the highest poly object in the game is a toothbrush - which ended up being a stock asset that YandereDev used without modifying the mesh.
Advertisement:


Individual games with their own examples

Even the most competent and not so competent games can have a mistake or two.

  • Big Rigs: Over the Road Racing. It's an obvious pre-alpha build of a game, with no collision detection, no AI, and some incredibly bad physics (for example, you can go as fast as you want - Warp 9000, if you have the patience - but only in reverse). Despite being obviously an alpha, the creators tried to sell it as it was anyway.
    • In one of the strongest cases of "why bother?" in history, they added AI in a patch... which causes the truck to drive in a fixed course at a rate of 1 mph and stop short of the finish line. Why? Well, the opponent stops because it has finished the race, but there is no loss condition in the game. That's right, the game simply doesn't allow you to lose.
    • Something in the game's code causes it to be a severe memory vampire - it uses half the available RAM when it's running. No one knows why - lord knows nothing in the game itself needs anywhere near that amount.
  • Sonic the Hedgehog (2006) is an Obvious Beta - probably the most infamous example from a AAA-publisher - that's rightly criticized for all manner of issues, but probably the biggest complaint is its Loads and Loads of Loading, particularly in the hub worlds. This is because the game loads the entire hub world whether it's needed or not, even when you're already in the hub world.
    • To give you an idea of how ridiculous the loading could get, talking to an NPC would cause the game to reload the entire hub world from the disc - even though you were already in the hub world. Then once it's finished, the NPC would speak a single line of dialogue, and then it would load the entire hub world again. This is only subverted on one of the missions in Shadow's story, as you are given the instructions first, and then it loads once. You'd think they would make all the missions like this to bypass the very ludicrous and frequent load times.
    • This issue is demonstrated well during one of the boss fights - one bug allows you to explore the whole hub world, even though only a small portion of it is used in the fight. Sure, the textures for certain locations won't load, but the coding will.
    • Thanks to a typo in one of the game's scripts, Sonic's energy meter never drains like it's supposed to. This allows you to infinitely use many of his abilities, breaking the game wide open.
  • Action 52 for the NES is already a masterpiece of broken game design, but one of the key factors for some of the glitches that can happen in the game is the mapper in the cart, not just in the coding. Action 52 uses Mapper 228, which is unique as it's similar to the ones found in most bootleg multi-carts. Every game made for the NES has different types of mappers, and some of them have their own coding that can pull off some effects - like in the Japanese version of Contra, there's snow blowing in the mountain level, which was removed in the international versions because Nintendo didn't allow third-party developers outside Japan to manufacture their own cartridges with custom mappers. If you were to use a mapper, you need to be aware that the console can only read information from it in a specific way, or else you'll run into problems. Even then, it's not guaranteed to work because, for the most part, the NES isn't made to read unlicensed mappers, especially if you were to program something in a certain way that the NES couldn't handle. One notable example regarding this issue is that Alfredo and the Fettucini and Jigsaw always crash when you try to load them normally, even though most games on the cart start just fine. Why is that?  Of course, Action 52 is already infamous as it is for boasting so many games in one cartridge, and not a single one of them got past Obvious Beta or is even considered acceptable for alpha standards.
    • The mapper issue is the same reason why the unreleased Cheetahmen II stops at Level 4, as it uses the same cart as Action 52. While this is fixed in unofficial patches and the still-buggy re-release, if you own the original, you need to fiddle with the cartridge upon inserting it into the system so it'll boot up the inaccessible levels.
  • The Tetris: The Grand Master clone Heboris - specifically, the unofficial expansion - has more or less died out, because attempts to peek into the source code, much less make any further modifications, have proven futile due to the game being a messy hybrid of a gaming scripting language and C++.
    • On a related note, there were a handful of genuine C++ ports of it. However, the MINI version (which allows for "plugins" to define additional game modes and/or rotation rules) is the most commonly used version, and the way it works pretty much inhibits any attempt at porting it entirely to C++.
  • Zero Gear, a rather forgettable Mario Kart clone, isn't problematic in and of itself... but the nature of its Steam integration in 2010 allowed it to be used to play any Steam-locked game you wanted, without owning the game. This was most notably used by hackers to bypass VAC bans: just start a new account, download the Zero Gear demo, and copy the files over. This has since been patched, though.
    • The same method was used by various crackers including the now-arrested Voksi (one of the infamous crackers who boasted of capabilities to play online with pirated games and tricking Denuvo instead of removing it) but using a different game to bypass, which is Space War, a hidden to normal user game created to demonstrate aspects of the Steamworks API for developers.
  • Sometimes, Dungeon Fighter Online gives you a broken page showing on the launcher, saying that the navigation to the page was canceled. Since the entire program is based on Internet Explorer, even if you use the Firefox plugin made by users at DFO Nexus, it won't access the page, giving most of the time a timeout error. The worst part, however, is that it could not only break the login page, but a bug regarding SSL certificates could show you the login to pages that are not from Neople, such as godaddy.com or datameer.com. Fortunately, this stuff is fixable by resetting the router.
  • Indie game developer and utter egomaniac MDickie used to host the source code for many of his games, including the infamous The You Testament. By looking at the code, you discover for instance that some "exit program" functions work by deliberately crashing the game.
  • Death Trap is already an infamous point-and-click horror game, but one of the more notorious aspects about it is how the game works. In ActionScript 2 note , there are two commands called "gotoAndPlay(frame number)" explanation  and "gotoAndStop(frame number)" explanation . These commands are meant to be used for really basic stuff, like buttons in menus; they're not meant for more complex stuff like, say... movement buttons in point-and-click games. You can guess that the author used them because of how simple they were. Since these two commands work with the main timeline, it's impossible to make a traditional point-and-click game using this setup without making it really linear. And that's exactly what the author did - he made the game really linear.
  • Back in the days of DOS and Windows 9x, many games (such as the PC version of Slave Zero, as Lowtax discovered in one of the first articles he ever wrote for Something Awful) were hard-coded to assume that the CD-ROM drive was "D:", rather than actually bothering to check with the OS to see that this was the case. If you had more than one hard drive or had your disk partitioned - which a lot of people with >2GB hard drives had to do prior to Windows 98 arriving on the scene - you were generally out of luck unless you could either edit the game's configuration files or find a No-CD patch.
    • Ubisoft apparently decided to resurrect this little relic of the 90s with Assassin's Creed: Unity and Assassin's Creed: Syndicate, which will crash on bootup if they're installed anywhere other than the C: drive. It is possible to get them to work while installed on another drive, but requires copying several files and creating symbolic links to the C: drive.
  • The developers of the Anno Domini series need to be slapped with some basic GUI guideline books. For example, the first game would only save after you hit the Save button, but not after naming the save game. It would also completely remove the game directory on uninstall, including save games and settings. Anno 1404, released in 2009, still assumed that there would be only one user and that this user would have admin rights.
  • The installer for Duke Nukem Forever seems to have been programmed by someone with an "everything but the kitchen sink" mentality. Not only does it install a bunch of applications and frameworks that the game doesn't actually use, but it installs the AMD Dual-Core Optimiser regardless of whether your CPU is multi-core or even made by AMD.
  • EVE Online had a stellar example of what not to do in programming with the initial rollout of the Trinity update. Eve had a file called boot.ini that contained various parameters... but it's also the name of a critical system file stored in C:\. A typo in the patch caused it to overwrite the version in the root directory, not the game's folder, resulting in an unbootable system that had to be recovered with a rescue disk. This is the exact reason you never name your files after something that already exists in the OS, and the file in question was renamed start.ini.
  • Valve took this Up to Eleven by making its Linux Steam client delete all files on the machine it's running on if its directory is changed.
    • To make matters worse, Steam's uninstaller also deletes everything in the folder it's on.
    • When adding a game library that already has games on it, Steam may delete the entire thing and start over. Even if you have all your games on it.
  • Myth II: Soulblighter had an uninstaller bug that was discovered after the game had gone gold. If you uninstalled the game, it deleted the directory in which the game was installed. Additionally, it was possible to override the default install settings and install the game in the root directory of a given drive. Fortunately, only one person suffered a drive wipe as a result (the person who discovered the bug), and they actually replaced the discs after the copies of the game were boxed, but before the game was shipped. Still, it was a fairly glaring blunder.
  • Pool of Radiance: Ruins of Myth Drannor also had an uninstaller issue, except the bug was discovered after release, it didn't just tamper with folders but apparently ruined the registry as well because the uninstaller tried to delete the wrong registry values - which belonged to Windows 9x at the time - and system DirectX files too (proper uninstallers doesn't touch system files, even if they installed anything there to make the game work) and according to a few who played the game and were affected by this bug, it happens on top of another bug that renders the game itself unwinnable and unplayable. The update at the time that claimed to fix the bug instead told buyers to copy the contents of the installation disk, and use the fixed installer provided by the patch.
  • The uninstaller for early betas of Realm of the Mad God's Unity version would delete all files in the folder containing the game's folder (for example, if the game was installed in C:\Program Files\Rot MG, the uninstaller would delete all of the Program Files), which almost invariably would lead to unrelated files being deleted or worst case scenario the entire PC being bricked.
  • Space Empires V, unlike all its predecessors, is notorious for being a resource hog, bringing even the mightiest of PCs to their knees, despite running only on DirectX 8:
    • The battle replay files generated by the game, instead of storing "Ship A shot at ship B and hit it for 15 damage to the armor.", stores "Ship A fired bullet X. 50 milliseconds later, bullet X has moved a few pixels. After another 50 milliseconds, bullet X has moved a few more pixels. Repeat ad infinitum. Bullet X hit ship B for 15 damage to the armor." Thus, battle replays are frequently in the tens of megabytes - per turn!
    • Every time you load the ship list screen, the game loads into memory all the data about all the ships in the game, regardless of if it is actually going to be used in the list's current view mode, delaying the screen's loading by upwards of a second. Fortunately, you can disable the loading of some of the larger bits of data, such as order queues, but then you can't see it in the list when you bring up the views that use it...
    • Processing a turn for a multiplayer game when the game is set to fullscreen mode is much slower than processing the same turn when the game is set to windowed mode, in which the game doesn't bother drawing anything but just processes in the background. Surely rendering a progress bar can't be that taxing? (In fact, everything is slower in fullscreen mode for some reason... isn't that kind of backward?)
    • The game has a scripting language that you can use to write random event and espionage scripts... but the language is horribly broken in the way it handles the order of operations. Calculating 5 + 3 × 4 will give you 32, not 17 - but that's just the tip of the iceberg. Somehow you can manage to take 1, then repeatedly subtract and add 1 from it alternatingly, and wind up with any negative number you want, simply by repeating the subtraction-addition cycle the right number of times!
  • The graphics engine for Need for Speed: Most Wanted (2012) literally cannot run above 30FPS without massive framerate drops. The issue can't even be explained by a correlation to the number of objects present on-screen, as this even happens in the loading screen. This was discovered by people who noticed that locking the framerate to 30 in the PC version's configuration file eliminates the gratuitous slowdown that the PC version of the game is known for. Generally, games being locked to certain framerates isn't Idiot Programming, as some games were deliberately designed to run with certain framerates in mind, which means that trying to change it to any other framerate (like 60FPS) would normally cause the game to run at double speed and have screwy physics (among other glitches). Here's the catch: the game's graphics engine is a modified version of the same engine that powered the last Criterion NFS game, Hot Pursuit (2010), which could run perfectly fine at an uncapped framerate. Need for Speed: Rivals also runs terribly and barely reaches 30 FPS in systems that should've been exceeding the recommended system requirements at the time. It makes you wonder how a company in charge of a big-budget racing game series modified an existing, completely proprietary graphics engine in such a way that they accidentally broke the engine.
  • Welcome to Ponyville was a relatively short My Little Pony: Friendship Is Magic visual novel, and yet it was over a full gigabyte in size. This was due to the fact that the programmers appeared to have no knowledge of data compression: for example, a brief audio file for a closing door was over 32 MB (with several minutes of silence to boot). Some have estimated that if the audio and sprite files were properly compressed and trimmed, the game could have been 60-90 MB.
    • To make matters worse, after one reviewer criticized the game's technical flaws, they proceeded to block his social media accounts so that he could no longer contact them and refused to take any advice from other programmers. Some suspect that their shutdown was not due to hackers like they claimed, but embarrassment after an unofficial 5MB Flash port was released on the internet.
    • Even worse, a lot of the files in the game were unused. Every single folder has at least one file that's never called in the game. While it's normal for games to have unused content, the issue is that these textures weren't scaled to run in a game with a 640×480 resolution, along with them being huge in size. Considering the quantity of these files, this further compounds the reason why a game of this type was so unusually large.
  • The original PlanetSide, a 2003 MMOFPS with up to 111 players on each of the three empires fighting on each individual 20×20km continent, handled everything clientside (thus "Clientside" still being a Fan Nickname for the game), with the game only checking up with what the server knows every couple seconds, which caused a significant amount of the gameplay to be devoted to exploiting the hilariously bad netcode (for example, "ADADA" strafing relied on the game not realizing when players shift their strafing direction, causing them to teleport from side to side on other players' screens). Because everything was clientside, the game was also one of the easiest MMO games to hack, with common hacks including warping all players on a continent to stand directly in front of you (on your screen) and kill them, causing players from across the continent to spontaneously fall over dead, or enabling a hack to disable weapon cone-of-fire, which would result in sniper shotguns and Gatling guns that could pick off players from a thousand meters out. Even without hacks, the game was pitifully easy to exploit - players could stand somewhere safe, unplug their Ethernet cable, then run around the battlefield knifing enemy players to death. Once the player was happy with how many kills they got, the player could then plug the cable back in and bask in huge amounts of XP as half the battlefield suddenly dropped over dead (this exploit was eventually fixed by locking the game's controls if the server didn't respond for a few seconds). For a long time, having a certain type of dual-core processor would cause the game to run in turbo mode, causing vehicle and players to move and fire several times faster than normal. Thankfully, Planetside 2 uses much more serverside authentication, which has fixed almost all the issues with the first game's idiotic netcode.
  • The initial release of the Android port for the seminal SNES RPG Chrono Trigger was nothing short of a disaster. It was incompatible with many then-popular contemporary devices like the Samsung Galaxy S3, which easily could've ran the game, and threw in extremely aggressive always-online DRM that crashed the game the moment the phone went offline, changed networks, or even recieved a call. While this form of DRM isn't uncommon on mobile games, most at least give some mercy window. It was also incompatable with the Android 4.3 update, which was released the same year as the port - this took Square-Enix a full year to fix. The port was replaced in 2018 with an improved one based on the then-recent (and admittedly itself not well loved) PC port, and it was semi-generously given out for free to current owners. While feedback was still mixed, it was at least seen as a big improvement.
  • The initial rollout of The Witcher had atrociously bad back-end code. This is best seen when upgrading to the Enhanced Edition, as despite the latter adding no small amount of content, the same computers loaded as much as 80% faster than before. That's the difference a little optimization can make.
    • Playing Poker Dice in the first title is heavily prone to crashing the entire OS, to the point where it forces a reboot.
  • The Sims 2 had its corruption trigger be deleting a Sim or family, a feature that's more than easy to access. Even modders can't fix the problem. Worse still, some of the premade families that ship with expansion packs are inherently corrupted (although this can be rectified by replacing the Sim Bin template for those families with an empty template made by modders).
  • The Sims 3 is known for having a large number of expansion packs... and for their horribly wasteful installation method. Every time you install an expansion pack, another copy of an identical set of help files (in all languages) is installed on the machine. Plus, if you uninstall The Sims 3, it removes the majority of the expansions' content - but not the extra help files, for which you must run the expansion pack's uninstaller.
    • The game's engine itself was reportedly so broken that it made Bethesda games at launch look perfect: there's a lot of game-breaking bugs that are only fixable via fanmade tweaks, and an FPS limiter on high-end hardware is necessary to prevent the system from overheating due to the lack of an internal FPS limiter.
  • Splinter Cell: Blacklist is plagued with issues, such as poor multiplayer support because people can't seem to connect to one another (and everything goes through Ubisoft's infamous UPlay service) and where the game's saves are stored. You would think if you regularly back up your saves, that they would live in the My Documents folder or the App Data folder. Nope, they live where UPlay is installed, which is usually in the Program Files folder. And to make matters even worse, the permissions for the saves folder are left open to anyone, which wouldn't be a problem... if you don't consider everything in Program Files requires admin privileges to write files into.
  • The notoriously-bad but long-gone Super Mario World Game Mod Super Mario Superstar 1 has a bizarre case of this in the final battle. Not only does the final boss fail to do anything (in fact, nobody can figure out what it was supposed to do) and make it Unwinnable by Mistake, but via some absolute miracle of shoddy programming... the boss' graphics glitch if you enter its room through one door and not the other. As in, you go through one level ID and it appears correctly, you go from another level ID and the graphics are glitched tiles.
  • Speaking of resolutions, the PC version of Deadly Premonition (which is amusingly named the "Director's Cut") is such a bad port that the game has only one possible resolution to be played at: 1280×720. While this is High Definition, even the lowest-quality LCD monitor has a native resolution bigger than that, and any CRT monitor has a different aspect ratio. The game was released in 2013, too, so we weren't that dated on the monitor department. Fortunately, because it's a PC game, modders were there to do what developers couldn't (albeit Version 0.9.5 of the mod causes a lighting glitch that isn't in the previous version).
  • Call of Duty: Ghosts is apparently a sloppily-developed game. It weighs in at a hefty 30GB and requires 4GB of RAM (8GB recommended). You'd think this game would be amazing on all fronts... until you find that the game is rather bloaty, will happily eat your RAM (it even stutters on the loading movies after the level is done loading), and looks no better than previous installments on the highest settings. Compare this to the Trope Codifier for Tech Demo Game Crysis from just six years prior, which runs just fine on the recommended requirements (a "wimpy" dual-core processor and 2GB of RAM) and just needed a graphics card two generations later to run on absolute max settings at 60FPS. Later COD games have gotten even worse about this, as the required system specs get higher and higher for little noticeable graphical improvement - a system that meets the recommended requirements for Ghosts, and will still struggle to run that game at high settings, is barely at the minimum requirements for Black Ops III, and will constantly crash trying to run the game unless the settings are so low that it looks worse than the first game from 2003.
  • The online play in Meteos Wars seems to have forgotten about lag entirely. As a Falling Blocks Puzzle Game, it only needs to keep track of the other player's incoming blocks and controller inputs, but it decided to keep track of the exact locations of every block as they're falling, resulting in much more lag than necessary. If the connection becomes unstable, instead of taking guesses and correcting itself later (as is seen with all other falling-blocks puzzle games with online play), it just stops the action until the signal restabilizes, or terminates the match outright if it's taken more than a few seconds. All the while, as the online play shifts between slow and immobile, the timer counts down in real-time, functioning totally independent of the game, resulting in nearly every online match ending in a time-out instead of elimination.
  • When it was announced that the PC version of Titanfall would require a massive 48GB of hard drive space, many assumed that it was a sign of developers finally starting to include visual assets that far exceed those of typical 360/PS3 ports. As it actually turned out, a whopping 35GB of the game's installation was taken up by uncompressed audio files, in every single one of the game's 20 languages. The developers' rationale for this was because they thought the audio decompression would take up too much CPU power on older and/or bargain-basement PCs... never mind the fact that any CPU which struggles with anything as simple as audio decoding probably wouldn't be powerful enough to run the game in the first place. Had they compressed the audio files and actually made separate installers for different languages, the game install would probably only be about 15GB.
  • Fargus Multimedia's Russian bootleg of Putt-Putt Saves the Zoo already has wrong voice clips for characters and nonexistent lip-sync, but when originally released the game's W32 file - which executes the game - was blank, making it completely unplayable. This was only fixed when fans stuck a W32 from the US version onto it.
  • don't take it personally babe, it just ain't your story closes by forcing itself to crash.
    • The version of Planescape: Torment on the Dungeons and Dragons Anthology collection does the same thing, which is rather odd given the otherwise fine carryover job.
  • Super Monkey Daibouken. Despite being for the Famicom, as opposed to the Famicom Disk System, it had to load regularly. And that's to say nothing of the game's battle system, which is too inconsistent to be remotely coherent.
  • Hoshi wo Miru Hito had a world map so badly programmed that the display just spat out tiles at random. The display never showed your total hit points, and the battle menu was so broken that you couldn't even access it without progressing in the story.
  • LEGO Island 2: The Brickster's Revenge is infamous for its Loads and Loads of Loading, on par with the likes of Sonic the Hedgehog (2006). The reason for this? The game prioritizes rendering the loading screen over actually reading any data. This means that for every frame that is rendered, only a single byte of information is read, which causes the game to spend an eternity loading things for absolutely no reason. The kicker? This can be fixed by changing a single instruction in the game's EXE file, which makes it read all the data before rendering a single frame, and the loading is minimized to only half a second rather than minutes on end.
    • In any game, a 3D model that is placed repeatedly is simply the same one used over and over again. Not in this game, where many reused models in the game are actually duplicate copies, wasting a lot of disk space. The grandest example of this is the asteroids minigame, where the asteroids have two variations - normally, this would require loading just four files (specifically, their model and collision files), but the game instead gives each of the 235 asteroids its own model, requiring the game to load 470 files.
  • The netcode for the original Dark Souls is infamous for being terrible. It can take upwards of half an hour to summon a friendly player, and sometimes the game thinks that you're being invaded by an unfriendly player, preventing you from exiting an area for over 10 minutes until the problem resolves itself.
    • This isn't even getting into the notorious PC port, which is less of a port and more of a straight-up emulation of the Xbox 360 version, thanks to FromSoftware having very little experience with porting games to PCs at the time. The resolution is absurdly limited and the controls are basically designed to have both hands on the keyboard at all times, which is incredibly finicky at best for a game like Dark Souls. It also initially had the much-maligned Games For Windows Live attached to it, which was eventually removed in favor of Steamworks instead.
    • Dark Souls II attempted to fix this problem by adding dedicated servers for matchmaking, which did alleviate the issues somewhat. Unfortunately, the dedicated servers are only used for matchmaking; once you actually connect everything is handled as a peer-to-peer connection, meaning astronomical lagspikes and severe Hitbox Dissonance if you happen to connect to a player across the world. The game's engine also had an odd quirk where the game's framerate actually affected the degradation speed of your weapons, for some baffling reason.
    • And it seems like From Software didn't quite learn their lesson the first time: Bloodborne's netcode is almost as bad as the original Dark Souls and has all the same issues. It also had terrible environmental optimization before patches, leading to Loads and Loads of Loading.
    • Dark Souls III had an anti-cheat software that was so poorly programmed that it would often mistake the game's actual code as cheats, ejecting customers who had literally done nothing from online play. It was so bad, in fact, that even simply switching from offline to online could trigger the anti-cheat. Fortunately, FromSoftware did eventually fix the anti-cheat and removed many of the accidental bans.
  • The netcode in JoJo's Bizarre Adventure: All Star Battle is terrible, resulting in mind-blowing amounts of lag no matter how good your connection is. This thankfully doesn't affect Campaign mode, which unlocks most of the content in the game, because that only uses the connection to look up what other players have set as their characters (the actual fight is you versus the AI).
  • Dragon Age: Inquisition was loaded with bugs from the very beginning. The most infamous among them is the notorious Patch 4, which was not only nearly seven gigabytes large but had a programming error in the Xbox One port that caused it to uninstall and reinstall the entire game (though this is also due to a glitch in how early versions of Xbox One's operating system handled patches, with said glitch also happening with patches for Assassin's Creed: Unity).
  • Banzai Pecan: The Last Hope for the Young Century is not without its problems, but none were as egregious as the palette-swap feature for its main character. Without using them, the game takes roughly 4 seconds to load. If you use any of the palette-swaps (save for her Awakened Mode), it extends the load times to nearly 16 seconds. What makes this even more bizarre is that the game can load most enemy types in many other colors without any issues.
  • Grand Theft Auto IV: The PC port was commonly cited as an example of this trope before patches were released. Disproportionately heavy performance on the most commonly available computers of the time (even high-end computers from more than a decade later have performance issues running the game at its highest settings), and a graphical settings menu that had an issue where setting the quality to low made the game run slower. True, patches helped alleviate these problems, and the game engine boasts its share of Game Mods, but the game became a textbook example of shoddy PC ports. Also, the game required the infamous Games for Windows Live on top of its own Social Club launcher, and a massive amount of tampering of the game files is needed to even run it in present Windows versions; it's horribly optimized for Windows 8 and above, which is not recommended if you want to play it via Social Club (if ever, because massive amounts of fan patches are required and none of the PC players touched the multiplayer). Although finally, in 2020, as the Complete Edition is released, the GFWL requirements and installations are removed at the cost of multiplayer.
    • It's not until some fans managed to make the game ran on Vulkan (a graphical API that didn't exist for around 8 years until GTA IV was released) that the game ran as intended in modern systems on a fresh Complete Edition installation, but even then, some of the PC options, such as draw distance, exceed what the game engine capable of, as such, raising the draw distance above 35 will make the game frame drops. Though thankfully even at those ranges, draw distance is still high, although minor texture pop-ins might happen.
    • Grand Theft Auto V, for a whopping 7 years after its release, had its multiplayer GTA Online mode's Loads and Loads of Loading mostly caused by a 10 MB JSON database of in-game purchasable items parsed in such an egregiously inefficient manner that a fan patch reduced it by 70%!
  • Saints Row 2 suffers the same thing as Grand Theft Auto IV above, though thankfully without GFWL, and while GTA IV was finally fixed with fanmade mods and patches, attempts to fix Saints Row 2 (including modding it, releasing it to GOG, and even porting it to Linux) have been a failure so far. This was later revealed to be because the PC version of the game was a third-party effort, and when their effort was revealed to be half-hearted at best, Volition fired them from the project, declared fixing it hopeless, and washed their hands of the port entirely. Thankfully, the source-code was recovered and a small group of developers decided to work on an updated version to both make the game run acceptably and integrate the DLC that was never released for PC, but time will tell.
  • When Disgaea came out on PC, it was considered a disaster on many levels due to poor performance, unresponsive controls, and spotty gamepad support. One modder decided to reverse-engineer the game and see what was causing the problems, and in the process discovered that much of the game relied on bizarre, archaic, and ancient methods of handling basic internal things like input polling, controller support, texture coordinates, and screen refreshing in OpenGL, resulting in the issues listed above.
  • The remake of Cannon Fodder recreates the game with a modern 3D engine. However, the remake takes an incredibly long time to load, even on modern fast computers, and doesn't keep loading in the background if you alt-tab out of the process. Click start, go brew a cup of coffee, lazily mix it with sugar and milk, drink it while you read the paper, come back, and if you're lucky, the game will be just about ready to start. And for all that, the graphics are really nothing to write home about.
  • Sega, with their Mega Drive/Genesis titles on Steam, finally opened up modding support for them through Steam Workshop, much to the rejoice of fans everywhere. However, it was soon discovered that for some reason, uploaded mods that utilized SRAM support wouldn't save their data... unless the mod was listed under Sonic 3 & Knuckles. And even then, it will not save all data properly if the mod's SRAM data is bigger than the aforementioned game's, as seen with Sonic 3 Complete.
  • Wildlife Camp is a PC game released in 2010 that doesn't have an option to put the game in windowed mode, one of the most basic features that a game can have. This would be bad enough on its own, but if you open up the game's options.ini file, you'll find that the game does have a fullscreen toggle - the line of code that enables the button for it to appear has just been commented out. Re-enabling the code causes the fullscreen toggle to appear in-game and work without a problem, which begs the question of why it was Dummied Out in the first place.
  • While Valve Software never really paid much attention to Counter-Strike in the first place, a few aspects of the game are just plain terribly coded:
    • Where do we start with Valve Anti-Cheat? Cheating is so common thanks to this system's failures, and most players use third-party clients with stricter cheat detection. It only scans the game files to see if a program is modifying them with no regard to what's actually happening in-game, which means that a player that's running at Super Speed across the map and getting five instant headshots every single round could easily be ignored by the Anti-Cheat and only be banned by manual reports, and a player that's hiding their cheats is nearly impossible to get banned.
    • For some reason, player models don't reflect the way the actual player is aiming, so enemies see the model snap to them incredibly quickly in a way that resembles cheating in other games, which contributes to a lot of "crying wolf" reports that make the game's banning system even more of a joke. Why Valve doesn't just simply fix this is beyond the community's knowledge.
    • The "mesh" layer that codes the bot movement in some maps is incredibly poorly generated, including bots going around obstacles that no longer exist, standing out in the open because the area is coded as "cover", and, in at least one case, failing jumps and inflict significant damage on themselves.
  • When Nights of Azure was ported to PC, the developers didn't include the option to close the game, requiring users to force-quit it from outside the program. This is one of the most basic features any game should have, yet they didn't bother to code it in. Also, if you're a keyboard user, Azure and Atelier Sophie: The Alchemist of the Mysterious Book have no options to rebind keys. If that's not bad enough, the game doesn't even bother to tell you the controls!
  • The licensed NES games produced by Australian developer Beam Software (now known as Krome Studios Melbourne) in the late 1980s were notorious for their botched renditions of well-known songs. However, this wasn't due to any lack of talent on the part of the composersnote  - for some inexplicable reason, the company's NES sound engine was only able to play music back at a tempo of 150bpm. This wasn't such an issue with the original titles the company produced, as the composers could write their music with this limitation in mind, but most of their output was licensed games for LJN Toys, meaning that a lot of familiar tunes got horrifically butchered. It wasn't until near the end of the NES' lifespan that they fixed this problem.
  • Telltale Games was so notorious for pushing out Obvious Betas of their games that you have to question whether or not they actually bug-tested them. Given that they were revealed to rush games out as quickly as possible in an attempt to turn a profit, they likely didn't.
    • Strong Bad's Cool Game for Attractive People has its share of problems. Skipping the dialogue too often in the PC versions causes the character textures to disappear, and the Wii version will freeze on Coach Z's dialogue in Extended Mode if the console's set to widescreen mode (which is the default view for it). To make matters worse, you need to see this scene to get 100% completion.
    • For whatever reason, Poker Night at the Inventory refuses to load if you have an Xbox 360 controller or something similar plugged into a USB port.
    • Never play the iOS version of Poker Night 2. It's a Porting Disaster because the game was never designed for it. There are slowdowns, random crashes, aliasing beyond belief, and it's nearly impossible to play unless you're using an iPad.
    • The Wii versions of Sam & Max: Freelance Police had a tendency to lock the cursor at the lower-right corner of the screen, which would softlock the game.
  • Undertale, being made almost entirely by one Toby Fox, has a few issues:
    • All of the RNG-based Easter Eggs were initially Dummied Out by accident. This is because Fox didn't realize that the string reading the values that triggered them was case-sensitive.
    • The game's dialogue system contains hidden "control strings" which dictate, among other things, whether to show the next line or close the current text box and continue when the "advance dialogue" key is pressed. As this Reddit post shows, the "close text box" string is sometimes used when the "show next line" string should be used instead, resulting in some lines of dialogue never showing up. This can cause some unintentionally Orphaned Setups when the skipped lines are the punchline of a joke.
    • The sequel to Undertale, Deltarune, has a much more severe error that's very similar to the one in Myth II: Soulblighter: the uninstaller of the initial release of the "SURVEY_PROGRAM" deletes the directory it was installed in instead of just the contents in the folder itself. Fox admitted this could have "catastrophic" consequences, and advised people to not use the game's uninstall tool.
  • Cartoon Network: Punch Time Explosion is a halfway decent Super Smash Bros. clone. Emphasis on "halfway". There's a ton of lazy development quirks that almost make the game unplayable: Unresponsive controls, an unfinished battle system, and an unintuitive control scheme that even veteran Smash players will find hard to get used to. There's also an infamous bug that freezes the game during one of the final levels. And instead of trying to fix the issue, the developers told everyone to just input the code that unlocks everything, which makes playing Story Mode pointless. While there are ways to bypass this bug (usually by sheer luck), it's still a problem that makes the game a textbook example of Obvious Beta.
  • The PAYDAY 2 Steam version is pretty good, stable, and is generally considered to be a great game... except for the fact that every time it updates, it doubles the game's total size without any explanation before dropping the size back to its original amount after the update's installed.
  • The Blue's Clues games by Humongous Entertainment are the only games that can't run on Windows 3.1, despite other SCUMM engine games working just fine on it. Why is this? The Full Motion Video for Steve has filenames that are too long note . If the files and pointers are shortened manually, the games run perfectly fine.
  • Initial releases of The Horde were deliberately programmed to delete save files from every other game on the system without informing the player in order to make room for itself. This was changed when the developers realized that people didn't like this "feature".
  • The PC version of Guitar Hero III: Legend of Rock has an unforeseen quirk that limits how many custom fret-charts can be put into the game. Basically, the developers decided to put a cap on how many text objects can be on a menu at a time. This cap also goes towards the high scores. An in-depth analysis of this bug can be found here.
  • Some third-party Wii games have GameCube controller support. However, some of them (such as Castlevania: Judgment and the aforementioned Cartoon Network: Punch Time Explosion) shut off all other controller methods if a GameCube controller is plugged in, even though the Wii is perfectly capable of handling both controllers at the same time. So, if you want to use a Wiimote but you accidentally left a GameCube controller plugged in, you'd be frantically pressing buttons and wondering why the game isn't accepting any of your inputs.
  • A special case goes towards the Doodle system in Toontown Online. It seemed fine at first, but when private servers arose after the game's closure, Doodles couldn't be implemented as-is because they put a ton of strain on the servers. You see, the coding for Doodles was very poorly written, and no one knew this because Disney has tons of money and, as such, had access to servers where the strain didn't matter. The problem wasn't noticed until much later on, and fans had to rewrite the code from scratch just so they could be implemented.
  • As of 2017, Fallout 4 and The Elder Scrolls V: Skyrim Special Edition are equipped with "Creation Club", where players can purchase exclusive fanmade content from the new Bethesda store service. Already controversial for essentially being proof that Bethesda learned nothing from their ill-fated attempt to add a price tag to Skyrim mods on the Steam Workshop in 2015, this one makes itself even worse by downloading all of the Creation Club files (whether you intended to actually buy any of them or not) and only making stuff you paid for usable in-game. While having to carry DLC you don't own for a single game on a console that's expected to get by with only eight gigabytes of space is bad enough, these games could reach the point where you had space requirements in the terabyte range on top of their already ridiculous system requirements. The only redeeming factor is that mods are only added seasonally (usually every six months or so) and, possibly due to the controversy surrounding the Creation Club, are much fewer than those hosted on Bethesda's own website or Nexus Mods (likely so they won't reach catastrophic space requirements until long after most companies would stop supporting a game), and their presence in the Creation Club means that Bethesda, at the very least, claims that they will all work with each other and with future updates to the game itself. That said, those updates still tend to break mods anyway, most commonly Script Extender and any mods that require it.
    • Skyrim Special Edition also has a weird glitch that causes issues with the save file thumbnails in the save/load menu. The cause of the issue is... the anti-aliasing setting being something that isn't "best" ("off" results in the thumbnail being blank, and "low" results in the thumbnail being a screenshot from a moment before the player saved).
    • One consistent criticism on the pure gameplay side of Fallout 76 is that bugs that have existed as far back as Fallout 4 and Skyrim are going unpatched because Bethesda seems to be used to letting the fans patch their games for them - and have nothing to fall back on for an MMO where the fans can't mod out old bugs.
    • Fallout 3, as ground-breaking as it was when it was launched, also suffered from issues on the PC end. Namely, the game wasn't properly coded for multi-core CPUs, which were starting to become popular at the time the game went gold. It also used DirectSound in its game engine, despite Microsoft announcing during the game's development that it would be abandoned with the release of Windows Vista, resulting in the game having stuttering music and lots of locking up upon release, particularly on new high-end dual-core PCs running 64-bit versions of Windows Vista. The worst part? When fans tried to fix the music issues via mods, Bethesda hit them with a DMCA, arguing that the mod contains licensed music (due to the fix requiring the music files to be recompressed to a different audio format). And when Windows 10 came about, it was found that the game's installer would forcefully try to install Games For Windows Live, which would then break the network stack. It took until GOG.com got the rights to fix and publish the game so it was finally playable out-of-the-box, but by then people were already soured by the whole mess. Even then, you need to buy the game on GOG, as the Steam version remains broken and abandoned.
  • There's one point in X-Men (1993) where you have to literally restart your Genesis to continue. A fun idea in theory, but the issue is that a lot of later Genesis models like the Nomad lack a Reset button entirely, and powering the system off and then on doesn't count as restarting the system. Even then, it's really finicky on whether or not it actually works; you have to press Reset long enough to where it sends the actual signal, or else the game just soft resets entirely.
  • Aliens: Colonial Marines was regarded as a poorly-designed game in general, but one of the biggest reasons was that the Xenomorph enemies suffered from some of the most broken, dysfunctional AI in any modern videogame. Years later, it was discovered that this was the result of a typo in the game's configuration files (someone misspelled "tether" as "teather") and that, when corrected, the Xenomorphs had perfectly serviceable AI that even had the occasional moment of Artificial Brilliance. While correctly-functioning AI wouldn't have saved the game from its numerous other problems, it might at least have propelled it into So Okay, It's Average territory instead of just being bad (and prompted some software companies to ask you to spell "tether" in online interviews).
  • Like most Idle Games, Hero Simulator Idle Adventures lets you purchase an in-game autoclicker to attack enemies, and lets you purchase further improvements like increasing its damage which stay with you when you start a New Game+. Unlike most idle games, these only last as long as you keep the browser tab open: merely reloading the page causes the game to remember that you purchased the auto-clicker, but doesn't actually give you the autoclicker. An update was issued that lets the autoclicker survive the page reloading, but not its upgrades (and even then it tends to stop working after a while). It also has a mechanic where you can watch ads for in-game bonuses, but these fail more often than not without giving you the bonus.
  • The Touhou Project fighting games by Twilight Frontier have very poor netcode. For one, you have to go out of your way to even get it to work (it requires you to port forward your router, which can be tedious or risky depending on what kind of router you have). Then there's the fact that it can't even handle pings that are too high, which causes it to softlock the games on a black screen and force you to close it out manually. Because of this, the Lobby system introduced in an update for Urban Legend in Limbo completely broke for people outside Japan, forcing everyone else to continue using the archaic method of directly connecting to each other's IP address. They didn't even bother fixing this for Antinomy of Common Flowers' Steam release, only adding an option for English subtitles (not that the translation is any good). They clearly anticipated people outside of Japan to buy it, so why they didn't bother fixing the online for a competitive fighting game is anyone's guess.
  • Anthem has been noted for its horrific memory leaks. The PC version often leads to even eight-core processors getting 100% usage on every core and can sometimes force your OS to reboot, while PS4 versions can not only cause the entire console to crash and force-shutdown during matchmaking but also (on rare occasions) brick the entire console.
  • The bundle edition of Baldur's Gate series (not the enhanced version) published in France by Mindscape contains the main games in French, while both expansion packs (Tales of the Sword Coast for the first installment and Throne of Bhaal for the second) are provided in their English version, which changes all of the text from French to English. note  This was obviously something they knew about before shipping since it's written (in small font) on the back of the box.
  • A lot of security pundits said you risked getting malware by downloading pirated content. However, legitimately purchased content might be hiding some nasty surprises... Here are some of the infamous but unintentional cases (not the intentional cases, like how some bitcoin-miner games infamously slipped under Steam's radar before complaints made Steam pull those games).
    • One Easter Egg that was common with a lot of Sega Dreamcast games was that if you were to put the disc into a PC, you'd find extras on it. In 2001, Atelier Marie: The Alchemist of Salburg did this, and included a screensaver. However, the person behind this idea apparently didn't scan their machine for viruses first, as the screensaver was infected with a virus called "Kriz". If the user is unfortunate enough to install the screensaver, the virus completely wipes the BIOS if the PC's clock is set to Christmas note . The game was later reprinted with a non-infected version of the screensaver, and later re-releases lack it completely.
    • In 1998, version of WarGames Defcon 1 was infected with a Trojan Horse virus called "Marburg". After installation of the game, it bloats any EXE or SCR file it can find with its own code, and infected applications will do the same. Three months later, the desktop will be filled with the Windows "Error icon", as if the PC had the measles.
    • Also in 1998, three PC magazines in Europe had their copies of the Si N demo infected with "CIH", a rather infamous worm that triggers its payload in the 26th day of a month, which will overwrites the victim's hard drive with random junk until the system crashes, and then corrupts the victim's Flash BIOS, essentially bricking the PC and putting it beyond repair (which was an unintentional effect, by the way, as the creator intended for it to test security vulnerability, only to spread outward). Thankfully, due to increasingly protected access, the worm doesn't affect NT-based (from XP onwards) Windows anymore.
      • Oddly enough, this wasn’t the first time a magazine had shipped with a virus. The July 1998 copy of PC Gamer Europe shipped with the Marburg virus on its disc. In a rather amusing twist, it's speculated that the aforementioned PC version of WarGames DEFCON 1 had the virus because one of the engineers at MGM Interactive had viewed the said infected cover disc on one of their development machines.
  • WWE 2k20 suffered from a crippling (yet hilariously appropriate) Y2K-like bug where several modes stopped working the minute January 1st, 2020 ticked in. The only way to get the game working again was to set your machine's clock back before that date, and that's only if your version of the game wasn't tied to the servers. Thankfully, this was patched.
  • The Pinball Arcade is a labor of love, a long-term project to digitize as many notable pinball machines as possible. Though a noble effort, it's pretty clear the people at Farsight Studios are pinball fans first, programmers second:
    • A lot of the stranger glitches stem from the fact that when a ball enters a ramp, loop, or another fixed path, rather than letting physics do its thing, the game will move the ball along that path once it detects the ball has reached the entrance at a sufficient speed. This results in the ball taking the routes of those fixed paths even when it's not actually there, most notably if the ball flies over an entrance or under a raised path.
    • This ball-guiding programming exists in the first place because the physics themselves are improperly programmed. Without it, the ball will occasionally and unpredictably accelerate, decelerate, go through solid objects, or fly off at angles; this happens the most in the Whirlpool in White Water, where the ball will occasionally fly right off the table, as (apparently) there's no protective glass. Oddly, the programmers seem to have taken this into account, as the game immediately provides a replacement ball when this happens.
    • A bigger issue, however, is Farsight's Skewed Priorities as far as what platforms they'll support despite them porting the game to every major platform. For some reason, they prefer the PlayStation 3, giving it the most priority with updates, patches, and DLC while every other platform - including the PlayStation 4 - either receives them months later or not at all, resulting in the PS3 version being relatively smooth and free of major glitches while everything else is a mess. This also applies to the mobile landscape in that particular OS updates, both on iOS and on Android, cause Pinball Arcade or its variants to glitch to nigh-unplayable levels while they never get fixed. Meanwhile, patches continue to be released on the mobile versions to fix minor, rarely-occurring problems while issues like there being only the sound of the flippers and a completely absent Heads-Up Display remain unaddressed years later. It's as if the programmers at Farsight assume players never update their devices.
  • A lot of games using the Unity Game Engine have a lot of performance issues (especially 3D games), to the point that games using the Unity engine yet well optimized are very few. Infamously, a mid-end machine that can run Far Cry 5 well will struggle to run 7 Days to Die without lagging.
  • For some reason, The Demon Rush has many unnecessary things in its files that add to its already bloated memory footprint. These include Netscape 2.0, printer support, Direct X 8 (when version 9 had been out for over five years), 16 different "sound not found" handlers, and the Hebrew character set.
  • Getting decent performance out of Path of Exile can be as much of a gamble as its randomly-generated loot. Some people find themselves running the game just fine on a laptop that's slightly out of date, while others with the newest parts have to contend with framerate drops and outright freezing. People on Reddit discovered that one source of the performance issues is the sound - people have reported significant improvements after disabling certain sound sources. Not muted, disabled. As in, you have to directly edit certain files in the game's folder to stop it from rendering certain sounds, because the game would still render them while muted.
    • Near the end of the Delirium league, Grinding Gear Games unveiled their beta support for Vulkan, which in place of Direct X 11 resulted in a significant performance boost across all machines capable of using it. Where things turned sour was the league that came right after it, cited by some to make the game run worse than before on DX 11.
    • Another easily exploitable issue in Path of Exile is the game handling all damage calculations server-side. Because of how the game handles it, it's perfectly possible to make a build that has so many individual calculations that the entire server crashes.
  • Until Patch 1.3.0, Crysis Remastered refused to create save files if your Nintendo Network ID contained certain characters a Windows PC would consider "illegal", such as a colon, resulting in the game crashing.
  • For some bizarre and unexplained reason, the PC version of Code Vein has a single elevator in a late-game area that takes several minutes to start moving if your framerate is above 60fps. No other elevator in the game has this problem, including another elevator in the same area, making it stand out as extremely strange.
  • Improbable Island originally stored stats in a weird way — there were database values for your total attack, defense, hit points, and your various modifiers, but no values for your base stats. On top of making it difficult to calculate anything, this proved particularly problematic when the owner wanted to upgrade the system eleven years into the game's lifetime, and he ended up having to rebuild the whole damn thing to make it do what he wanted. note 
    CavemanJoe: The analogy of this current system is an RPG character sheet where you pencil in your total attack, and then when you get new gear you rub out the old value, subtract your old gear, add your new gear and write in the new value. If you make a mistake at any point, then your math is gonna be wrong until you notice and then have to try to remind yourself where all these numbers came from.
Top

How well does it match the trope?

Example of:

/

Media sources:

/

Report