Patches, Game Builds & Error Terms

By Treesz · Updated Oct 12, 2026

Every game you play exists in many versions at once: the one on the disc, the one the studio patched an hour before launch, the one only testers can open, and the one running on your PC right now with a memory problem nobody has noticed yet. This glossary covers the words used for those versions and for the things that go wrong with them: day-one patches, dev builds, tech demos, crash logs, runtime errors, launch commands, memory leaks and random seeds.

Some of these are release terms you read in news and patch notes. Others are troubleshooting terms you meet in an error window or a support thread. Each entry says what the term means, where you run into it in real games and what you can do as a player. The table comes first; the explanations follow in the same order.

Term	What you notice	Who it concerns	What to do
Day-one patch	A large download on launch day, even with a disc	Everyone who buys at launch	Pre-load if the store offers it, read the patch notes
Dev build	A version with debug text, test maps or a "not final" label	Testers, leakers, curious players	Treat as unfinished; do not expect support
Tech demo	A free showpiece that is not a full game	Anyone curious about an engine or a console	Use it as a benchmark, not as a preview of gameplay
Crash log	A text or dump file written when the game closes by itself	Anyone reporting a crash	Find the file, attach it to the support ticket
Runtime error	A pop-up with a code or a missing DLL name	PC players	Repair files, install runtimes, update drivers
Command line	Text such as `-windowed` in a launcher field	Players who want to change start-up behaviour	Add only options the game documents
Memory leak	The game gets slower and slower the longer you play	Long sessions, open-world and MMO players	Restart now and then, report the pattern
Random seed	Two players get exactly the same "random" world	Roguelike, survival and speedrun communities	Share the seed and the game version

Day-one patch

A day-one patch is an update released on the day a game launches, or just before it, that players are expected to install before they play. It exists because of timing. A game is declared "gold" when its build is finalised for manufacturing and certification, which happens weeks before the shelf date because discs have to be pressed and shipped. Developers keep working during that gap, so the team ends up with a better version than the one on the disc. The day-one patch is the difference between the two. When it is released a few days ahead of launch it is sometimes called a day-zero patch.

The practical effects are easy to feel:

A download you cannot skip. Even a physical copy may need several gigabytes before the game starts, and on consoles the update is often mandatory.
A game that is not the one in the reviews. Reviewers usually play a pre-release build plus the day-one patch, which is why a review can describe fixes that the disc itself does not have.
Slow servers on launch day. Everyone downloads at the same time, so download speeds drop even if your own connection is fast.

What helps:

Pre-load. Steam, PlayStation and Xbox let you download a game before release; the files stay locked until the official launch time. Check the store page a few days ahead.
Read the patch notes. A day-one patch usually lists known problems and fixes. It tells you in advance which crashes or progress bugs are already understood.
Do not panic if the first hours are rough. Launch-day problems are often server load rather than bugs in the patch. See online play and connection terms for how to tell the difference.

Version numbers are a separate topic: our article on game versions explains what the numbers in patch notes mean.

Dev build

A dev build (development build) is a version of a game that the developers use internally. It is not meant for release and it behaves differently from the version you buy:

It often contains debug tools: an on-screen frame counter, a console for typing commands, level-skip shortcuts, cheat menus, placeholder art and test maps.
It is unoptimised. Debug checks that are removed from the shipped game stay on, so a dev build is typically slower and more crash-prone.
It may contain features that were cut or have not been finished yet.

Players see dev builds in three ways. First, in leaks: unfinished footage that circulates after a studio's files are stolen or shared by mistake. Rockstar confirmed in September 2022 that early footage of the next Grand Theft Auto had been taken in a network intrusion. Second, in official tests that studios run with players: closed betas, technical tests, and public test servers such as the PTR (public test realm) World of Warcraft has used for new patches. Those builds are real but are labelled unfinished, and progress made on test servers normally does not carry over. Third, in opt-in branches: Steam lets developers publish a test version as a beta branch that players switch to in the game's properties.

A few rules of thumb:

A dev build is not "the real game early". Balance numbers, drop rates and even whole quests in it can change before release.
Testers are normally bound by a non-disclosure agreement (NDA), which is why you see test footage blurred or cut off on some streams.
If a site offers you a "leaked dev build" file to download, treat it as unsafe: fake game files are a common way to spread malware.

Tech demo

A tech demo is a short, polished piece of software made to show what an engine, a graphics technique or a piece of hardware can do. It is not a game: there is usually no progression, no balance, and nothing in it is promised for a future release.

