Aether v0.33.0 opens System Studio: a place in the browser to build a game system without writing code, test it, and use it at your own table. During the alpha it is available to accounts that can host Worlds.
Build the pieces of a system
A System Project holds everything a game needs. Record Types describe characters, items or ships and their fields. Catalogues hold ready-made records, browsed as a list or a tree, imported from CSV or JSON, and checked for every reference before you delete an entry.
Views lay those records out. Build Sheets, workspace panels and Chat cards from reusable Parts, with exact Area widths and inline text. A Creation flow walks a player through making a new record one question at a time.
Rules cover six families: derived values, dice, effects, actions, macros and seeded generators. A Translations activity keeps every language, key and message for the project in one place.
Test before anyone plays
Save sample records and ordered cases, then run each case in a fresh private World tied to the project revision you are looking at.
Play it and share it
Install a saved revision in a World and its Sheets, Rules entries, workspace panel and Action results work in Play. Action cards in Chat keep their text, result values and up to six Action controls; the World checks every press. Library → New offers Basic or one of your Creation flows, and a GM can ask a player to create a record. Answers stay private until Finish.
Versions you build appear under Your systems when you create a World, within the usual three-World limit. When you change a system later, Studio compares it with the previous version and either moves established Worlds forward with migrations you preview first, or keeps the new version for new Worlds only.
To share a system, submit a version with its listing copy, media and the rights for each file. An Aether admin reviews it and can ask for changes; once approved, it appears in the Marketplace. Worlds that already use a version keep that exact version.
Projects can be exported as source, imported, forked under a new package ID, archived, transferred to one new owner, or recovered read-only through a designated account.
Build it from Claude Code
With an access token, an MCP client such as Claude Code can read a project, change its records, catalogues, sheets and rules, and run its previews and tests. During the alpha, Aether staff turn on MCP access per account; you then create tokens in Account settings, each lasting up to 90 days. Building versions, test Worlds and review submissions stay in Studio.
Also in this release
When you change your password, tick Sign out everywhere else to end your sessions on other devices. After five failed sign-ins for one email address, Aether refuses further attempts on it for up to 15 minutes.
What System Studio does not do yet: Creation flows have no point-buy step, effect durations count the affected record's turns rather than rounds, and Action inputs cannot offer a list of choices.