ARDEM intelligence · Evidence checked 19 September 2026

ARDEM Protocol: The Outbreak — what the 15 October public playtest can finally tell us

Protocol: The Outbreak is scheduled to open ARDEM to the public on 15 October 2026 on PC. Techtive says there will be no invite requirement or waitlist, although the event page still asks players to sign in and apply. The start time, duration, preload, download route, public streaming rules and complete build contents remain unannounced. A04

Playtest status

Scheduled · 15 October 2026 · PC

QuestionCurrent answerEvidence state
EventProtocol: The OutbreakFirst-party title A04
Date15 October 2026First-party schedule A04
PlatformPCFirst-party schedule A04
AccessTechtive says everyone can join; no invite or waitlistDeveloper statement A04
Current actionThe official page asks players to sign in and applyPublicly observed A04
Start timeNot announcedUnknown
End time / durationNot announcedUnknown
Preload / downloadNot announcedUnknown
Public-test NDA / streamingNo rule published on the reviewed public pageUnknown
Exact build contentsNo complete public-build manifest publishedUnknown
Server regionsGlobal deployment is the stated plan; an October region list is not publishedDeveloper-described / unknown A22
Early Access relationshipTechtive says the test will set the Early Access dateDeveloper planning statement, not a date announcement A22

The date is a current schedule, not proof that the event has happened. This panel should change when Techtive publishes operational instructions or if the schedule moves.

What Protocol: The Outbreak is

Techtive describes this as the first time ARDEM will open its world to everyone at once: no access waves, waitlist or invitation, with players encouraged to survive, build and bring friends. A04

That wording makes the event broader than the closed technical waves. It does not establish that the October client contains every system advertised on ARDEM's website or Steam. Techtive has not published a complete build list, the accessible portion of Minnowa, the available server rules or the persistence policy for this test.

The useful expectation is therefore specific: October should be the first broad chance to examine whether ARDEM is becoming the connected survival game Techtive describes. The Gameplay page covers the intended loop across the wider game; this page asks which parts are actually present in this build and how well they connect.

How to join

The official event page currently gives two messages at once: access is open to everyone, and visitors should Sign in to apply. The most cautious reading is that an account/application step may still be required even though Techtive says players will not be selected through a waitlist or invitation. Techtive has not explained that interface more precisely. A04

For now:

  1. Use Techtive's official Protocol: The Outbreak page.
  2. Sign in or create the account requested there.
  3. Do not assume the word “apply” means places are selective; the same page says the test is public.
  4. Recheck before 15 October for the client, Steam branch, download, start time and region instructions.

There is no verified access code, preload method or special Steam command to publish yet.

Three access tracks, three different evidence limits

Closed technical waves

Techtive says the current closed build is under NDA, contains very little content compared with what is being prepared for October and exists mainly to stress servers, expose crashes and generate technical logs. Wave 2 began on 4 September with a few hundred additional players selected at random from more than 30,000 registrations. A05

That makes the closed build poor evidence for the breadth or feel of Protocol: The Outbreak. A missing feature may simply be outside the technical build, while private impressions cannot be independently checked. Most importantly, the closed-test NDA does not automatically apply to the separate public event.

Protocol: The Outbreak

The 15 October event is the announced public track. Techtive presents it as the point at which players can explore the world and experience the game rather than merely help the underlying technology survive. A04 A05

Public access still does not make the client a finished or fully representative version of ARDEM. Build identity, available systems, server conditions and patches will matter when interpreting what players see.

Creator programme

Techtive's creator programme is a third route. It can provide early access to unreleased material under separate NDA and embargo conditions. That access should not be mistaken for the universal public entry promised for 15 October, and creator footage should be labelled by build and conditions where known. A19

How the testing plan reached 15 October

DateWhat changedWhy it matters
12 August 2026Techtive announced a smaller closed test for 31 August followed by a public test on 15 OctoberThis replaced the earlier idea of opening broadly in August and made the public test dependent on staged technical preparation A22
31 August 2026Closed technical testing began in small wavesThe studio chose controlled load testing before inviting the full audience A22
4 September 2026Closed Wave 2 added a few hundred randomly selected players under NDATechtive described the build as sparse, technical and not representative of the October experience A05
10 September 2026A new development roundup showed active work on locations, clothing, farming stages, weapons and character fittingThese are useful signs of ongoing production, not a confirmed October build inventory A06
15 October 2026Protocol: The Outbreak is scheduled to open on PCThis is the first announced broad-access checkpoint A04
After the public testTechtive says results will determine how much work remains before Early AccessThe next release answer should come from test findings, not a guessed date A22