Well-known examples:

Half-Life 2: Lost Coast (October 2005) was a short level Valve released free to owners of Half-Life 2 to show high dynamic range lighting in the Source engine. It was a technical showcase rather than a story chapter.
The Matrix Awakens: An Unreal Engine 5 Experience (December 2021) was a free download for PlayStation 5 and Xbox Series X and S. Epic Games used it to show a large, detailed city built with Unreal Engine 5.
Epic's 2020 real-time demo for the PlayStation 5 reveal, which introduced the Nanite and Lumen features of Unreal Engine 5, is another widely discussed example.

Tech demos are easy to confuse with other things:

Term	What it is	Is it a game?
Tech demo	A showpiece for an engine, effect or console	No
Demo	A trimmed-down version of a real game, released to let you try it	A small piece of one
Vertical slice	A fully polished short section of the game made to prove the concept	Yes, in miniature
Benchmark mode	A fixed scene that measures your hardware	No

For you as a player, the useful way to treat a tech demo is as a stress test: if it runs smoothly on your PC or console, the underlying engine runs well there. It tells you much less about what a finished game on that engine will look like, because shipping games have to fit gameplay, networking and memory limits that a demo does not.

Crash log

A crash log is a file the game, the engine or the operating system writes when the game stops unexpectedly. It records what the program was doing at that moment. Most of it is for developers, but you can read two or three lines of it and they often point to the cause.

Where to find it. Locations depend on the game and the engine:

Windows Event Viewer: open it, go to Windows Logs, then Application, and look for an "Error" entry with the game's executable name. The entry names the faulting module (the file that failed) and an exception code.
Unity games keep a Player.log file. On Windows it sits at %USERPROFILE%\AppData\LocalLow\<company>\<game>\Player.log.
Unreal Engine games usually write logs and crash reports into a Saved folder inside the game's data folder (look for Saved\Logs and Saved\Crashes).
macOS collects reports for crashed apps in ~/Library/Logs/DiagnosticReports.
Launcher-based games often have their own "send logs" or "open log folder" button in the settings or support menu.

What the common clues mean:

Clue in the log	Usual meaning	First thing to try
`0xc0000005`, "access violation"	The program touched memory it should not have	Verify game files; update the game; check RAM stability
`DXGI_ERROR_DEVICE_REMOVED` or "device hung"	The graphics driver stopped responding	Update or clean-reinstall the GPU driver; lower overclocks
Faulting module is a graphics driver file	The GPU or its driver	Same as above
"Out of memory"	RAM or video memory ran out	Close other programs; lower texture settings
Faulting module is an overlay or capture tool	A third-party overlay clashed with the game	Turn the overlay off. See in-game overlays

How to use it. When you contact support, attach the log rather than describing the crash from memory, and say what you were doing, which game version you run (see game version) and your hardware. Many studios also collect crash data automatically; that is part of what is called telemetry.

Runtime error

A runtime error is a problem that appears while a program is running, as opposed to an error found when the code was being built. For a player it means one thing: a message box with a code or a file name, and often a game that closes at once.

The message usually falls into one of these groups:

Missing runtime component. Messages such as "VCRUNTIME140.dll was not found" or "Microsoft Visual C++ Runtime Library: Runtime Error!" mean a shared library the game depends on is missing or damaged. The fix is to install the current Microsoft Visual C++ Redistributable (both the 64-bit and the 32-bit version, because some games need both). Older games may ask for DirectX runtime files such as d3dx9_43.dll.
Application unable to start correctly (0xc000007b). Often a mismatch between 32-bit and 64-bit components, or a damaged runtime. Reinstalling the redistributables is the usual cure.
Damaged game files. An update that stopped half-way or a failing disk can leave a file unreadable. Use the launcher's verify or repair command: "Verify integrity of game files" on Steam, "Verify" in the Epic Games Launcher, "Scan and Repair" in Battle.net.
Unsupported hardware or outdated drivers. If the game needs a newer graphics feature than your card offers, it will fail on start. Check the system requirements, then update the graphics driver.
Security software blocking the game. An antivirus that quarantines one file produces the same message as a missing file. Look at the antivirus log before reinstalling anything.

A sensible order: restart the PC, verify game files, update the graphics driver, install or repair the redistributables, then look for the exact message on the game's support page. Write down the exact text of the error: it is more useful to a search than a description such as "it just crashes".

Command line (launch options)

The command line is the text interface of a computer. In games it matters for two reasons: you can add arguments (options) that change how a game starts, and many PC games have a developer console where you type commands while playing.

