Skip to main content

Run one Rust event with another community

Agree on one Rust world and one place to read the current event details before either Discord announces the event. Each community can introduce it in its own voice while sending players to the same time, joining instructions and fallback.

Agree which jobs each community owns

Have the game host verify the world, its meeting point and playable capacity. Give each Discord one contact who can publish changes and answer their own members. If there is a separate livestream, name where that will happen as well. Facepunch’s 2023 Charitable Rust announcement illustrates the value of naming the official stream even when multiple creators are taking part.

If you use a Discord event as the shared reference, check what members of the partner Discord can see. Use an Event Server Invite when they are welcome to join the hosting Discord. If partners will stay in their own Discords, share a page they can open or put the essential details in both posts.

Test the two announcements together

Swap drafts and have one person from each side follow the other post. Both should reach the same game world and see who to ask if the meeting point changes. Agree on one person to call a delay or cancellation, then have each Discord contact acknowledge that they posted it.

The shared brief can fit on one screen. Include the playable world, start time, join path, gathering point, who calls changes, and the channel each community will use for updates.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details