Why October matters to Early Access

Steam displays a 2026 Early Access target, while Techtive's press material has also used TBA. The studio's 12 August update says the public playtest will “set the Early Access date” by showing how much work still has to go into the Early Access build. A02 A03 A22

That is planning language. It does not mean 15 October is Early Access, that an exact date has already been fixed, or that one successful test day guarantees a 2026 release. It means the public build is intended to inform a later decision.

Steam's current Early Access description says ARDEM's core systems are already working together and that a large portion of the 64 km² map is open. That is a first-party developer claim published on the store page; it is not independent proof of the October build's contents. A02

For the broader release position, including the 2026/TBA tension, see ARDEM Release.

What is confirmed, expected, WIP or still unknown

StatusWhat belongs hereWhat it means for 15 October
Confirmed for the event15 October 2026; PC; public access; no invite; no waitlist; sign-in/application currently shownThese are the only firm operational details on the event page A04
Named in the event invitationSurviving, building and playing with friendsStronger than a general product-page promise, but still not a detailed feature manifest A04
Developer-described for ARDEMHandcrafted exploration, the restless, weapons, bases, electricity, vehicles, farming, hunting, weather, persistent servers, territory and reputationThese define the intended game and the questions worth testing; they are not all confirmed for this client A01 A02
Shown as active work in progressInfected animation/behaviour work, weapon and attachment development, farming growth stages, reactive clothing, location dressing and character fittingThese systems are visibly being developed, but their October availability and maturity are not established A06 A09 A22
Unknown for the October buildExact playable area, system list, server modes/cap, persistence, wipes, territory, reputation, progression carry-over and full infected/combat scopeWait for build notes, the client or a direct Techtive answer

The distinction protects both directions. A feature shown in a development clip should not be promoted to “playable in October” without evidence. A feature absent from one test build should not be called cancelled unless Techtive says so.

What survival-game fans should be able to learn

The headline question is not whether ARDEM has a long feature list. It is whether the systems present in Protocol: The Outbreak create a coherent reason to leave shelter, take risks, bring resources home and prepare for the next journey.

Exploration: is Minnowa dense enough to reward the journey?

Techtive advertises a 64 km² / 25 mi² handcrafted world with no procedural terrain generation. Current first-party material names towns, gas stations, diners, shopping areas, motels, farms, barns and sheds, forests, industrial areas, military sites, checkpoints, bunkers, caves and hidden locations. A01 A02

Map size alone says little about exploration. The important test is whether places have distinct resources, threats, stories or strategic value—and whether the space between them creates decisions rather than empty travel. Techtive has shown locations being dressed for loot and environmental storytelling, including dark Claypit interiors intended to require light sources. These are work-in-progress examples, not proof of the October map's density. A07 A09

The public build can begin to establish how much of Minnowa is accessible, whether landmarks are memorable, how often travel produces a meaningful discovery and whether players learn the landscape rather than simply follow interface markers. It cannot establish that the full advertised world will be present at Early Access or final release.

The restless: are they a survival system or background population?

The infected are currently called the restless in ARDEM's product language. Steam describes varied enemies with different behaviours and attack patterns, while Techtive's 2026 work-in-progress material includes zombie body types and visual reactions involving blood and clothing damage. A02 A06

Those materials support the existence and continued development of the infected. They do not show how a representative public encounter works. Players still need to learn how the restless detect sound and sight, how far they pursue, whether one enemy can be dangerous, how groups behave, how attacks communicate risk and whether the game's night-time threat has a mechanical consequence.

If only a limited infected set appears in October, the page should record that as the scope of that build. It should not silently downgrade the wider design or pretend an unfinished test proves final variety.

Gunplay: do weapons change survival decisions?

