Keep the room
Use when one or more friends are already inside.
Do not rebuild first. Help the missing friend compare the latest card while the joined players stay in place.
Host checklist tool
MECCHA CHAMELEON Private Lobby Checklist
Use this before friends search: build one room card, check host setup, test one outside join, and roll back the latest change if the room disappears.
Quick answer
Host first, share once, test once, then stop changing search fields.
A private lobby fails most often when friends are using different room details. The host's job is to freeze the search fields long enough for one outside friend to find and enter the room.
If your menu uses different labels, match the closest idea: region or server area, room name, access type, password, tag or filter, open slots, host lobby state, and the latest changed field.
-
1
Create or reopen the room before friends search, then keep the host waiting in the lobby.
-
2
Send one current room card so friends do not combine old password, tag, or region details.
-
3
Ask one friend outside the room to search first, then let the rest of the group join.
-
4
If it breaks, undo the latest search-critical change before rebuilding everything.
Lobby tool
Fill the room card while the host sets up.
Use the fields that exist in your room menu. Leave anything blank if it does not apply, then copy the generated card into your group chat.
Field lock
Lock search fields before tuning match feel.
Not every room option has the same risk. Anything friends use to find or enter the room should stay unchanged until one outside friend has found and joined it.
If your menu does not include one of these fields, skip it. The useful habit is tracking the fields your group can see and compare.
| Field | Can block search or entry? | Host action | Friend action |
|---|---|---|---|
| Room name | Yes, if friends identify or search by name. | Choose a short name, avoid mid-setup edits, and resend the full card if it changes. | Match spelling, spaces, and capitalization from the current card. |
| Region or server area | Yes, if room lists are separated by region. | Pick one value before friends search and keep it stable for the outside test. | Use the same value as the host before refreshing search. |
| Access type and password | Yes, especially when the room is visible but entry fails. | Set access before the card. If password changes, send the full card again. | Copy exact case and avoid using a password from an older message. |
| Tags, filters, or mode labels | Yes, if the room list can be narrowed by these labels. | Share the exact label, then avoid changing it while friends search. | Remove extra filters unless the current room card says to use them. |
| Player slots and lobby state | Yes, mostly for entry after the room is found. | Leave space for the full group and stay in lobby until friends are inside. | Search before the match starts and tell the host if the room looks full. |
| Match pacing or comfort options | Usually lower risk for search, but still worth announcing. | Tune after one outside friend can find and enter the room. | Wait for the host's updated card if the setting affects access or room identity. |
| Last changed field | It tells the group where to roll back first. | Write the latest changed field in the card before testing again. | If the room disappeared after that change, compare only the current card first. |
Host preflight
Check the host side before friends search.
This checklist is saved in this browser. Use it like a launch panel: prepare the room, freeze search fields, test once, then start.
Progress
0 of 0 checked
Friend join checks
Before a friend searches, make them compare the current card line by line.
This keeps the private lobby page useful without repeating a full join guide. The host owns the card; each friend matches it.
| Friend status | Host should ask | Likely mismatch | Safe next move |
|---|---|---|---|
| Cannot see the room | "Are your region, tag, room name, and filters exactly from the latest card?" | Old card, wrong region, hidden tag, spelling, or host already changed state. | Host resends the full card, friend clears extra filters, then searches once. |
| Sees room but cannot enter | "Does your password match exact capitalization, and is the room still open?" | Password, open slots, access type, or match already started. | Keep current room if others are inside; fix only the entry field if needed. |
| One friend joins, another cannot | "Are both friends using the same latest card and search state?" | One player has older room details or a different filter view. | Do not rebuild immediately. Compare the missing player's screen to the joined player's card. |
| Room disappears after an option change | "What was the last field the host changed?" | Search-critical field changed without a fresh card. | Undo that field once, send a fresh card, and test with one outside friend. |
| Everyone fails after an update | "Has each player restarted the game after the update?" | Mixed version or stale room state. | Everyone restarts, then host rebuilds a fresh room and sends a fresh card. |
Failure rollback
When the room breaks, change one thing back.
A failed private lobby gets worse when the host changes name, password, slots, tags, and access at the same time. Use this order to recover calmly.
-
Step 1
Freeze the room.
Host stops changing fields. Friends stop searching from old messages.
-
Step 2
Read the latest card out loud.
Compare region, name, access, password, tag, slots, lobby state, and last changed field.
-
Step 3
Undo the latest search-critical change.
If the password changed, change only password back. If tags changed, change only tags back.
-
Step 4
Run one outside search.
One friend searches from outside the lobby. The full group waits until that test works.
Undo once
Use when the room vanished after one change.
Reverse the last changed search field, resend the full card, then test with one outside friend.
Rebuild cleanly
Use when the room state is too messy to track.
Everyone restarts if needed, host creates a fresh room, and the group uses a new card only.
| Situation | Best move | Why | Do not |
|---|---|---|---|
| One friend is inside, one friend is missing | Keep the room and compare the missing friend's screen to the latest card. | The room already works for at least one player, so the failure is likely a mismatch or entry state. | Rebuild immediately and kick the joined player out. |
| Room vanished after a single field changed | Undo that field once, send a fresh card, and test with one outside friend. | A single rollback keeps the cause visible. | Change password, tag, region, and slots together. |
| Several settings changed and nobody knows which one mattered | Rebuild cleanly with a short name, simple access setup, and one new card. | A clean room is faster than guessing through old state. | Keep forwarding older cards or screenshots. |
| Everyone fails right after an update | Everyone restarts, then the host creates a fresh room and sends a new card. | This avoids mixed version and stale room-state confusion. | Keep refreshing the old room without restarting. |
Limits and safety
This tool keeps setup tidy; it does not override normal game behavior.
Use normal game menus and platform features. If the problem changes into account access, purchase state, sign-in, or platform availability, stop changing room fields and use official support paths.
Local storage note
Checklist progress and room-card fields can be saved in this browser on this device. The page does not need an account and does not submit your room-card entries.
What this cannot fix
It cannot force a room to appear, override platform state, or repair a broken sign-in session. It helps the host avoid avoidable setup mistakes.
What to avoid
Avoid account tools, unsafe third-party tools, or system changes you cannot easily reverse. Start with room fields, restarts after updates, and one clean outside search.
FAQ
Quick host checklist answers.
What should the host check before friends search?
Prepare a fresh room card, keep search-critical fields stable, confirm open slots, and have one friend test the room from outside the lobby.
Which room fields should stay locked while friends search?
Keep room name, region or server area, access type, password, tags or filters, open slots, and lobby state stable until one outside friend can find and enter the room.
How is this different from the join friends guide?
This page is for the host. It tracks room setup, current room-card details, friend readiness, outside search, and rollback steps. The join friends guide is for players trying to enter the room.
Should the host change several settings at once?
No. Change one search-critical field at a time, send a fresh room card, and test once before changing another field.
Does the checklist send my room details anywhere?
No. The checklist runs in your browser. It can save progress locally on your device so you do not lose the card during setup.
When should the host rebuild the room?
Rebuild after updates, after several field changes became hard to track, or after the group compared the latest room card and one outside search still fails.
What if the room menu uses different words?
Use the closest matching field. The goal is to share the current values friends need for search and entry, not to force a specific menu label.