Manage world assets and storage

Open View → Assets to see the files stored for the current world. The Asset Library is GM-only. It includes map and token images, handout media, audio, models, other uploads, and files imported by content packages.

#Find and inspect a file

Search by filename or media type, filter by Images, Audio, Video, Models, or Other, then sort by newest, name, or size. Select a card to see:

• the declared MIME type and logical size;
• whether the backing file exists and its observed byte count;
• upload time, full SHA-256 content hash, and verified audio details where available;
• the package and version that supplied an imported file; and
• every current world document and field that refers to it.

Image cards use an authenticated preview. Audio details provide browser controls and wait for you to press play. The library shows filenames and product metadata while keeping storage credentials and infrastructure details private.

Choose a reference to open its source in the Library. References from a custom ruleset include their exact field path, so you can find and clear the use safely.

#Remove an unused asset

Select an asset with no listed uses and choose Remove. Aether checks the live world again immediately before removal, which proceeds while the file is still unused, locally managed, and requested by a GM.

Two Asset records may point at identical content. Removing one record keeps the shared backing file until no Asset record or world reference needs it.

For a package-owned asset, choose Adopt local copy when you intend to keep and manage it outside the package lifecycle. Adoption means later package upgrades and uninstall leave that resource alone. When local work still uses a package resource, the library lists each reference so you can remove the use or adopt the resource before uninstalling.

#Read storage measurements

World settings has a Storage section with separate Assets and World data rows. Billing rolls the same observations up across worlds and compares the measured bytes with the plan allowance.

These values are asynchronous samples. Each component has its own status and timestamp:

• measured has an observed byte count and successful sample time;
• stale retains the last measured bytes but marks a sample older than 30 minutes;
• unknown means the substrate did not supply a usable measurement; and
• failed means the last attempt could not complete.

Asset and world-data samples may have different timestamps. When only one has a usable measurement, Aether labels the account total as partial and keeps the other row's status visible. Storage limits remain informational in v0.16: the sampler reports usage without enforcing a quota or removing files.