Support the Atlas

KNOWLEDGE IS YOUR WONDER WEAPON

Field Guides.

Browse curated map tutorials and original Atlas articles on preparation, crew play, and record keeping.

← All Atlas Field Notes
Using the Atlas

Share Your Zombies Progress On Your Terms

Understand personal records, player discovery, group recruitment, and public group statistics as separate choices.

You can want a permanent personal record without wanting a public profile. You can want teammates without publishing every accomplishment. Atlas separates these decisions so that joining the community does not require exposing everything at once.

Browse Before Creating An Account

Public guides and the map catalog can be explored without signing in. The guest tracker is useful for trying the record form, but guest progress is temporary. If a record matters, sign in before relying on the site to preserve it.

An account lets you save personal progress and use eligible community features. It also brings age confirmation and account settings. Read the labels when changing visibility; being signed in is not a command to publish all of your statistics.

Separate Progress From Discoverability

Personal record visibility controls which progress can appear publicly. Per-game visibility can differ from your overall preference. Review the games you play most often instead of assuming one visible result means the entire history is shared.

Player discovery serves a different purpose: helping other players find you by the information you choose to share. Consider which details are useful for matchmaking. A broad region, supported platform, and preferred play style can be enough; precise personal locations are unnecessary. Review the visibility choices for individual social fields as well.

Decide How People Can Contact You

Accepting new friend or message requests is another choice. Being searchable does not mean that you must accept every request. Keep initial communication inside the service until you are comfortable sharing another contact route.

If a conversation becomes unwelcome, use the available block and report controls. Blocking on Atlas affects its own contact and discovery flows. Discord has separate controls and permissions, so review those separately when the same person can reach you there.

Treat Crew Publishing As A Shared Decision

Group recruitment determines how people discover or join a crew. Public group statistics determine whether anyone can see its aggregate accomplishments. Leaderboard participation is a further opt-in. These switches are independent of each member’s personal record visibility.

Before an owner or admin publishes crew statistics, review the group name, description, and image as public-facing content. Publishing includes member count, but the public statistics endpoint does not list member identities, private messages, schedules, or Discord links. Keep personal arrangements out of the public description.

Review After A Change In How You Play

A good time to revisit settings is when joining a new crew, switching from casual play to public challenges, or sharing the site with a larger audience. Check your personal settings and any group you administer separately. Do not rely on the appearance of a single screen as proof that every other view is private.

Turning visibility off prevents subsequent public access through the relevant service endpoints. It cannot erase copies someone already made while information was public. If you need help with an account or data request, use the account controls and the contact information linked in the site footer. Never send a password or Discord backup code to support.

Put the Guide to Work

Record your result and the checkpoint to improve next time.