Short answer
Ready or Not is a 2023 tactical first-person shooter by Ireland-based VOID Interactive that started on Unreal Engine 4 and was upgraded to Unreal Engine 5 with the Home Invasion DLC on July 23, 2024. Wikipedia lists Engine: Unreal Engine 5 for the current build, while PCGamingWiki lists Former: Unreal Engine 4 and current: Unreal Engine 5, which is why search keeps asking UE4 vs UE5.
It released on Steam Early Access on December 17, 2021 and hit 1.0 on December 13, 2023, then came to PlayStation 5 and Xbox Series X/S on July 15, 2025. Wikipedia records those dates and the console port. It was the best-selling game on Steam in the week after release and is described as a spiritual successor to Sierra's SWAT series and early Rainbow Six. That reception note is in the same overview.
My argument is different from most engine postmortems: VOID did not pick Unreal for beauty. It picked Unreal for slowness, then paid a migration tax to keep that slowness on consoles. UE4 let a tiny team fake AAA weight with Blueprints, penetration and surrender AI. UE5 was forced by the console future, not by Nanite envy — and the upgrade broke as much as it fixed.
Why the engine question is so confused
If you type the obvious queries you get version whiplash:
- what engine does ready or not use
- what game engine does ready or not use
- is ready or not unreal engine 5
- what engine is ready or not on
- ready or not unreal engine 4 vs 5 / unreal engine 5 update
That confusion is accurate. Development began in June 2016 with a reveal trailer on May 3, 2017, alpha for Supporter Edition owners on August 19, 2019 under NDA, and a PvP test in April 2020 before Early Access. Wikipedia traces that long runway. For most of that runway the game was UE4. The DLC section explicitly says Home Invasion on July 23, 2024 also upgraded Ready or Not to Unreal Engine 5.
In other words: if you played 2021-2023, you played UE4. If you play on PS5 in 2025-2026, you play UE5. Both answers are right, which is why PCGamingWiki keeps both entries.
What Unreal Engine 4 bought a SWAT game
UE4 was the boring, correct choice in 2016-2021 for a team that could not afford to write a renderer.
1. Blueprints + C++ for a tiny team. UE4 shipped in March 2014 with physically based materials and Blueprints visual scripting, and UE4.27 was the stable end of that line in August 2021. VOID needed exactly that: designers who could wire doors, optiwands, stingers and arrest logic without waiting on engine programmers. The game's signature is not shooting — it is commanding. In single-player you split four SWAT into red and blue elements or order gold as a whole to breach, restrain and cover autonomously. Wikipedia describes red/blue/gold command and autonomous restrain and cover. That is Blueprint-friendly gameplay.
2. Penetration and few-shot lethality. Both players and enemies die in a few shots, bullets react with walls, furniture and bodies, and suspects bleed out from artery hits in legs. Wikipedia notes realism as central pillar with few-shot kills and tactical planning, and Steam stresses that bullets pass through walls, furniture and bodies and that cover and corners decide life or death. Unreal's collision and material system made that readable without a custom ballistics lab.
3. Surrender AI as content. Suspects fake death when shot, pretend to surrender then draw, use hostages as human shields, retreat to weapon caches, hide under objects or rush with knives. Those behaviors are listed together in the gameplay section. Add less-lethal tasers, riot guns, pepper spray and beanbag shotguns where arrests score more than kills and S-rank requires everyone detained alive and conscious, and you get a morality meter built from engine AI states. That arrest-over-kill scoring rule is explicit.
4. Co-op without writing netcode from zero. Missions run solo with AI teammates or cooperatively with up to 5 players online, while competitive PvP was cut after 1.0. Wikipedia confirms 5-player co-op and the PvP cut, and Steam advertises crossplay 5-player co-op on all platforms. UE4 replication, already hardened by Fortnite's 100-player work that Epic folded back into the engine, was good enough for slow CQB where 5 players clear rooms instead of 100 players dropping from a bus. Epic's Fortnite-driven replication improvements are part of UE4 history.
What UE4 cost: shader precompilation hitches, CPU bottlenecks on some PCs, forced film grain with no toggle, and ray-traced reflections/shadows/ambient occlusion that were planned for Early Access but never shipped in full release. PCGamingWiki notes ray tracing was planned then not implemented and documents film-grain, FOV, DLSS/FSR and frame-limit workarounds. Tactical players noticed — CQB lives or dies on clean dark corners.
Why move to UE5 in July 2024 if UE4 worked?
Not for Nanite showpieces. For ports and DLC pipeline.
UE5 launched April 5, 2022 with Nanite virtualized geometry and Lumen dynamic global illumination, plus World Partition streaming, Chaos physics replacing PhysX and MetaHuman-class character tooling. Ready or Not does not use most of that as a showcase. Dark Waters added maritime maps, clothing updates, aerial thermal camera, new animations and AI behaviors. Wikipedia lists those Dark Waters additions for December 10, 2024. Home Invasion added three hurricane-aftermath missions — Dorms, Narcos, Lawmaker — plus weapons and customization. Those three missions and the UE5 upgrade share the same July 23, 2024 note.
My reading, labeled as analysis rather than VOID's statement: the upgrade was console insurance. PS5 and Xbox Series X/S shipped July 15, 2025 with two new Los Suenos Stories missions, Hunger Strike and Stolen Valor, plus difficulty and career record. Wikipedia ties Los Suenos Stories to the console date. Staying on UE4.27 in 2025 would have meant backporting console SDKs, FSR 3 / DLSS 3.7 work and controller support that UE5 already carries. PCGamingWiki records the Los Suenos Stories patch updating FSR 2.1.2 to 3.0.4 and DLSS 3.5.2 to 3.7.20. The price was new stutter discourse, the same shader-compilation and traversal stutter criticism that follows many UE5 games, and a censorship fight that had nothing to do with Nanite but everything to do with platform rules.
On June 27, 2025 VOID announced toned-down dismemberment and nudity for consoles, which also affected Windows. Players called it censorship, review-bombed Steam, and within an hour a Nexus Mods mod called Uncensored or Not passed 7,000 downloads in 24 hours. VOID said it only changed what was absolutely required. Wikipedia recounts the June 27, 2025 announcement, backlash, review bombing and mod numbers. Despite that, it became the most pre-ordered game on PlayStation Store. That pre-order note is in the same section. Engine migration did not cause censorship, but it enabled the single-build future where one censored build ships everywhere and mods restore the rest.
Three contrarian takeaways
These are my interpretations, not VOID press releases.
1. Readability beats realism, so the upgrade was deliberately boring. Most UE5 migrations sell Lumen and Nanite. Ready or Not sells darkness you can read. CQB needs baked, predictable corners where a suspect's shoulder pixel is a decision. Fully dynamic Lumen would make every flashlight a performance and fairness gamble. VOID kept lighting conservative, kept forced grain as cheap dread, and spent UE5 budget on thermal camera and animation rather than photogrammetry streets. If you think UE5 means prettier, this game says UE5 can mean portability with the same muddy hallway.
2. The S-rank is an engine feature. Other shooters use Unreal for 60fps doctrine or sub-tick shooting. Ready or Not uses Unreal to make you not shoot. Arrest scoring, bleed-out timers, fake surrenders and Commander mental-health deterioration where officers need therapy, can sit out, unlock traits or resign if you kill too much — that therapy/trait/resign loop is documented in Commander mode — turn save files into conscience files. Ironman wipes progress on death. Ironman as Commander with full reset is explicit. That is the opposite of a live-service shooter that forgives everything to keep you queuing.
3. Slow AI is cheap content. Four DLCs — Home Invasion July 23, 2024, Dark Waters December 10, 2024, Los Suenos Stories July 15, 2025, Boiling Point March 12, 2026 with G18-C, S2011-P, RTWC-6.5 and gas/CQB suspect mechanics — reuse the same Los Suenos decline lore told through environmental storytelling rather than cutscenes. Wikipedia lists all four DLCs, dates and Boiling Point weapons. New rooms + new surrender rules = new game, no new engine needed. Indie devs should steal that: if your AI can fake death, one apartment is five missions.
What indie devs can steal
- Prototype arrests, not guns. If surrender/fake-death/human-shield states are fun with gray boxes in UE4 Blueprints, they will survive UE5. If they are boring, Nanite will not save them.
- Freeze your engine until your platform forces you. VOID lived on UE4 from 2016 to mid-2024. That is seven years of stable ballistics and mod paths. Migrate for SDKs and consoles, not for demos.
- Budget for grain and stutter honestly. CQB players will forgive ugly walls faster than unfair darkness. Ship FOV sliders, separate world/weapon FOV, resolution scale and DLAA/FSR options early — PCGamingWiki shows how much of Ready or Not's support load is exactly those settings.
- Design scoring that punishes your engine's strength. Unreal makes killing easy and juicy; S-rank that demands live arrests turns the engine against itself and creates YouTube-worthy restraint moments.
Train the habits in a browser before you breach
You cannot practice Ready or Not's teamwork in a 150 MB web game, but you can practice the two habits that kill beginners: rushing doorways and spraying.
For doorway discipline, BodyCamera Shooter is a useful warm-up. It is a single-player browser FPS fought through a shaking chest camera with fisheye distortion, where you clear buildings, hold concrete cover, burst-fire and pre-aim doorways. The site explicitly frames corner checks and doorway fights as the core skill and warns that standing in the open ends runs. That is the same lesson as Los Suenos on a tiny budget.
For angle discipline, Block Contra: Clutch Strike trains the Counter-Strike habits Ready or Not assumes: crosshair at head height, safe vs aggressive angles per lane, reload only when safe, and isolating duels instead of fighting two suspects at once. Its guide centers on not taking coin-flip peeks and repositioning after every kill — good prep for red/blue element breaches where trading one-for-one still fails the S-rank.
Neither replaces 5-player co-op, optiwand work or less-lethal arrests, but ten minutes of fisheye corners and blocky clutch rounds will make your first Los Suenos entry less embarrassing.
Bottom line
Ready or Not bet on UE4 because a small team needed Blueprints, penetration and co-op replication more than it needed beauty, then moved to UE5 on July 23, 2024 because consoles and upscalers demanded it. The result keeps generally favorable reviews — Metacritic 79 and OpenCritic 82 per PCGamingWiki — not because UE5 made it prettier, but because UE4 made it slow enough to be scary, and UE5 let that slowness ship everywhere.
Top comments (0)