Desktop and system terms
Before a game is worth choosing, it has to run. This guide covers the words that describe what a desktop game needs, what it installs and why two computers with similar badges on the box perform very differently.
Desktop distribution is a specific arrangement, not a default. A desktop-only title ships a client compiled for Windows, macOS or Linux, expects a keyboard and mouse or a connected controller, and assumes a graphics processor with its own memory. A sign-up page opened on a phone may accept a registration, but the game will not run there, and no amount of browser trickery changes that. Where a game's material says desktop only, it is describing where the client executes.
Client, launcher and patcher
The client is the installed program that draws the game and talks to the publisher's servers. The launcher is the smaller application that installs the client, applies updates and signs an account in. Many players use the two words interchangeably, which is harmless until a support article distinguishes them: a launcher problem and a client problem have different fixes, and the instruction to reinstall one is not an instruction to reinstall the other.
Patching happens through the launcher and is usually incremental, downloading only what changed. Two consequences follow for Australian connections with data limits. A major update can still be large, because an engine change can invalidate most of the installed files; and a launcher left running will patch in the background, at whatever time the publisher releases the update. The setting that controls that behaviour is normally in the launcher's own preferences rather than the game's.
Minimum and recommended specifications
| Published as | The promise | Usually unstated |
|---|---|---|
| Minimum | The game starts and runs on this hardware. | At which resolution, at which settings, and at what frame rate. |
| Recommended | The game runs well on this hardware. | What well means, and whether it was measured with other applications open. |
Neither figure is a guarantee, and both are revised between major updates. The reliable version is always the one on the publisher's own system requirements page at the time of installing, which is why this site does not reproduce requirements for any title: a number copied here would be wrong within a season.
The hardware words that matter
- Graphics processor (GPU)
- The component that renders the image. In most competitive desktop games it sets the ceiling on frame rate at high settings.
- VRAM
- Memory on the graphics card. Texture quality consumes it first. Exceeding the available VRAM produces stutter and hitching rather than an even slowdown, which is why dropping texture quality one step often fixes a problem that raising other settings cannot.
- Frame rate
- Frames drawn per second. Consistency matters as much as the average: a steady rate feels better than a higher one that fluctuates.
- Draw distance
- How far away objects are still rendered. Lowering it raises frame rate and, in games with long sight lines, changes what a player can see and react to.
- Input lag
- The delay between an action and its result on screen. It is produced by the display, the client and the operating system, and it is distinct from network latency, which is covered in multiplayer and matchmaking.
- Storage headroom
- Free disk space the launcher needs to unpack an update. A drive with just enough room for the installed game will eventually fail a patch.
Operating systems and what support means
A publisher supporting Windows, macOS and Linux is making three separate commitments, and they are rarely equal. Windows usually receives the primary build. A macOS build may lag behind on features or run through a compatibility layer. Linux support ranges from a native client to community-maintained compatibility with no support commitment at all. The distinction that matters is whether the publisher will accept a support ticket for that platform, and that is answered on the publisher's support pages rather than by the presence of a logo.
Settings worth changing first
- Set the resolution to the display's native value, then reduce quality settings rather than resolution. A non-native resolution costs sharpness everywhere, including in menus and text.
- Drop texture quality one step if the symptom is stutter rather than a low but steady frame rate.
- Turn off motion blur and depth of field. Both cost performance and both hide detail that matters in a competitive match.
- Check whether the game offers a colour-blind mode, a subtitle size control or a reduced-motion option. Accessibility settings are frequently present and rarely signposted.
- Cap the frame rate slightly below the display's refresh rate if the machine runs hot. A capped, steady rate is more comfortable than an uncapped, fluctuating one.
Downloading safely
A game client is an executable with broad access to the machine it runs on, so where it comes from matters. Download from the publisher's own domain or a major distribution platform, never from a mirror found through a search advertisement, a forum link or a video description. Fake installer pages that imitate a publisher's launcher are a recurring scam pattern, and they can be reported to Scamwatch. General guidance on protecting a home computer, including on updates and multi-factor authentication, is published by the Australian Cyber Security Centre.
Two habits cover most of the risk: type the publisher's address rather than following a link from an unfamiliar source, and treat any page that asks for account details before a download as suspect.
Input devices and comfort settings
Desktop games assume a keyboard and mouse, and most also accept a controller. The distinction that matters is not which is better but which the game's interface was designed around: a title built for mouse aiming will usually provide controller support that works without being equal, and a title built for a controller will feel indirect with a mouse. The game's own control settings page is the honest answer, because a game with full remapping and separate sensitivity curves for aiming and turning was designed with both in mind.
Remapping deserves a few minutes at the start rather than a month in. Keys that are used constantly should sit under fingers that rest naturally, and any action that is held rather than tapped should be reachable without moving the hand. Games in this category frequently allow a toggle-versus-hold choice for aiming, which is the single change most likely to reduce hand strain over a long session.
Accessibility options are worth looking for explicitly, since they are rarely advertised on a store page: colour-blind palettes, subtitle size and background controls, a reduced-motion or camera-shake setting, and interface scaling for high-resolution displays. Where a game offers them, they are usually in the same options screen as the graphics settings and switched off by default.
Patch notes, and why they are the only reliable record
Patch notes are the publisher's own statement of what changed in an update. They are the only reliable source for balance changes, because a community discussion of a change is a description of how it felt rather than what it was. For a player returning after a break, reading the notes for the intervening updates in order explains more than any guide can, including this one.
A practical reading habit: skim for the words removed, reduced, increased and now, which is where substantive changes cluster, and ignore the top section, which is usually the marketing summary of the season.
Quick answer
The launcher installs and patches; the client runs the game. Minimum means it starts, recommended means it runs well, and neither is a promise. Stutter usually means VRAM, not a slow processor. And the publisher's own domain is the only sensible place to download from.