Excry Game Guide, Wiki, Discord and Trello

The fastest route into Excry is a three-stop loop: start on the official wiki for the beginner path and verified numbers, join the official Discord when you need a live answer or a group to play with, and check the Trello board before you assume something is broken or missing. The wiki tells you what is true, the Discord tells you what to do right now, and Trello tells you what is already known and what is planned. Used in that order, you skip the most common new-player trap — asking a question that was already answered in writing months ago.

Quick comparison: which Excry resource to open first

What each part of the hub is actually good for

The wiki: your source of record

Treat the wiki as the place you go for anything that has a correct answer: stat tables, item sources, unlock requirements, map layouts, and the recommended order for the opening hours. The single most useful habit is checking a page’s last-edited timestamp against the current patch version, visible in the page’s revision history. A page last touched before the most recent balance patch is a hypothesis, not a fact.

The trade-off is that wikis are volunteer-written, and the pages people lean on hardest — drop tables, resistance values, anything touched by a rebalance — are exactly the ones most likely to be out of date. If a page’s last edit predates the current patch and the patch notes mention that system, verify before you build a plan around it.

The Discord: the fastest human answer

Discord is for questions the wiki can’t answer because they depend on your situation: whether your current setup is normal, whether a rough patch is a skill issue or a known problem, and who wants to group up right now. It is also the only one of the three that responds in minutes.

The trade-off is that Discord is a terrible archive. The same question gets three different answers depending on who is online, and the correct answer from six months ago is effectively invisible. Ask with the four details that make an answer possible — platform, patch version, how far you are, and the exact in-game wording or error text — and then copy anything useful into your own notes, because it will not be findable later.

The Trello board: what’s known and what’s planned

Trello lists usually map to a triage pipeline: reported, confirmed, in progress, and fixed-pending-patch, often with a separate roadmap column. It is the right first stop when something feels broken, because checking it takes under a minute and prevents duplicate reports that bury real ones.

The trade-off is that cards are intentions. They get merged, reworded, moved backward, or sit untouched for months. A card in a planned column is not a release date, and a card that disappears usually means it was consolidated rather than cancelled.

How to use all three in the right order

1. Write your question in one sentence. Reason: a specific question gets a specific answer, and the act of writing it usually reveals that you already know which of the three resources to check.
2. Search the wiki using the exact in-game term, not the community nickname. Reason: page titles generally match in-game strings, while nicknames drift between patches and between groups.
3. Check the page’s last-edited date against the current patch version. Reason: this is the fastest reliability test available, and it takes about ten seconds.
4. If the wiki is silent or stale, search the Discord before posting. Reason: many “unanswered” questions were answered last week and are recoverable with a channel search.
5. Post with platform, patch version, progress point, and exact wording. Reason: without these, responders have to ask three follow-up questions, which is when threads die.
6. Check Trello before calling anything a bug. Reason: known issues are triaged there, and a duplicate report costs you more time than the check would have.
7. Write the answer into your own notes. Reason: none of the three is a reliable personal archive for your specific situation.

Which resource to lean on, by situation

A worked example: budgeting your first 10 hours

Suppose you play about 6 hours a week across three sessions. Spending 30 minutes in the wiki before your first session and 10 minutes per session waiting on Discord answers costs roughly 30 minutes a week — about 8% of your play time. Skipping the wiki read and asking everything in Discord instead typically costs 10–15 minutes per question in wait time plus follow-ups, and you only get answers when someone knowledgeable is online.

The break-even is simple: if a wiki lookup takes 3 minutes and a Discord answer takes 12, any question with a written answer is worth four times the effort to look up. Reserve Discord for the questions that genuinely have no written answer — “is this normal,” “does anyone want to run this,” “did the patch change this yesterday.”

Common mistakes that cost the most time

• Trusting a page without checking its edit date. Old numbers are worse than no numbers, because they look authoritative.
• Asking in the wrong Discord channel. General chat moves fast; a dedicated help channel keeps your question visible for hours.
• Paraphrasing an error instead of pasting it. Exact wording is usually the fastest path to a known-issue card.
• Treating Trello as a schedule. Plans change, and a card’s position says nothing about timing.
• Reading build guides before you understand the systems. Advice written for one patch is noise once the underlying rules move.
• Not checking whether the wiki, Discord, or board you’re using is the one linked from the game itself. Community-run spaces can look identical and be far less current.

Frequently Asked Questions

What should I read on the Excry wiki first?

Start with the beginner or getting-started page, then the controls and interface page, then whatever progression page covers your first major unlock. Reading the beginner path end-to-end takes about 30 minutes and prevents most of the early mistakes that are expensive to undo later. Leave stat tables, drop rates, and build pages until you actually need a number from them.

How do I know if an Excry wiki page is out of date?

Open the page’s revision history and compare the last-edited date with the current patch version. If the last edit predates the most recent patch and that patch’s notes mention the system the page covers, treat the page as unverified. Cross-checking one number against the patch notes or a recent Discord discussion is usually enough to tell whether the whole page needs a second look.

Where should I report an Excry bug?

Check the Trello board first to see whether it is already triaged, then post in the Discord’s bug or support channel with your platform, patch version, and the exact error text or a short clip. Duplicate reports dilute attention, so a minute of searching saves everyone time. Keep the report factual — what you did, what you expected, and what happened.

Is the Excry Trello board a release schedule?

No. Trello boards of this kind track triage state and intent, not dates. A card can sit in a planned column for months, get merged into another card, or move backward when a fix causes a new problem. Use it to find out whether something is already known and roughly how far along it is, not to plan around a specific date.

Do I need Discord to play Excry?

No — the wiki covers everything with a written answer, and you can play through the early game without ever joining. Discord becomes genuinely useful when you want a group, when you hit something that looks like a bug, or when a patch just landed and the wiki hasn’t caught up. If you do join, mute everything except the channels you actually read.

How do I avoid spoilers in the Excry Discord?

Most servers separate story and endgame discussion into dedicated channels, so read the channel list before you start scrolling. Turn off previews for image-heavy channels, and search for terms rather than browsing recent history. If a server’s spoiler rules aren’t obvious, ask a moderator which channels are safe for your progress point.