Kanban and decks
Decks, cards, and lanes you actually use: features, bugs, polish, spikes. Filter by milestone without cloning a 40-field issue type forest.
Discord
Discord in the loop, not on the board
Game teams already live in Discord. The failure is treating a channel as the tracker. Keep Discord for conversation and slash-command intake. Keep Brainloot cards as the record. This is not a Unity page.
Hallway, board, Hand
Intake writes cards. Hand is what you ship. Discord stays the chat.
Discord
Keep Discord as the hallway. Feedback and status can become tracked cards so channels do not turn into a second backlog.
Learn more
My Hand
A small active set with a real WIP cap. Pull a few cards, ship them, then draw again. The rest of the board stays visible and quiet.
Learn more
Guilds and seats
A guild is the studio container: boards, roles, and paid seats. Start free. Solo Pro and Team when the cap matters.
Learn more
The hallway problem
A playtest drops. Someone pastes a crash in #bugs. Three replies rewrite the title. Nobody owns it. Next week the same crash is a new thread. That is Discord-as-tracker. The studio thinks it is communicating. The board is empty.
Discord task management for game teams means a pipe, not a second kanban. Chat stays chat. A card gets a title, a deck, and an owner.
/bug and /feature become cards
Brainloot Discord Connect can bind a guild so staff or players file /bug and /feature and the report lands on the workspace board. That intake ships on Solo Pro and Team. Free stays the web board, Hand, and Focus. We do not pretend a free Discord bot is the whole product.
Connect from guild settings when you are ready. Do not invent a shadow spreadsheet because a channel felt faster for one afternoon.
Triage on the board
Intake should fill a deck, not everyone's Hand. Close duplicates. Tag the real crash. Then draw. The daily loop is in game-dev task management. If you skip triage, Discord just became a firehose with nicer cards.
What this page is not
This is not an Unreal or Unity lander. Engine bridges are optional. This is not a case study and not a blog post about community growth. If you are shopping tools, use best game-dev software and the compare hub. Codecks Decky is a different bet (votes and community sync). Brainloot's bet is the studio board stays authoritative.
FAQ
- Should Discord be our task tracker?
- No. Discord is the hallway: pings, builds, playtest chat. Cards on a shared board are the record. When a thread becomes the task list, owners vanish and the board goes stale.
- What is Discord /bug and /feature intake in Brainloot?
- On Solo Pro and Team you can connect a Discord guild so /bug and /feature reports become tracked cards. Free plans keep Hand, Focus, and the web board. Intake is the paid loop that stops players and staff from inventing a second backlog in a channel.
- Does this replace Codecks Decky or a community forum?
- No. Brainloot intake is a hallway-to-board pipe, not a voting forum or a full community bot. If you need polls and public roadmaps in Discord, keep that tool. Use Brainloot when the studio board must stay the system of record.
- How does intake stay out of My Hand?
- New reports land as cards on a deck. They do not auto-fill anyone's Hand. Triage on the board, then pull a small Hand. That split is the daily ritual in the game-dev task management guide.
Related
Ready to level up your workflow?
Start free, pull a few cards into My Hand, and ship from one studio board.