Yume Utility
Welcomes, levels, invites, birthdays, check-ins, applications, voice tools, and the staff inbox.
Private by design
Yume began as a way to replace disconnected third-party bots with features that actually match the community using them.
It is privately developed, shaped by day-to-day server life, and able to change when Yume changes. There is no public installation flow because this project has one home.
How Yume is organised
Welcomes, levels, invites, birthdays, check-ins, applications, voice tools, and the staff inbox.
Economy, quests, Pusheen, UNO, casino games, QOTD, confessions, starboard, and live events.
Cases, sanctions, quarantine reviews, appeals, security workflows, and staff decisions.
Useful context
No. Yume is a private platform built around its own community and is not publicly distributed.
Utility, play, and moderation have different responsibilities. Keeping them separate makes each system clearer while the shared platform keeps them connected.
Only public project information and high-level service availability. Member conversations, moderation records, deployment details, and controls stay protected.
Only authorised Yume staff accounts. Access is permission-scoped, so each account sees only the tools assigned to its role.
Yes. Features evolve with the community, while persistent data, migrations, recovery, and audit systems keep changes dependable.