Kind conversation, clear boundaries
Chat & Safety
Choose the right chat scope, understand delivery and moderation, and use mute, block, and report controls safely.
On this pageChoose a conversation scope
Choose a conversation scope
Press Enter when gameplay input is available or use the Chat button to open Village chat. Tabs separate Nearby, Channel, Party, and System messages. The composer shows the selected scope before you send, so check it when a conversation is meant for a particular group.
Nearby is for players close enough to participate in local conversation. Channel reaches active players in the same channel. Party reaches members of your active party even when party members are in another world or channel where supported. System is reserved for game-authored connection, village, and activity notices; ordinary players cannot send a System message.
| Scope | Audience | Useful for |
|---|---|---|
| Nearby | Players close enough in the current world | Introductions and local coordination |
| Channel | Players in the current channel | World-wide conversation for that channel |
| Party | Members of the active party | Ready checks and cooperative coordination |
| System | Game-authored information | Connection, safety, and activity notices |
Writing and receiving messages
Messages are short, player-friendly chat lines rather than long-form posts. The composer shows the remaining space and prevents an oversized message. Starville sanitizes text, applies a bounded sending rate, and can reject messages that are empty, invalid, too frequent, or unavailable in the selected scope.
Typing suppresses movement input, so WASD and other gameplay keys become text while the composer is focused. Press Escape to close the composer or chat panel safely. Unread counters identify tabs with new messages. Optional local timestamps can be enabled in Settings.
A reconnect can restore a bounded recent history associated with the current live chat context, while entering a fresh session may start with an empty chat view. Chat is not a permanent public archive for players, although moderation may preserve evidence required to review a report.
Mute and block
Mute hides a player’s ordinary messages from your view without telling the sender that you muted them. Use it when you want less noise but do not need to prevent interaction. Unmute restores eligible future messages; it does not recreate messages that were not shown while muted.
Block is the stronger personal safety boundary. It prevents incompatible new social requests and can invalidate supported interactions between the two players. A block does not expose a reason to the other player. Unblocking does not automatically recreate a friendship, party invitation, gift, or trade that was cancelled.
Safety preferences are tied to the player account and should remain authoritative across a refresh. If an unwanted player still appears after a block, allow the current panel and presence state to refresh before assuming the action failed.
Report harmful chat
Open the safety menu on the relevant player message and choose Report. Select the closest category, then provide a concise explanation if requested. Report the message that contains the behavior rather than copying private account information into a different channel.
Reports can cover harassment, hateful or abusive language, spam, scams or suspicious links, impersonation, sexual content, and other policy concerns. A report creates a reviewable moderation record; it does not guarantee an immediate automated punishment. Human review and broader context may be needed.
Do not announce or coordinate retaliatory reporting. Use mute or block for immediate personal control, leave the conversation if needed, and preserve only the information the official report flow requests.
Availability and safe reporting
Core realtime chat is available now. Some unusual report, reconnect, restriction, and incompatible-state paths continue to be refined, so a moderation control may occasionally need a refresh or a careful report.
If a moderation control behaves unexpectedly, capture the public display name, approximate time, selected scope, visible error, and safe steps to reproduce. Never include private credentials or copied access headers in a community report.