
What to do when a shout-out fills your Rust server
When a creator sends a crowd to your Rust server, first find out whether the people already inside can play. A full, playable world calls for a queue message. A world that players cannot load into needs a status update and a closer look before you send more people there.
Check the game and Discord separately
Ask one player already inside if movement and interactions are working. Ask someone at the door what they see when they try to join. Compare that with your player count and the slot limit. A working world with a queue can stay on the current settings. Facepunch documents server.maxplayers as the player cap and notes that more players increase CPU demands.
If Discord is filling up with the same question, answer it in one visible post and have a helper point people there. If game joins are failing, pause further promotion and say which world is affected. Keep a known working alternative in the post only if players can join it and its play style is clear.
Give the creator a line they can repeat
For a full world, try ‘Harbour Solo is full and people are still playing. Use the normal join post for the queue. We’ll update #updates if we open more space.’ For a broken join, replace that instruction with when and where people should check again.
Review the rush after it passes. If players inside were fine but the queue stayed long at several busy sessions, choose a capacity change you can test. If the queue cleared when the stream ended, keep the working limit and save the status message for the next rush.