Community · Player guide

GRAIN ROT Discord: Official Invite and Help Routes

The official launch FAQ uses Discord as the central route for finding a group, reporting bugs, sending feedback and opening technical tickets.

Quick answer: The official invite is discord.gg/grainrot. Use the server’s current role prompts to reach Looking for Group, Bug Reports, Suggestions & Feedback and technical-ticket support. Never post account credentials, save archives or a private lobby password in a public channel.

Join the official server safely

Use the link from the developer-controlled FAQ or this verified redirect. Avoid lookalike invites sent by unknown accounts.

An invite can change or expire, so confirm that the landing server identifies the same game, developer and official channels. Do not enter Steam credentials into a Discord bot. Discord and Steam sign-ins are separate.

Find a group to play with

The FAQ directs players to the roles channel before accessing content-specific channels, including Looking for Group. Include region, language, preferred crew size and whether the lobby is public, friends-only or invite-only. Do not post account credentials or personal contact information.

The game is balanced around roughly four players, but host settings can support different counts. State whether the group is new, spoiler-free or working on a particular objective. Clear expectations reduce griefing more effectively than adding unknown players without a plan.

Report a bug

Use the Bug Report route for a game defect and include the current patch, operating system, host/client role, save origin and exact last action. A screenshot of the objective or error is more useful than a generic statement that the game is broken. Remove personal information from logs or file paths.

Test without unsupported modifications and verify Steam files before reporting a vanilla bug. If the issue came from an old demo or playtest save, say so. The official FAQ recommends a fresh full-release save for progression checks.

Open a technical ticket in the right place

The official FAQ points technical support to the open-tech-ticket route. Use it for issues that need structured help rather than repeating the same message across public channels. Follow the server’s visible category rules.

Do not send passwords, one-time codes or payment data to a helper. A legitimate support process should not need them. If someone requests an executable or remote-control session outside the official workflow, stop and verify with moderators.

Suggestions and feedback

The official roles flow includes a Suggestions & Feedback channel. Describe the problem, the player goal and an example instead of presenting one implementation as the only solution. Separate balance feedback from reproducible bugs.

Check whether the suggestion already exists and add your details to the same discussion. Keeping similar requests together makes the problem and proposed solution easier to understand.

Community and account safety

Official channels can still contain user-generated links. Do not download trainers, cracked builds, unknown mod loaders or files that require disabling security protections. The current game does not document an official mod SDK.

Use host privacy, grief protection and ban controls for multiplayer safety. Patch 1.08 made bans persistent and strengthened password-server security. Report abusive behavior through the server and in-game tools rather than sharing personal data publicly.

Prepare a useful support or group-finding post

For Looking for Group, include region or timezone, preferred language, current progression and whether the lobby is public, friends-only, invite-only or private. Say whether the group is learning, farming a resource or attempting a specific quest so players can choose the right session.

For a bug, provide the game version, operating system, host or client role, lobby size and a short sequence that reproduces the issue. Add screenshots or logs only when the official support route requests them, and remove personal information before uploading. Search the Bug Report area first and add your details to an existing report when it matches. If the problem is technical or account-specific, use the open-tech-ticket route named by the official FAQ instead of asking random members for files or credentials.

Official Discord FAQ

What is the official GRAIN ROT Discord?

discord.gg/grainrot, as linked by the official game-account FAQ.

Where do I find teammates?

Use the roles channel, then the Looking for Group area described by the FAQ.

Where do I report a technical problem?

Use Bug Report for reproducible defects and the open-tech-ticket route for technical support.

Helpful links

Official pages, patch notes and practical walkthroughs for additional context.

Keep reading