Update 02/11/2026 · Subscription and modules, account, contracts
Module subscriptions with plans and promo codes, an account page on the site, family creation with /init, contracts with payouts and an end date for inactivity.
- Subscription: family features are split into modules (members, applications, gatherers, contracts, shop, map, mini-games and others), and access to them comes from a subscription with a plan. Existing families kept full access, and a new family gets a trial.
- Subscription: a section without access is marked with a lock in the menu and leads to a page with a link to the account, and the bot names the unavailable module in the family language. Your data is kept and comes back with the subscription.
- Subscription: the bot messages the family owner 3 days before modules end and after they end.
- Subscription: when the project administrators remove a plan, all modules of the family are taken away at once instead of at their end dates.
- Account: a new page opened from your name in the site header: the Discord profile, birthday and your families with the role, subscription, modules with dates and a notice that the subscription ends soon.
- Promo codes: in the account you can preview a promo code, choose a family and redeem it — it gives a plan or a set of modules for a set time — and see the activation history there.
- Creating a family: after a new family application is approved, there are 7 days to run
/initon the server: the bot then creates the family and grants a trial if the applicant has not had one. The family name must be free on the server. - Creating a family: the bot messages the applicant about the approval (deadline, trial, administrator contacts), a rejection with the reason or an expired deadline, and if direct messages are closed it pings the administrators in the application thread.
/initreplies in the language chosen in the application, and the account shows the trial and the application state. - Contracts: new contract gatherings (
/create_messagewith thecontracttype): a group contract goes through start, finish, photo confirmation and closing the thread by button or automatically after 4 hours, a solo one is a contract type and one screenshot. Every participant gets the start and finish in direct messages; the permissions areCAN_JOIN_CONTRACT,CAN_MANAGE_CONTRACTSandCAN_MANAGE_CONTRACT_PAYOUTS. - Contracts: closing a contract opens a payout application like the other applications: a reviewer claims it, accepts it or rejects it with a reason, and can exclude participants from the payout with a reason. After a solo contract the bot replies with a link to the payout card.
- Applications: the "Mention" and "Call to voice" buttons on all five application types and on the shop order card also send the call in direct messages to the application author, the buyer or the payout participants, so it is not missed in a muted thread.
- Inactivity: an inactivity application now has a required end date (DD.MM, Moscow time). After it is accepted the status ends on its own at 00:00 Moscow time, the member gets a direct message, and the date shows on the card, in the inactivity list, in the profile and on the main panel.
- Applications: up to five screenshots (PNG, JPG, WEBP, GIF up to 10 MB) can be added to points and penalty-removal applications — they show as a gallery on the card, and the bot warns the author if the screenshots did not arrive.
- Applications: points and penalty-removal applications no longer have fields for expected points, reprimands and warns: the reviewer decides the amount when accepting.
- Gatherers: the gatherer message goes out with its buttons from the start and no longer loses them on a redraw (before, a bot crash could leave a gatherer without buttons and block a new gatherer of the same type); if a thread is left without a record, a button offers to delete it.
Ready to set up your family?
Log in with Discord, choose your server and add the bot: the site walks you through every step.