KNOWLEDGE IS YOUR WONDER WEAPON
Field Guides.
Browse curated map tutorials and original Atlas articles on preparation, crew play, and record keeping.
Plan A Crew Night That Survives The First Setback
Set a realistic goal, organize roles and availability, and turn a failed attempt into a useful next session.
Most avoidable crew problems begin before the first round: different expectations, uncertain start times, or nobody knowing who is leading the next step. A short plan leaves more of the evening for playing.
Pick One Primary Outcome
Decide whether the session is for learning a route, completing a quest, pushing rounds, or improving a timed result. “Do everything” creates conflicting choices: one player wants to explore a side quest while another wants to restart after a slow opening. Put the primary goal in the session description.
For a first attempt, define a checkpoint you can reach even if the final clear does not happen. Learning the setup route or practicing one unfamiliar encounter is a concrete outcome. A crew can then recognize progress without calling every unfinished quest a wasted night.
Make The Calendar Invitation Usable
Set the actual map edition, mode, start time, expected end time, and player capacity. Use Atlas’s group calendar to collect RSVPs. Check the displayed time in your own timezone, particularly when teammates live in different regions. A weekly availability window is not the same as a confirmed RSVP for a particular session.
Leave room for a late arrival or a failed opening without making the evening indefinite. Write a stopping rule such as “one more attempt if setup finishes before our agreed cutoff.” Confirm any game, map, or platform requirements with the crew before the night begins.
Assign Responsibilities, Not Permanent Status
Choose a route caller, a person to watch the next guide checkpoint, and someone to log the shared result. For a larger party, agree who handles door spending or objective interactions as the map requires. These are temporary jobs, not a ranking of who matters most.
Give new players a meaningful task and explain the reason for it. “Watch this entrance while I interact” is clearer than a stream of unexplained commands. Use a short ready check before an interaction that commits the party to a difficult encounter. In solo play, replace the role split with a written checklist you can review at a safe moment.
Plan For A Failed Attempt
Agree in advance whether a disconnect means continuing, restarting, or switching to practice. Before a new attempt, identify the earliest preventable mistake rather than blaming the last player to go down. The final failure may be the consequence of an earlier spending or communication decision.
A useful debrief is specific: “Two players needed ammunition when we triggered the encounter; next time everyone confirms supplies first.” Change one decision on the next attempt so you can tell whether the adjustment helped.
Leave A Record The Crew Can Use
Choose one person to create the shared group run and add the actual participants. Let the confirmation flow do its job; four teammates should not create four copies of the same group attempt. Record unknown results honestly and use the notes to preserve the one improvement worth carrying forward.
Keep sensitive arrangements in private group spaces. Public group descriptions and statistics can be visible to signed-out visitors when enabled. Discord access is a separate permission system: appearing in an Atlas group or seeing a public crew card does not by itself prove access to its private Discord spaces.
A Five-Minute Pre-Run Brief
Here is an example for a learning session: “We have one hour. Tonight we are learning the Terminus power route, not promising a full clear. Morgan calls destinations, Jules keeps the reference open, and everyone names a shortage before the next interaction. After a failure, we change the earliest decision that caused trouble.” Names and timings here are examples you can replace.
The objective gives the session a stopping point, the roles reduce overlapping instructions, and the shortage call catches a weak setup early. Afterward, record the checkpoint reached and one useful change. If the crew exceeded the plan, that is a bonus; the session still has a meaningful result if it only achieved the original practice goal.
- Name the map edition, mode, party, and session end time.
- State the goal in one sentence and agree what counts as done.
- Choose the route caller and the person checking the guide.
- Agree how to handle a disconnect or an unready teammate.
- Finish with one shared note for the next attempt.