Techtive has shown weapon, attachment and animation work built around realism, function and practical compatibility. One example says an attachment may need another component to function rather than acting as a universal upgrade. The September roundup also makes clear that some assets are sourced and then adapted rather than created wholly in-house. A06 A09

The unresolved part is the feel and consequence of combat. A useful test needs to separate modelling and customisation from aiming, recoil, feedback, damage, ammunition pressure, weapon noise, maintenance, attachment logic and performance against the restless or other players. The question is not whether a rifle looks detailed; it is whether firing it solves one problem while creating another.

Where PvP is available, server rules and player count will also shape the answer. A short low-population session cannot establish the long-term combat balance of a persistent world.

Bases and electricity: does shelter become a working survival system?

ARDEM's base pitch goes beyond placing walls. Techtive describes freely built shelters that can be fortified, furnished and used to cultivate land, with protection from weather, infected and other players. Its electricity pitch names fuel, wind and solar generation and says power can run lights, garage doors, outlets, floodlights, security and other equipment. A01 A02

The interesting connection is between those systems. A base becomes more than storage if light changes night safety, fuel creates a continuing burden, powered equipment supports recovery or production, and damage or resource loss forces a response. October can begin to show construction freedom, permissions, storage, fortification, repair, generation and useful powered devices.

It may not settle offline protection, raid balance, long-term decay or behaviour across wipes. Sourceborne will not infer batteries, wiring limits, grid capacity or failure mechanics that Techtive has not documented or the public build does not show.

Vehicles: transport or a real logistics layer?

A 64 km² world gives vehicles an obvious purpose. Techtive describes finding, repairing, fuelling, maintaining, upgrading and customising vehicles, with cargo and allies making them part of longer journeys. Earlier developer material also discussed storage and heavy utility trailers. A02 A22

The public test can show whether vehicles are simple speed boosts or assets that change what players can carry, where they can establish a base and how far they are willing to travel. Repair requirements, fuel use, breakdowns, cargo, persistence and recovery after death or disconnection will determine whether driving becomes survival logistics.

The final roster, handling, damage model and ownership rules remain open even if one or two vehicles are playable.

Farming, hunting and survival: do the resource loops connect?

Techtive currently describes hunger, thirst, weather, crops, hunting, fishing and foraging. September material shows farming props across multiple growth stages, explicitly labelled as ongoing work. The developer also says a core crafting system is in place while its item breadth and gaps are still being expanded with community feedback. A02 A06 A11

What matters is the trade-off between these systems. Does a player carry food for a long expedition, forage on the way, hunt at the cost of time and noise, or invest in crops that tie them to a defensible home? Do weather and clothing change preparation, and does storage make returning to base worthwhile?

A test build does not need final balance to reveal whether those relationships exist. It does need enough of the loop to show that farming, hunting and crafting are more than disconnected demonstrations.

Multiplayer, persistence, territory and reputation: what does “MMO” mean here?

Techtive now calls ARDEM an open-world survival MMO. Its detailed website copy describes persistent servers for up to 64 players, while hero marketing says 64+ Player Servers. Sourceborne uses the more precise up-to-64 wording and preserves the inconsistency rather than turning it into a new number. A01

The studio also says the world runs continuously, changes while players are offline, supports territory claims and offers PvE, PvP or RP paths, with reputations described as permanent. Those are consequential promises because they extend beyond one session. A01 A02

Protocol: The Outbreak can begin to reveal the displayed server cap, regions, queues, grouping, server identity, persistence across sessions, rule-set choices, territory tools and any formal reputation state. It may still leave the meaning of “MMO”, the wipe policy, offline consequences and long-term social systems unresolved.

Claim-to-observation record

This record is not a scorecard. It preserves what Techtive said before broad access and adds public evidence without erasing the original source.

