OFFICIAL FACTS
Patch 1.0.1 says public matches cycle through the available maps before repeating. It does not describe private-match selection or the lifetime of a rotation across sessions.
Sources & verification ↓Reading position: —
Reading position stays in this browser.
A PLAN TO TRY
| Record | Why it matters | Example format |
|---|---|---|
| Mode | Public rule has a specific scope | Public / private |
| Map sequence | Memory can merge sessions | Map A → Map B → Map A |
| Session changes | The patch does not define persistence | Joined another party after match 2 |
| Version and outcome | Keep comparisons consistent | Installed version; completed or left |
Start by identifying which mode you entered
Record whether you entered public matchmaking or a private match. The patch labels this as a public-match change, so a privately selected map is not a test of that rule. Next write the map name from the game rather than inferring it from a familiar house or street. Use the map directory when you are unsure which neighborhood you are seeing.
Keep one sequence before deciding the cycle is broken
Write down each match’s map in order and note whether it completed. Mark any return to the menu, group change or fresh matchmaking attempt. The notes do not tell us whether those events reset or preserve a rotation; keeping them visible prevents unrelated sessions from being presented as one uninterrupted sequence. This is an observation method, not a claim about server rotation storage.
Example: the same map after joining another group
Suppose you finish on one map, leave and join a friend, then see that map again. You have observed a repeat across a group change, but that alone does not establish how the documented cycle was applied. Record both the map and the group change. If repeated maps also occur without an obvious session change, preserve that separate sequence instead of merging the two reports.
Use variety to prepare without predicting the next map
Prepare a short reminder for each map: a landmark naming convention, a route question and a useful related guide. Do not promise teammates which map will appear next from an incomplete history. The rule concerns map selection, not fixed item or escape locations within the map. Recheck those in the current match even when the neighborhood is familiar.
Questions about this guide
Does the public rotation rule apply to private matches?
The cited patch labels the change for public matches. It does not establish the same behavior for private selection.
Does changing party leader reset the map cycle?
The cited notes do not specify that. Record leader changes rather than assuming either a reset or continuity.
Can I predict the next map from the last two matches?
This guide does not provide a reliable prediction method. An incomplete sequence and unspecified session behavior are not enough.
Does a new map cycle guarantee different item locations?
Map rotation and item placement are separate questions. Check current objectives and items in the match.
Your next-match checklist
0/3 completedProgress stays in this browser. No account or cloud sync.
Sources & verification
Official sources checked September 12, 2026. Advice is editorial, without our own gameplay testing.
Official game · News ↗