A running world can receive a marketplace install now. v0.7.0 handles mods and content packs live, and uses the same pinned package when a stopped world starts.
Mods, packs and systems
Store categories no longer decide what an item does when someone installs it. Mods sandbox-load. Maps, collections and audio import declarative packs. A sheet pack can add a sheet only for a type it declares. Audio packs currently stop at imported assets. System packages remain browse-only.
Creator Studio shows the package kind, compatible systems and direct dependencies before publication. It also shows the requested grants, version and artifact hash. Aether-published listings stop linking to the missing repository URL that older entries carried.
A running table can receive it
A GM chooses a compatible world and confirms the pinned version. For a running world, connected clients get the install through the existing table connection. A mod loads for each client. A content pack appears in Content for the GM to import, without stopping or reconnecting the table.
Stopped worlds keep the same install for their next launch. If an open world never acknowledges the command, the marketplace reports a retryable failure instead of saying it worked. A mod that fails to load on one client does not remove the working version from the other clients.
Checks before import
Before a content pack changes the world, Aether checks its bytes, identity, version, compatibility and dependencies. A failed check leaves the world unchanged. Direct dependencies have to be present; v0.7.0 does not solve a dependency tree for the GM.
The Content panel now has clear install, import, export, loading, failure and retry states. Roll Tables has an empty screen with its create action. Player View has named setup and error states.