Developer-described claimEvidence before the public testWhat the public build can addCurrent resolution
64 km² handcrafted worldCurrent website and Steam descriptions A01 A02Accessible area, build boundaries, location density and repeatable travelDeveloper-described; October scope unknown
Up to 64-player persistent serversDetailed website and Steam copy; conflicting 64+ hero line A01 A02Client/server cap, queues and observed sessions under stated conditionsDeveloper-described; not publicly established
World evolves while players are offlineCurrent website persistence statement A01State retained across logout, restart or an observed absenceDeveloper-described; not publicly established
Territory claimingCurrent product description A01Claim interface, permissions, ownership and conflict behaviourDeveloper-described; October inclusion unknown
Permanent reputationCurrent multiplayer description A01A durable formal state or clear persistent social consequenceDeveloper-described; meaning unresolved
Base buildingWebsite and Steam feature descriptions A01 A02Placement, construction, permissions, damage, storage and persistenceNamed in event invitation; exact scope unknown
ElectricityFuel, wind and solar power with named uses A01 A02Generation, distribution, resource costs and functioning devicesDeveloper-described; October inclusion unknown
VehiclesFinding, repair, fuel, upgrades, cargo and maintenance descriptions A01 A02Playable vehicle loop, persistence and recovery rulesDeveloper-described; October inclusion unknown
Farming and survivalProduct-page claims plus WIP growth stages A02 A06Accessible crops, food pressure, hunting/foraging and their connectionsDeveloper-described / WIP; October scope unknown
Infected threatProduct descriptions and WIP zombie-related material A02 A06Detection, pursuit, attacks, variety and combat behaviourDeveloper-described / WIP; October scope unknown
PvE, PvP and RP choicesCurrent website and Steam descriptions A01 A02Available server options and documented rule setsDeveloper-described; October options unknown

After opening, each observation should record the date, build or patch where available, server conditions, what was actually visible and any limit on the conclusion. “Not in this build” and “cancelled” are not the same finding.

Test-day verification programme

Access and build identity

  • opening time and whether access is actually non-selective;
  • account, Steam or separate-client requirements;
  • download route, branch and visible build identifier;
  • regions, queues, maintenance and server selection;
  • public recording, streaming and discussion rules.

World and core loop

  • accessible map area, boundaries, location density and travel time;
  • reasons to enter, revisit or avoid different locations;
  • loot, hunger, thirst, weather and the return-to-base loop;
  • restless detection, pursuit, attacks and combat behaviour;
  • weapons, attachments, damage, ammunition pressure and noise.

Construction, power and logistics

  • building freedom, storage, permissions, damage and repair;
  • generators, solar or wind sources, distribution and powered devices;
  • crops, hunting, fishing, foraging and crafting where available;
  • vehicle discovery, repair, fuel, cargo, ownership and persistence.

Multiplayer and technical state

  • advertised server cap and observed population;
  • grouping, communication and PvE/PvP/RP rules;
  • territory, reputation and offline-world changes;
  • persistence through logout, restart or interruption;
  • crashes, disconnects, latency, recovery and hardware-specific performance.

Evidence should be proportionate. One machine cannot establish general performance; one quiet server cannot establish population behaviour; one short session cannot prove long-term persistence.

What remains deliberately unresolved

Unless Techtive publishes new information before opening, the following remain unknown:

  • exact start time and time zone;
  • test end time and total duration;
  • preload and download/install procedure;
  • public-test NDA, streaming and recording rules;
  • complete October build manifest;
  • accessible share of the 64 km² world;
  • server-region list, capacity and queue model;
  • available PvE, PvP and RP options;
  • wipe and restart policy;
  • progression or character carry-over between test sessions;
  • carry-over into Early Access;
  • offline-base protection and decay;
  • territory-claim rules;
  • whether reputation is a formal mechanic;
  • which advertised and WIP systems will be enabled.

These are practical player questions, not gaps to fill with inference. The list should shrink when Techtive or the live build supplies an answer.

FAQ entries

When is the ARDEM public playtest?

Protocol: The Outbreak is currently scheduled for 15 October 2026 on PC. A04

What time does the ARDEM playtest start?

Techtive has not published a start time or time zone on the reviewed event page.

How do I join Protocol: The Outbreak?

Use Techtive's official event page and complete the sign-in/application step shown there. Techtive says the test is open to everyone with no invitation or waitlist, but download instructions have not yet been published. A04

Is the public playtest really open to everyone?

That is Techtive's current wording: no waves, invite or waitlist. The simultaneous “Sign in to apply” prompt means an account step still appears necessary, but Techtive has not described it as selective. A04

Is there an ARDEM public-playtest NDA?

