Commercial server resources
Every resource audits itself on startup and reports exactly what it found — in plain language, with the file and the line. The server decides. Nothing fails quietly.
— Baillie · sole developer, BlackStone Development
I've spent about seven years in this ecosystem — running a server, working staff, and building resources for other people's communities. Most of that time went into debugging things I didn't write.
The pattern was always the same. Money moves and nothing is logged. A config key goes missing and the script quietly stops working. An event trusts whatever the client hands it. Then the documentation is one paragraph, and support takes four tickets to answer one question.
I came into this from cybersecurity and incident response, where a system that can't tell you what it just did is considered broken. That idea hasn't really arrived here yet. That's the gap I'm building into.
Every resource is written against the same standard. It's public so you can hold me to it.
Every resource audits itself on startup and prints what it found — faults and healthy state alike. Every fault is specific enough to fix without opening a ticket.
Configuration shapes behaviour; it never gatekeeps it. A missing or invalid value falls back to a documented default and logs which one it used. The resource still runs.
The client asks, the server decides, the client displays the result. No state exists on the client that the server didn't authorise.
Every handler that receives client data checks its shape, its range, and whether this player is actually allowed to make the request. Jobs and permissions are always checked server-side.
Nothing fails without saying so. Every fault produces a specific, actionable message in your console — not a blank screen and a guess.
I'm one person. Work happens in sequence, and I'd rather tell you where something actually is than promise a date.
Stocked, owned and free machine economies, configured per machine.
Phase 1 completeAccounts, cards, loans, crypto and investments — the hub other resources plug into.
In repairDrop in a resource, find out what's broken and where. Free to use.
In buildSee what's actually happening on your server — economy movement, duplication attempts, performance stalls, and who did what.
In developmentVehicle, medical and property cover that ties into the wider economy.
QueuedOwnership, staffing and revenue that runs without an admin in the loop.
QueuedBorrowing with real consequences, built on top of banking.
QueuedThose are already done well by people who've spent years on them. A fifth worse version helps nobody, and reselling someone else's work under a new name is a large part of why this scene has a trust problem. I'd rather build the things nobody has bothered to build properly.
One email per release. Nothing else, ever.