Launch options. Most launchers have a field for them. On Steam: right-click the game, open Properties, then General, then Launch Options. Arguments are separated by spaces. By long-standing convention in Valve's engines (and Quake before them), a hyphen starts an engine option, and a plus sign starts a console command that runs at start-up:

-windowed starts in a window instead of full screen, and -noborder removes the window frame.
-novid skips the intro videos in many Source-engine games (it does not work in every game).
+connect <address> joins a server directly.

Support varies from game to game; an option that works in one title can be ignored in another. Fortnite, for example, has its own list of supported options: see our guide to Fortnite launch options. Be cautious with long "FPS boost" lists copied from forums; some of the options in them do nothing, and a few have been reported to make performance worse.

The developer console. Many PC games open a console with a key such as the tilde (~), after which you can type commands. Typical categories:

Information: show the frame rate or network statistics.
Settings: change graphics or input values that the menu does not expose.
Cheats: commands such as noclip (walk through walls) or a god mode. In Source-engine games these only work on a server that has sv_cheats switched on, which is why they cannot be used in ordinary online matches.

Note the line between settings and cheating. Console commands that change your display are normally fine; commands that give an advantage in a competitive match are against the rules and can lead to a ban. See cheats, mods and bans for how studios treat them.

Memory leak

A memory leak happens when a program asks for memory, stops using it, but never gives it back. Over time the amount of memory the game occupies grows and never shrinks. Eventually the system starts swapping to disk, the frame rate collapses, and the game freezes or crashes with an "out of memory" message. The same can happen with video memory (VRAM) on the graphics card.

The signature is time. A game that runs well for 20 minutes and then gets steadily worse until you restart it is a typical leak. A game that is heavy from the first minute is not leaking; it just needs a lot of memory.

How to check:

Open Task Manager (Ctrl+Shift+Esc on Windows). On the Processes tab, watch the Memory column for the game. On the Performance tab, choose GPU and watch Dedicated GPU memory.
Play normally and look again every 15 minutes.
If the number climbs steadily, even while you stand in the same place, it is a leak. If it jumps when you load a new area and then stays flat, it is normal caching.

What you can do:

Update the game and the graphics driver. Studios regularly fix leaks in patches, so look for a mention of "memory" in the patch notes.
Lower texture quality or texture streaming settings to give the game more headroom, which postpones the crash but does not remove the cause.
Restart the game between long sessions, or return to the main menu from time to time. Leaving to the menu often frees the memory.
Close other programs, especially browsers, overlays and capture tools, which compete for the same memory.
Report it. Note the game version, the hardware, how long it took and what you were doing, and attach any crash log.

Leaks are particularly noticeable in games that are kept open for hours: open-world games, MMOs where you stay logged in, and games that are left running while you are away.

Random seed

Computers do not produce truly random numbers; games use pseudo-random generators that follow a fixed formula. The starting value for that formula is called the seed. Give a generator the same seed and it produces the same sequence of numbers every time. Games use that in two ways.

Procedural worlds. Minecraft lets you type a seed when you create a world; the same seed (in the same game version) gives you the same terrain, which is why players share seeds for good starting islands or villages. Updates that change world generation can make an old seed produce a different map.
Roguelikes and daily challenges. Games such as Spelunky offer a daily challenge that is the same level layout for every player on that day, so scores are comparable. Other roguelikes let you enter a seed to replay an exact run.

Why it matters to players:

Fair competition and sharing. A seed is a short code that stands for a whole level or run.
Speedrunning. Communities distinguish random seed categories (the game picks the seed, so luck is part of the run) from set seed categories (everyone plays the same world). Minecraft's "random seed glitchless" and "set seed glitchless" categories are the standard example.
Randomness manipulation. In some older games, players learn how the random generator advances and time their actions to get the outcome they want. This is a speedrunning technique, not a hack, and it works only in games where the generator can be predicted.
Testing. Developers use fixed seeds to reproduce a bug exactly: if a crash only happens on one generated map, the seed lets them get that map again.

Online games that care about fairness do not let the player choose the seed: the server rolls loot and critical hits so that nothing can be replayed or predicted from your side.

Four related terms have their own pages:

Game version explains how version numbers such as 1.2.3 are built and how to tell a hotfix from a major update.
Sunsetting covers the removal of items, features or whole services from a game, and what warning players normally get.
Telemetry describes the data a game sends about performance and play, and why privacy settings sometimes let you limit it.
Prologue is the opening section of a game, often doubling as a tutorial.