No public-test NDA has been established in the material reviewed. The earlier closed technical waves are under NDA; that restriction cannot be carried over without a separate rule for Protocol: The Outbreak. A05

Can I stream or record the public playtest?

Techtive has not published public-test streaming or recording rules on the reviewed event page. Wait for a direct rule rather than borrowing the closed-test NDA.

Can I preload ARDEM?

No preload or download information has been announced for the public test.

How long will the playtest last?

The official page gives the date but no end time or duration.

What will be playable in the October build?

The event invitation explicitly mentions surviving and building with friends, but Techtive has not published a complete feature manifest. The wider game descriptions and WIP updates should not be treated as a promise that every named system is enabled on 15 October. A04

Will Protocol: The Outbreak include the restless?

The restless are central to ARDEM's current product description, and Techtive has shown ongoing zombie-related development. The precise infected variety and behaviour in the October client remain unconfirmed until Techtive publishes build details or the test opens. A02 A06

Will every ARDEM feature be playable?

Not established. ARDEM's website and Steam page describe a large connected feature set, while development posts show several systems still being worked on. That evidence describes the intended game, not a complete October checklist.

Is this the same build as the closed NDA test?

Techtive says the closed build contains very little content compared with October and exists mainly for server stress, crashes and technical data. Treat the two as different builds and access tracks. A05

Is this Early Access?

No. Protocol: The Outbreak is a public test before Early Access.

Does the playtest confirm the Early Access date?

No. Techtive says the test will help determine the date by showing how much work remains. Steam still displays a 2026 target, not an exact launch date. A02 A22

Will progress carry over?

No progression or character carry-over policy has been announced for later tests or Early Access.

How many players does ARDEM support?

Techtive's detailed website and Steam copy say up to 64 players per server. A separate website headline says “64+ Player Servers”; Sourceborne uses the more precise up-to-64 figure until Techtive resolves the difference. A01 A02

Sources

  1. A04 Techtive Games — Protocol: The Outbreak public playtest page; rechecked 19 September 2026.
  2. A22 Techtive Games — official Steam announcements feed; testing plan, global deployment intent, Early Access timing language and earlier WIP updates; rechecked 19 September 2026.
  3. A05 Techtive Games — Closed Playtest Wave 2 Is Live; NDA, selection and technical-scope statement; rechecked 19 September 2026.
  4. A01 Techtive Games — current ARDEM product page; world, systems, persistence, multiplayer and 64+/up-to-64 wording; rechecked 19 September 2026.
  5. A02 Steam — ARDEM store page; current 2026 target, Early Access description, product systems and requirements; rechecked 19 September 2026.
  6. A03 Techtive Games — press kit; TBA and platform context.
  7. A06 Techtive Games — Sneak Peek Roundup 2; September WIP locations, clothing, farming, weapons and character fitting.
  8. A07 Techtive Games — Sneak Peek: Nature Reclaims ARDEM; Claypit interiors, loot and lighting context.
  9. A09 Techtive Games — Sneak Peek: Weapons & World Design; location dressing, weapons and attachment compatibility.
  10. A11 Techtive Games — Crafting System Expansion; core-system and active-expansion wording.
  11. A19 Techtive Games — creator programme; separate early-access NDA and embargo track.

Reliability and review checkpoints

Reliability: High for the date, PC platform and access wording currently published by Techtive. Medium for the intended product systems because they remain developer descriptions. October build contents and operational rules remain unknown until Techtive publishes instructions or the client becomes publicly observable.

Evidence checked: 19 September 2026.

Scheduled reviews: Seven days before the event; 48 hours before; at opening; after the first 24 hours; after roughly 72 hours if the test remains live; and after the first substantive post-test Techtive statement.

Immediate review triggers: A schedule change, start/end time, preload or download instructions, build notes, region list, public streaming/NDA rules, patch notes or an Early Access date announcement.

After the public test

This URL stays in place. Once public evidence exists, the page should evolve toward ARDEM October 2026 Public Playtest — What Was Actually Playable.

The pre-test status, chronology and developer claims should remain visible. New observations should be attached to a build and date, and unresolved rows should remain unresolved. The lasting value is the comparison between the game Techtive described before broad access and the build players were actually able to examine.

Follow Game