Ardem Playtest: How to Join, Dates & Requirements

Ardem is currently in pre-release with an active closed playtest and a confirmed public playtest date. This page tracks what is publicly confirmed about testing phases, how to join, and what you need before you can play.

Playtest timeline

• Closed Playtest: Running in waves. Access is distributed in batches to registered players.
• Public Playtest: October 15, 2026. Open to everyone — no invite and no waitlist required.
• Early Access: Not yet confirmed (TBA).

How to join the closed playtest

The closed playtest is being run through the official Ardem patient zero program. To be eligible, you need:

1. An Ardem website account on playardem.com
2. Discord linked to your Ardem account
3. Steam linked to your Ardem account

Once your accounts are linked, you are in the pool for closed-playtest wave invitations. Invitations are sent in batches as the team scales server testing.

The closed build is primarily used to stress servers, find crashes, and generate logs. It is not a full or final representation of the game.

Closed playtest is under NDA

The official Ardem closed playtest runs under an NDA. Players in the closed test should not:

• Stream closed-playtest gameplay
• Screenshot or record footage
• Publish clips
• Publicly discuss build contents

If you are in the closed test, refer to the official Discord and patient zero portal for the current scope and reporting channels.

Public playtest — October 15, 2026

The public playtest opens October 15, 2026 and is open to everyone. Unlike the closed test:

• No invite required
• No waitlist required
• Open on the public date

This is the best entry point for most players who want to try Ardem before a full release.

What is confirmed

Ardem is an open-world zombie survival RPG from Techtive Games. Public sources confirm a handcrafted 64 km² world, resource gathering, vehicles, electricity restoration, farming, hunting, fishing, base building, and solo, co-op, PvE, PvP, and RP server play.

What is not yet confirmed

Exact map coordinates, item tables, vehicle part spawns, generator values, crafting recipes, balance rates, and individual server rules still need direct public evidence from the public playtest or official updates before they can be listed as database rows.

Failure modes

Do not treat closed-playtest leaks or secondhand accounts as confirmed data. The closed build is an NDA test build whose contents may change before the public playtest and again before Early Access. Facts only belong on this wiki when they come from official public sources or from the public playtest.

FAQ

Do I need to sign up for the public playtest?

No. The public playtest on October 15, 2026 is open to everyone with no invite or waitlist.

Can I play Ardem right now?

Only if you have received a closed-playtest invitation. Most players should wait for the public playtest on October 15, 2026.

What do I need to prepare for the public playtest?

A Steam account and a PC that meets the official system requirements (to be published closer to the public test date).

Why are some details missing from this page?

Information that is not publicly confirmed by official sources is left out intentionally. This keeps the wiki stable when pre-release material changes.

Source notes

Playtest dates and requirements are sourced from official Ardem channels: the public playtest page on playardem.com, the patient zero / closed-playtest program page, and official Ardem Discord / forum announcements. Specific features and systems come from the official Steam store page. Check the official site for the most current dates and signup status.

• Ardem on Steam
• Official Ardem site

Before the public test opens

Before October 15, use this page as a readiness checklist rather than a spoiler list. Confirm that your Steam account is usable, keep the official site bookmarked, and avoid downloading any unofficial launcher or test client from Discord mirrors. The public test should be reached from official Ardem links only. If a social post claims an earlier public date, compare it against the official site before changing your plan.

For groups, decide server expectations before the test opens. Pick whether you want PvE, PvP, RP, or co-op exploration, then record that preference separately from confirmed game rules. Public server names, wipes, region availability, and moderation settings can change quickly during a test, so the safest plan is to keep group logistics flexible until the live browser or official announcements confirm them.

If you join the closed patient zero waves, keep private observations out of public guides. Closed testing is useful for bug reports, stability notes, and official feedback channels, but it is not suitable evidence for public spawn tables or permanent mechanics. When the public test opens, re-check every survival loop from a clean public build before turning it into a database entry.

How to report and verify changes

When you find a public-test detail, record the date, route, server type, and exact screen where it appeared. A useful note says what you did, what the game showed, and whether the result repeated. A weak note only says that somebody heard about a feature. This wiki should prefer repeatable public observations and official notes over summaries copied from chat.

Use screenshots responsibly after the NDA boundary no longer applies to the public build. Capture UI labels, map names, vehicle part names, and resource names when they are visible, but avoid presenting one temporary value as final balance. If a later official post changes the same detail, update the page and keep the old value out of active tables.

What to check first on test day

Start with account access and server selection. Then confirm basic movement, inventory, gathering, vehicle interaction, electricity objects, and base placement prompts. These first checks make every later route easier to verify. If one system is unavailable or disabled during the test, mark it as unavailable in that build instead of filling the gap with older trailer assumptions.