The Steam listing confirms Online Co-op for hololive Dreams, but the public description does not publish a complete lobby manual. Use this route to test a friend session safely. It separates access, invitation, activity, completion and reward checks so you can tell a network problem from a quest or inventory problem.
Check the activity first
Open the current online menu and read the activity name, access requirement, party size, invite control and reward preview. If the activity is a mini-game, compare its solo and co-op labels. If it is a song or quest, note whether the current screen says the result is shared. Do not invite everyone before confirming that the target activity supports the type of session you want.
Invite one friend
Use the Steam or in-game invite control shown by the client. Confirm that the friend appears in the lobby and that both players reach the same ready state. If the invite does not arrive, check the active Steam account, privacy setting, overlay state and current network connection before changing game files. Record the point at which the path stops.
Run a low-risk test
Choose one short activity. Keep the party and input stable. At completion, read the result screen on both sides and compare quest progress and inventory. A host result does not automatically prove a guest received the same reward. If the client shows a claim or collection step, follow it once and record the response.
Fix common boundaries
If the friend cannot join, verify the access requirement and whether the client is still on the same activity screen. If the lobby is ready but the session fails, capture the error and timing. If the activity succeeds but a quest does not move, compare the objective wording. If one player sees a different catalog or reward, record platform and region rather than assuming a bug.
Read the result on both accounts
After the activity ends, wait for the result screen to finish loading. Compare the visible completion status, quest counter, resource total and any claim button. If one account is a guest, do not assume that the host’s reward is shared. If the activity uses a session score, save the mode name and the player order. A co-op guide should explain what was observed, not promise a reward distribution that the public Steam description does not define.
If the friend disconnects before completion, record whether the host can finish, whether the session returns to the lobby, and whether a partial result is shown. Avoid repeated retries while an account balance or quest state is unclear. A fresh screenshot and a date help separate a network interruption from a changed online rule.
When the session works, write down the exact activity and whether the second player changed the objective or only added company. This keeps a useful co-op note separate from a universal multiplayer claim and gives future tests a repeatable starting point.
Save that note beside the date, device and platform. A later update can then be compared against a known successful session instead of a vague memory.
Keep it brief.
Keep claims narrow
The official launch announcement confirms Steam, iOS and Android availability, not cross-play or shared saves. This guide therefore does not promise that a mobile friend can join a Steam lobby. It also does not claim local co-op, split screen, voice chat, dedicated servers, or identical rewards without a current client check.
Co-op checklist
- Select an activity that visibly supports online co-op.
- Read access and reward text.
- Invite one friend and verify the lobby.
- Run one short activity.
- Compare completion, quest and inventory results.
- Date any successful or failed observation.
Return to Multiplayer for PvP and platform boundaries, or to Systems when the question is where a reward can be spent. Exact party sizes, matchmaking rules and reward distribution remain version-dependent.