The primary Roblox source was reviewed on 2026-08-08. Exact values or steps that source does not confirm remain labeled unknown until reproduced in the current version.
No formal role list is confirmed
The high-level multiplayer description does not establish that the game uses selectable jobs. Terms familiar from real aviation or other flight games cannot be imported as Land or Die facts. Until the current interface explicitly names a responsibility, every proposed role title remains unknown.
The same applies to role count, availability, unlocks, limits, and assignment method. An existing fan site may list them, but this guide requires a current official statement or reproducible in-game observation before publication.
- Official role names — unknown.
- Number of roles — unknown.
- Selection or assignment method — unknown.
- Role unlocks or limits — unknown.
Permissions and exclusive actions
No evidence shows that a particular player can exclusively operate a control, enter an area, handle an emergency, or receive a distinct reward. Role permissions cannot be inferred from a title alone; they must be demonstrated in the current version and tied to the relevant task context.
A good verification record states what one player could do, what another could not do under the same conditions, and what interface wording explained the difference. Without that comparison, an apparent restriction may have another cause.
- Exclusive controls — unknown.
- Area access — unknown.
- Emergency responsibilities — unknown.
- Role-specific rewards — unknown.
Optional coordination is not a role system
Players can choose to say who will watch a visible objective or try a current prompt. That is general coordination, not proof that the game recognizes a role. Do not present an informal division of labor as required, optimal, or rewarded.
The maximum player count and best crew size are also unknown. A suggestion that works for one group does not establish scaling, matchmaking, shared credit, or a universal staffing plan.
- Communication plan — a player choice.
- Formal role mechanic — needs current-version verification.
- Best staffing — unknown.
- Group rewards and task credit — unknown.
How to document a current role
A future role entry should quote the exact current label, explain how it is assigned, list only permissions the interface states or a repeatable test demonstrates, name the task context, and include the checked date. Any recommended behavior should appear separately as advice rather than as a system rule.
Until such evidence is recorded, this page's correct status is unknown. Return to the Beginner Guide for initial task verification or How to Land for the checklist a role-dependent landing step would need to satisfy.
- Exact role label.
- Assignment method.
- Observed permission and task context.
- Date, version scope, and unresolved cases.