Cara GangA Dofus guild's hub and its Discord bot, from approved gear to recruitment tickets
For the Dofus guild whose staff I was part of, I built a site that gathers the approved gear, the breeding and profession guides and the services members offer each other, then a Discord bot that handles recruitment, dungeon runs, loans and events. Both share the same database.
The problem
Everything got lost in Discord
Recommended gear, breeding guides, who has which profession, who can run a dungeon, who borrowed what: it all lived in Discord channels and sank under the messages. Every newcomer asked the same questions again.
What I built
A site for the reference, a bot for the action
The site holds what has to last: gear approved by the staff and sorted by class, breeding guides with family trees, profession roadmaps, the charter and the announcements. The bot holds what moves: trial-period tickets for recruits, dungeon run requests, item loans, forgemagic, events, member profiles. Both read and write the same database.
What it changes
The staff stops repeating itself
A recruit finds the charter and the gear on their own. A run or loan request becomes a ticket, taken on by a named member, then closed. Gear submitted by members reaches the staff for approval before it is published.
What it changes for my clients
This project is unpaid: I was part of the guild's staff. It shows what I can do when a site and a bot have to share one database, with roles, approvals and tickets. The same mechanics apply to an association, a club or a team.
Key features
- Gear approved by the staffMembers submit, the staff approves or rejects from Discord, the site publishes
- Recruitment ticketsA private channel per candidate, a trial period that is followed, an automatic reminder to the recruiter, a decision and an archived transcript on closing
- Services between membersDungeon runs, item loans, forgemagic, sales: a request, a member who takes it on, a closing
- EventsCreated from Discord, sign-up by button, reminders before the start
- Member and profession profilesWho plays what, which professions at which level, readable with a single command
- Shared blocklistFlagged players are checked when they join the server, with a log of the decisions
Safeguards
Nothing is published on the site without a staff member's approval. The bot only holds the permissions it needs on the Discord server, and its secrets stay out of the code. The site shows no personal data about members beyond their in-game name.
Frequently asked questions
Why a Discord bot on top of the site?
Because the guild lives on Discord. Anything that calls for a quick action (a request, a ticket, a sign-up) happens where the members already are. The site keeps what has to stay readable over time.
Could you build the same thing for another community?
Yes. An association, a club, a guild or a team: the need is the same, a stable reference and a tool for action inside the group's messaging app. I start from how you are organised, not from a template.
Similar projects
A tool built for your team?
Internal tools start at €5,000 excl. VAT. We begin by scoping what you need.
Talk about what I needCase study updated on 25 September 2026