Export and publish Soundscape packages

A Soundscape package carries native cue, random-group, sequence, and Soundscape definitions together with the audio files they need. The result can be reviewed, published, installed in another world, and played through Aether's Audio panel.

#Export from a world

In a world where you are the GM, open View → Audio and find Export a Soundscape package. Select one or more Soundscapes, groups, or sequences, then enter:

• a package title and version such as 1.0.0;
• the author name;
• the license that applies to the included audio; and
• a rights declaration explaining why you may distribute every recording.

Aether follows every connected cue, group, and sequence, adds each verified audio file once, and replaces world-specific identifiers so the definitions remain connected elsewhere. It downloads <id>-<version>.aethersoundscape.json. Missing files, unsupported audio, circular references, or a package beyond the supported limits stop the export.

Playback remains under the table's control after installation. Participants choose whether to join table audio, keep their own volume settings, and hear the Soundscape when a GM starts it.

#Review the artifact

Format version 1 permits at most 128 audio files, 32 MiB per decoded file, 128 MiB of decoded audio, 256 definitions, 16 layers per Soundscape, 64 group entries or sequence steps, and 32 levels of linked definitions. Every file records its exact SHA-256 identity, byte count, file type, container, codec, duration, and filename.

You are responsible for the distribution rights to every included recording. Aether records your declaration with the exact artifact shown during publication and installation.

#Publish in Creator Studio

Sign in to Aether, then open Creator Studio from the dashboard's Mods menu or the Marketplace header. Choose New item, select Audio, and attach the .aethersoundscape.json file. The browser carries the package through inspection, listing details, and final review.

After upload, Creator Studio shows the exact package hash, which identifies the package bytes under review, together with definition counts, decoded total, formats, durations, author, license, and individual file hashes. Add a PNG, JPEG, or WebP cover between 600 by 300 and 5000 by 5000 pixels, write at least 20 characters of alt text, and confirm the distribution rights before publishing.

The Marketplace listing and the final Add-to-world consent repeat the exact package hash and contents. The GM chooses a world and confirms before anything changes.

#Install, upgrade, and uninstall

Before adding anything to a world, Aether checks the package structure, definition references, audio signatures, hashes, and size limits. The world changes only after the complete package passes, so a failed import leaves its existing assets and definitions in place.

Installing the same version and hash again keeps one copy. To distribute changed package bytes, publish a higher version. During an upgrade, untouched package resources keep their world IDs where safe. Edited resources become local copies, and the new package version receives its own managed copy. Resources still used by local work stay in the world.

Uninstall removes the resources that the package still manages. When local work uses one, Aether lists each reference so the GM can remove that use or adopt the resource as a local copy. Identical audio bytes remain available while any Asset or world reference needs them.