Read before you adopt

Care Guide

A walkthrough of the systems ServerPet is being built around. This is a design preview, not live documentation: commands, numbers, and names can change before launch.

⚠️ In development. ServerPet is not invitable yet. This guide describes the design in the repo's DESIGN.md so future communities know what they are signing up for.

1. Overview design preview

A server adopts one communal pet, pinned to a chosen channel. It has real needs, and the community collectively keeps it alive and thriving. The hook is shared responsibility: it is the server's pet, and its health is a reflection of the community.

2. Activity-Driven Care core mechanic

Member activity generates care energy, the resource the server spends on care actions:

3. The Five Needs in tuning

The pet tracks hunger, happiness, energy, cleanliness, and health. Health reflects the others over time: keep four green and the fifth follows. The landing page console is a live miniature of this exact loop.

4. Neglect, Revival & Streaks stakes

5. Rewards & Evolutions in design

6. Leaderboards & Flexing cross-server

7. Admin Setup scoped

Admins pick the pet channel (/setpetchannel), name the pet, and configure who can do what. Everything is per-server and properly permission-scoped from day one. Larger servers may eventually unlock multiple pets (expansion idea, not launch scope).

8. The SpartanBots Ecosystem cross-bot

ServerPet shares its rarity ladder, premium currency (Drachmas), and Patreon with the whole family: AestherBot, TackleBot, GargoyleBot, and the in-development TerraBot, PondBot, and BinderBot. Care and progress are earnable only; premium buys cosmetics and convenience, never power.

Questions, ideas, or the urge to alpha test? Join the SpartanBots support server.