Separate the server modes
“Private server” can refer to access control, Free Roam, or competitive Tourney use, and those are not interchangeable. The official December 3, 2025 changelog says Free Roam is a separate Apocalypse Rising 2 instance with a save separate from the main game. It also documents owner controls and notes Tourney updates. Current cost, player capacity, access steps, and exact menus still need a live Roblox and in-game check.
Before inviting players, state which mode you are using, whether progress is separate, what owner settings are active, and what rules the group expects.
Free Roam boundaries
The official save-separation statement is the most important rule: do not expect Free Roam inventory or character progress to modify the main experience. Use it for exploration, practice, screenshots, controlled testing, or custom sessions only after confirming the current interface still identifies that boundary.
The changelog lists owner options for infected, random events, natural loot, natural vehicles, stat decay, forced first person, free camera, and time lock. It does not guarantee that every option has the same label or range today. Read the live setting and communicate it before the session.
Community private-server pages may mention player limits, Sandbox, data, or cosmetic behavior, but some are marked as incomplete or stale. Treat those claims as items to verify, not current rules.
Tourney use
Tourney is suited to controlled competition when the current mode provides the needed rules. Establish teams, start condition, allowed equipment, perspective, map boundary, time, respawn or elimination behavior, observer rules, and how a winner is determined. Confirm which controls the host can actually enforce.
Do not assume Tourney and Free Roam share save behavior or owner options. Open the chosen mode and document what appears. If a setting cannot be enforced by the server, make it an explicit player rule and assign an observer.
Create a clear session
- Open the official experience and current private-server interface.
- Confirm mode, current price or access requirement, capacity, and map.
- Configure owner settings before inviting the full group.
- Write a short rules message with save boundary and active modifiers.
- Test spawn, inventory, perspective, map, vehicles, events, and admin actions with one player.
- Invite participants only after the test matches the session plan.
This process prevents an exploration session from accidentally using competitive settings or a practice session from being mistaken for main-game progression.
Useful practice setups
For navigation practice, choose a stable time and ordinary map state if available, then rehearse landmark-to-landmark routes. For PvP drills, use equal equipment, known range, a repeatable start, and observers. For vehicle training, reduce unrelated threats only if the current controls allow it, then practice entry, component checks, low-speed turns, stopping, and exit. For content verification, change one setting at a time and record the result.
Owner settings can make practice reproducible, but results may not transfer to public-server conditions. A weapon test without stat decay, infected, latency, or natural loot is a controlled result, not a complete survival ranking.
Host responsibilities
Tell players when recording is active and avoid exposing account information. Keep rules consistent. If the host changes time, loot, perspective, events, or vehicles, announce it. Do not use owner controls to misrepresent a “natural” spawn or drop.
For a public community session, moderate invitations and remove malicious links. Roblox and Discord safety still applies. A private instance does not make an external download, login page, or paid middleman trustworthy.
When the session ends, preserve only the settings and observations needed for reproduction. Do not claim main-game rewards from a separate save.
Verification checklist
Confirm live:
- Roblox private-server availability and current cost;
- player capacity and invitation permissions;
- Free Roam save and cosmetic boundaries;
- available maps and event variants;
- each owner setting and its range;
- Tourney rules and spectator behavior;
- shutdown, restart, and persistence behavior;
- platform support for host controls.
Leave a field unknown if the current interface does not answer it. A community claim from before the December 2025 update may describe a different system.
Common mistakes
Players often assume separate-mode progress returns to the main game, copy an old capacity number, call every hosted instance “Sandbox,” or begin a competitive match before testing perspective and spawn behavior. Hosts sometimes change settings mid-test, making results impossible to reproduce.
Avoid those errors with one mode, one written ruleset, one change at a time, and a short test before the real session.
Sources and freshness
Free Roam, separate save, the listed owner-control categories, and Tourney changes come from the official December 3, 2025 changelog. Community server documentation is used only as a list of questions because it may be incomplete. Access, price, capacity, current menus, cosmetics, persistence, and enforcement require live verification. Last reviewed September 18, 2026.