GameShare FAQ
A clear “can do vs cannot do” reference so your team can plan realistic co-op sessions and avoid common expectation mismatch.
Set Expectations Before the Session Starts
Most GameShare frustration comes from mismatched expectations, not from the feature itself. If everyone assumes their personal progress will merge perfectly at the end of a shared session, the group is set up for disappointment. Agree before starting that GameShare is a coordinated co-op workflow with a host-side source of truth, not a full profile merge.
Write down what the session will and will not change before anyone builds. A five-minute planning chat prevents an hour of duplicated work later.
Keep a Host-Side Plan as the Source of Truth
Because not every unlock and resource syncs identically across players, the host should keep the canonical plan: what was built, what was gathered, and what still needs doing. Other players treat their own view as session state, not as the record.
At the end of each session, capture unresolved blockers and the next host task in one note. That single note is what makes the next GameShare session start clean instead of re-litigating what already happened.
Role Lanes Beat Ad-Hoc Task Switching
Four players who all try to gather, build, and scout at once step on each other continuously. Split into clear lanes, gathering, transport, build execution, and a quality-check or checklist owner, and stick to those lanes for the session.
If a lane falls behind, rebalance at a checkpoint rather than mid-task. Mid-run role swaps are how two players end up doing the same job while a third waits on both.
Keep One Timezone Baseline for the Group
Daytime-dependent content is easier to share when the whole team uses the same timezone offset. Everyone applying the same setting means your daytime windows line up, so co-op goals can be done together instead of waiting on one member's local schedule.
Only shift the baseline when a real-life routine changes for most of the group. Frequent offset changes for individual events make scheduling harder than a stable shared setting.
What You Can Do
- Join up to four players in one shared island session.
- Build together and share real-time construction progress.
- Coordinate gathering roles for faster material throughput.
- Use a shared play plan to divide exploration and crafting tasks.
What You Cannot Do
- You cannot merge all permanent progression into one profile.
- You cannot expect every unlock to sync identically across players.
- You cannot skip host-side setup and still guarantee stable sessions.
- You cannot rely on ad-hoc timezone changes without team coordination.
Scenario Playbook
Solo Baseline
Finish your baseline base flow first, then invite teammates for targeted upgrades instead of broad rebuilding.
Duo Efficiency
Assign one player to gathering loops and one to crafting/placement to avoid duplicate movement and idle time.
Four-Player Co-op
Split into route scouting, material transport, build execution, and quality-check roles with a fixed checklist.
FAQ
Q: Can we treat GameShare as fully shared long-term progression?
A: Use it as coordinated co-op workflow instead of full profile merge. Keep a host-side canonical plan.
Q: Why does our team feel inefficient even with four players?
A: Most teams overlap the same tasks. Define role lanes and route ownership before starting the session.
Q: Should we change timezone settings frequently for events?
A: Use one stable baseline for daily play and only add short event-specific sessions when necessary.