The official Dimraeth website points to the Discord invite discord.gg/dimraeth. Use the Official Channels Discord link in this site's footer or the Discord link on Mudtek's game website to reach that invitation. The developer describes Discord as the main place for day-to-day patch notes, bug reports, balance discussion, build sharing and direct conversation with the team.
For practical help, the official FAQ names #🐞｜bug-reports for bugs and #🙋｜looking-for-group for finding co-op players. Channel names and access arrangements can change. Follow the server information you see after joining; channel access and onboarding may change.
Reach the official invitation
Start from an official game link rather than an arbitrary Discord search result. The developer's website uses the Dimraeth invitation directly. That connection matters because a server with a matching game name or avatar can still be an unrelated fan community.
- Open the site's Official Channels Discord link or the developer website's Discord link.
- Review the invitation destination before accepting it.
- Use your intended Discord account.
- Read the rules and any current onboarding instructions presented by the server.
- Find the channel that matches your task before posting.
Choose the right place for your request
Describe the task you need help with before deciding where to post. Joining the community, finding a party, reporting a reproducible fault and suggesting a balance change are different tasks. Keeping them separate lets other readers recognise what response would be useful.
| Your goal | Starting point described by the developer | Useful information to bring |
|---|---|---|
| Report a bug or strange behaviour | The FAQ's bug-reports channel | What happened, where and how to reproduce it |
| Find people to play with | The FAQ's looking-for-group channel | Your intended activity and session availability |
| Discuss a build | Current build-sharing discussions | Race, class and the specific interaction |
| Suggest a balance change | Current feedback or balance discussion | The behaviour and its effect on play |
| Read changes | Current patch-note or announcement information | The version or feature you are checking |
A general complaint can contain a useful issue, but it rarely tells someone how to help. Replace a broad statement that the game is broken with the specific state you reached. For example, say whether a problem occurs before the menu, when loading a character or after a particular quest interaction. Those distinctions also help you choose the site's crashing guide or missing-character guide before writing the report.
Prepare a useful bug report
The official FAQ asks for details about what happened, where and how, and says screenshots or videos are helpful. Start with that information. You do not need to prove the cause of a fault before reporting an observation, but you should keep an observed result separate from your explanation of why it occurred.
A useful report can follow this order:
- Give the installed game version when you can identify it.
- State whether the session is solo, hosted by you or joined from another player.
- Name the location, quest, item or menu involved.
- List the shortest sequence of actions that leads to the issue.
- Describe the result you expected and the result you saw.
- Add the relevant screenshot, short video or exact error message.
- Mention whether it happened once or whether you can reproduce it.
Keep the reproduction steps limited to what you actually performed. If you changed several settings and the problem disappeared, you have not isolated which change mattered. Say what changed rather than presenting one step as a guaranteed fix. That distinction prevents other players from unnecessarily changing or deleting a working setup.
Include what happened, where it happened and how to reproduce it when opening a report.
Make screenshots and clips explain the state
Choose evidence that shows the problem being reported. A character-selection issue needs the relevant selection state; a blocked quest needs the objective text and interaction; a missing crafting entry needs the menu where you expected it. A scenic screenshot of the same region usually cannot explain a failure.
For a video, begin close enough to the triggering action that the sequence is clear. You do not need to attach an entire play session when a short transition demonstrates the issue. If the behaviour depends on joining another player's world, include that context in the written description so a clip of the final result is not mistaken for a solo-session test.
Avoid cropping away the name or indicator that identifies the reported state. At the same time, review the image for unrelated personal information before posting publicly. The aim is a readable game report, not a screenshot of every open application on your computer.
Find a co-op group that wants the same session
The FAQ directs players without a party to #🙋｜looking-for-group. Dimraeth supports solo play and up to eight players in drop-in/drop-out co-op, so you can look for a small group without treating a full party as a requirement.
Before posting, decide what you want to do. Continuing a main quest, experimenting with a build, gathering materials and replaying a boss can all lead to different expectations. A message asking for anyone to play is easy to understand but gives potential partners little basis for deciding whether the session suits them.
Include the activity, your current progression, the time you plan to play and the kind of pace you prefer. State whether you can host or would rather join, and whether you want a short attempt or a longer session. These details are useful preferences; they are not requirements imposed by the game or server.
If a language or voice-chat preference matters to you, say so before the group starts. Do not infer that the server guarantees a language-specific party, a matchmaking queue or immediate availability. Looking-for-group is a place to find other people, not a promise that someone will be ready at the moment you post.
Agree on world progress and loot expectations
Co-op plans should account for the game's distinction between a hero and a world. The official Steam description says level, equipment, inventory, spells and personal progression travel with the hero. Story progress, recruited allies and buildings remain tied to each world.
That means joining a friend is not simply choosing a character and assuming every world-related result belongs to everyone in the same way. Agree which world the session uses and what the party is trying to advance. This discussion can be brief, but it prevents one player expecting story progress in their own world while the group works elsewhere.
The same official description does not establish how every enemy drop is allocated. If personal loot is essential to your party plan, use the personal-loot guide and the current game information rather than treating character portability as proof of an allocation rule. Ask about the actual behaviour you intend to use.
Ask build questions that can be answered
The developer identifies build sharing as one of Discord's day-to-day uses. To make a build question useful, include the race, class, current stage and interaction you are trying to improve. The current Early Access roster has Human, Minotaur and Elf races and Brawler, Mage and Shadow classes; larger promotional counts are future scope.
A request for the best build can mean faster clearing, safer boss attempts, stronger sustained casting or a particular companion choice. Name the desired result so replies can address the same problem. You do not need to post every item when a single tooltip or skill interaction is the focus.
Use the build comparison guide if you are still choosing a direction. Use a specific question when you already have a direction and something does not work as expected. Discord discussion should not replace reading the exact current tooltip when the question depends on a particular modifier.
Separate feedback from bug diagnosis
A feature can work as designed and still be frustrating. Treat a reproducible failure as a bug report, and treat a request to change behaviour as feedback unless you have evidence that the current result contradicts the intended function. That separation helps the team understand whether you need a repair or are proposing a different design.
For feedback, describe the part of the experience that creates the problem. If you find a repeated action tedious, explain where it interrupts play and what you would prefer. If you think an upgrade weakens a build, identify the effect you lose and the situation where it matters. Those details are more actionable than a general statement that every upgrade or quest needs redesigning.
Follow announcements without inventing deadlines
Steam's Early Access description calls Discord a place for patch notes and direct developer discussion. Read an announcement's actual status before treating it as a released feature. A plan, a test invitation and a live update are different stages.
If a channel is missing or a link fails, return to the current official website invite and check the server information that is visible to your account. This page cannot promise a particular access process or an immediate response from a small development team. If you use a different support route, keep the same concise description and evidence rather than rewriting the observation into a stronger claim.
Keep a report useful after the first message
The FAQ describes starting a thread in the bug-reports channel. Keep later evidence with that same issue where the current server arrangement allows it. A new clip, an exact version or a shorter reproduction sequence should clarify the existing report rather than turn one fault into several disconnected conversations.
After a patch, keep the old report's version visible and describe what happens in the new version separately. A patch-note statement that a bug was addressed and your observation that it still occurs can coexist until the exact case is identified. Conversely, if the original reproduction no longer fails, report that narrower result without claiming the update fixed every related symptom.