Defined pieces of work, not a catalogue of everything.

We write scripts and resources for a stated job: a gameplay system, a job, an interface, or a piece of economy or allowlist logic. The boundary of the resource stays clear, so it can be updated without rewriting the rest of the server.

This is custom work. We will not claim a script suits every framework. The first question is which framework you run, and what already depends on it.

New communities and existing ones both get stuck on structure: which resources load, who can do what, how data is organised, and what happens when a resource fails.

We help set that up, or simplify what is already there, so staff are not afraid to restart the server. We work with the stack you have.

Bots that moderate, answer common questions, post server status, or connect Discord to a dashboard. Aegis, our moderation bot, is the productised version of this work and includes a web dashboard.

A custom bot is for behaviour Aegis does not cover, or for a private integration with your server.

Moderation queues, configuration, allowlists, status. We build these as ordinary web applications, with explicit empty, loading, and error states.

They should be operable on a bad day as well as a good one, by people who did not write them.

Hierarchy, type, and contrast come first. Motion stays light, and it never carries information that the static screen does not.

The same standard applies to NUI and to dashboards: someone on staff should be able to tell what a control does without a tour.