Fling Things and People Plot ranks are documented as Owner, Co-Owner, Member, and Requester. They control who manages the plot, accepts participants, spawns or moves build objects, and uses sensitive house tools. Community documentation is detailed, but verify every permission in the current member panel before trusting someone with a valuable build.
Rank permission matrix
The safest default is the least authority needed. A friendly player who wants to place furniture usually needs Member, not Co-Owner.
Owner responsibilities
The Owner should choose the plot plan, protect save slots, review members, and announce any load or erase action. Keep a clear staging area and stop all collaborators before saving. Do not test ownership-transfer behavior during an important session.
If leaving temporarily, understand the live inactivity rules. Community documentation describes rank changes when people stay away too long or leave, while the official Infinite House Time pass protects against removal for that reason and lists exceptions. The Owner should not assume the title is permanent across every action.
When to use Co-Owner
Promote a player only when they must help handle incoming requests or coordinate a large build. Agree on who can accept members, move structural pieces, and change the plan. Two people making conflicting rank decisions creates more risk than it saves.
Do not give Co-Owner as a cosmetic reward. Current community documentation says the role has meaningful management rights. Test those rights in an empty or disposable plot before using them around a saved project.
If trust changes, use the live demotion control promptly and verify the result. Do not rely on asking the player to avoid a button they can still access.
Use Member for normal collaboration
Member is the practical rank for someone placing, rotating, and arranging objects. Assign a zone or job so their actions do not collide with another builder. Explain house capacity, Item Builder output rules, and the save milestone.
Before accepting a new Member, finish any sensitive load or erase task. Once they join, watch one simple placement to confirm the current permissions and controls behave as expected.
If a Member only needs to observe, leave them outside the permission set until the group is ready. Access should follow the task, not precede it.
Treat Requester as a decision point
Requester is the entry state for someone asking to join. Read the username carefully and ask the owner before acceptance. A crowded request list is not a reason to approve everyone.
The official Infinite House Time description specifically says becoming a Requester on a different house can remove you from another house list. That exception matters before someone casually requests access elsewhere. Read Infinite House Time for the exact creator wording.
If a request is unfamiliar or disruptive, deny or ignore it through the current UI. Do not start a Grab Line confrontation.
Verify permissions without risking a build
Use an empty plot and one disposable object. Test whether each rank can enter, spawn through the Item Builder, move a prop, accept a request, promote, demote, save, load, or erase. Stop before any control that would destroy saved work.
Record the date, device, rank, and visible button. A grayed-out button is stronger evidence than an assumption. Avoid old glitch instructions that bypass save or rank boundaries; they are not legitimate permissions and may disappear after an update.
Rank mistakes and recovery
If the wrong player is promoted, stop building, use the live demotion or removal control, and verify the member list. If ownership changes after someone leaves, pause all save/load actions until the new owner is clear. If someone moves a major structure, reset manually or load only after confirming the correct saved slot.
Use Building Plots for the full claim and collaboration workflow and House Saves before recovery with a saved layout.
Rank checklist
- Identify the owner and project goal.
- Accept only recognized Requesters.
- Use Member for ordinary building.
- Use Co-Owner only for trusted management needs.
- Keep save/load and erase decisions explicit.
- Recheck ranks before leaving or claiming another plot.
- Verify live permissions after updates.