LANDFALL '89: BUILDING 90s DEATHMATCH WITH MODERN NETCODE

We did not set out to remake Quake. We set out to remember what it felt like when your ping was 200 and you still won because you read the map better than the guy with the T1 line. Landfall '89 is our answer to a question nobody in a boardroom is asking: what if a fast FPS actually respected both the past and the present — the snap-aim chaos of 1996 and the netcode standards of 2025?

This dev log is not a hype trailer in text form. It is a field report from the trenches of a small studio that refuses to ship another hero-shooter with a seasonal narrative and a guilt meter for not logging in on Tuesday.

Why "Landfall" and Why "'89"

The name is deliberate. Landfall is the moment before impact — when you commit to a jump, a rush, a rocket jump that either makes you a legend or feeds the scoreboard. The apostrophe year is not nostalgia cosplay. 1989 is the hinge: 2D was dying, 3D was being born badly, and a generation of kids was learning that games could hurt you and you would come back anyway.

We are not simulating 1989 technology. We are channeling the design intent of the era: small maps, loud weapons, readable silhouettes, and a scoreboard that tells the truth. If you die, you died. No revive drone. No "redeploy." You walk back in and earn your revenge.

The Netcode Problem (Or: Why Your "Retro" Shooter Still Feels Like Soup)

Every month someone announces a "classic arena shooter" and every month the online play feels like wrestling a ghost through molasses. The art direction is pixel-perfect. The movement is wrong. The hit registration is a negotiation between client and server that ends with both sides angry.

Old games got away with murder because LAN existed. You and your friends ran coax cable across a living room and the host machine was God. The internet was a miracle and a curse. We lived through it. We do not romanticize 150ms peeker's disadvantage. We fix it.

Landfall '89 uses a rollback-style prediction model tuned for projectile and hitscan hybrid combat. That sentence will make three people happy and everyone else reach for the back button, so here is the plain English:

• Your shots register when they should. Not when the server gets around to it after your opponent has already rounded the corner.
• Movement stays crisp. We cap simulation at a fixed tick rate and interpolate visuals — no "smooth" camera lies that hide desync.
• Lag compensation has limits. We do not rewind you into walls. If your connection is garbage, you will lose. We will tell you your connection is garbage. Radical honesty.

Netcode is not a feature you patch in at launch. It is the game. Everything else is wallpaper.

No Lobbies. No Excuses.

Modern matchmaking treats players like cattle. Queue, load, wait for seven strangers to finish customizing their gun charms, sit through a cinematic, play one round, disband. Repeat until your soul files for unemployment.

Landfall '89 uses a server browser with filters that work. Ping. Map. Player count. Mod flag. Password. You pick a room like an adult. You stay in that room like someone who came to play. If the host leaves, migration hands off to the next stable peer — we spent two months on that alone because we have been burned by "host quit" messages since the days of Gamespy.

For solo players who just want to shoot, quick-play exists. It drops you into a populated server in under ten seconds. No battle pass popup. No "did you know you can equip a skin?" tooltip. You spawn. You fight.

Weapons: Loud, Legible, Unforgiving

We prototyped forty-two weapons. We kept eleven. The cut list hurt, but arena shooters live or die on whether a new player can tell what killed them in the kill feed without opening a wiki.

Current roster philosophy:

1. Every gun has a silhouette. You know a rocket launcher from across the map.
2. Reloads are commitments. No tactical slide-reload-cancel nonsense. You picked the shotgun. Live with it.
3. Power weapons spawn on timers you can learn. Map control is a skill, not a loot table roll.

The nailgun-analog — we call it the Riveter internally — is the most controversial weapon in playtests. Gen X testers love it. Younger testers say it "feels unfair." Good. It is supposed to reward aggression and punish campers who treat every corner like a rental property.

Maps: Designed for Flow, Not for Screenshots

Our lead level designer still prints top-down layouts on paper and walks the office with a red pen. We have three shipping maps in alpha: Overpass, Coolant, and Last Train. Each fits the 4:3 safe zone for CRT shader mode and the 16:9 default without cropping critical sightlines.

Verticality is mandatory. Chokepoints are intentional but escapable. Item placement follows a rhythm — mega health every forty-five seconds, not "when the algorithm feels like it." Playtesters who grew up on Unreal Tournament and Doom multiplayer nod. Playtesters who only know cover-based shooters take three sessions to stop hugging walls. Then they start flying, and the game clicks.

Audio: If It Does Not Punch, It Does Not Ship

We are mixing weapons at -3 dB hotter than the industry comfort zone. Yes, your neighbors will hate you. Yes, that is the point. Footsteps are directional. Jump pads have a distinct earprint. The announcer — optional, toggleable, and mercifully brief — only speaks when something matters: first blood, rampage, flag capture. No constant narration. This is not a podcast.

Mod Tools on Day One (Yes, Really)

Separate dispatch coming on mod pipeline details, but netcode and modding intersect here. Custom maps and mutators must not desync the simulation. We expose a documented SDK with map compiler, weapon definition schema, and a local test harness that simulates artificial lag. If your mod breaks rollback, the build fails. We are not shipping another ecosystem of broken workshop downloads.

What Is Left Before Beta

The honest punch list:

• Bot AI that does not cheat — they miss shots, they take bad angles, they die like humans.
• Spectator mode with free cam and player POV for the streamers we actually watch.
• Linux dedicated server binary — headless, scriptable, no GUI nonsense.
• Controller aim assist off by default. On by optional slider. Fight me.

We are targeting a closed beta this winter. If you have LAN scars and opinions about tick rates, watch the home page for signup. We would rather have fifty players who care about map control than fifty thousand who quit after the tutorial explains what a "loadout" is.

Landfall '89 is not a museum piece under glass. It is a live weapon on a workbench — old steel, new springs. We are building the deathmatch game we wanted to play at 2 AM in 1998, with the network stack we deserved but never got.

See you in the server browser. Bring ethernet discipline.