Demo content

Unreal

A new environment is empty, and an empty stash looks exactly like a broken one. This fills one in so you can tell.

Setting it up

Open the Raid State toolbar button, pick the template your game uses, and click Set up demo content. It is also under Tools → Raid State → Set Up Demo Content.

In order, it:

reads your environment's catalogue,
signs in a demo player called raidstate-editor-demo,
creates a stash and a loadout with the layout your template uses,
and grants the stash a spread of items.

Push your item definitions first

The demo has nothing to grant until your catalogue exists. Run Tools → Raid State → Push Item Definitions first; the demo will tell you if you forget.

The loot is your own items

The stash is filled from the catalogue your project pushed, not from a canned list of famous guns. That is deliberate, and it is the reason this can be one button.

In USME an item's id is its DataTable row name. A demo that granted AK74 would write a row your game cannot draw — no icon, no mesh, no name — and the stash would render as a grid of blank squares, which looks like the plugin failing. Granting items your project already defines means the stash comes up with your art on the first try, and it means the same button works for a template nobody here has seen.

The choice is spread across item types rather than taken in order, because a table written the usual way starts with a dozen consumables and a stash holding twelve bandages demonstrates nothing.

Picking the template

The only thing the template really selects is the layout of the containers it creates.

USME and Other slot-based inventory — a flat run of equal squares. An 80-slot stash and a 24-slot loadout, matching the sample lobby widget.
Grid with footprints — items carry coordinates and a size. A 10×8 stash and a 6×4 loadout.

A container's layout is fixed when it is created

containers/ensure is idempotent by owner and kind, so asking for a different layout later returns the original container rather than converting it. If you pick the wrong one, delete the container from the dashboard before trying again.

Running it twice

Nothing happens. If the stash already holds anything the demo stops and says so, because that stash may hold something you put there yourself and this button is not entitled to delete it.

Underneath, each grant carries an idempotency key derived from the item and quantity rather than a fresh random one, so a double click or a run that failed halfway replays the original answer instead of granting a second rifle:

the key one grant is sent with

Idempotency-Key: raidstate-demo:usme:ak74:1

Development environments only

The button is disabled when the resolved key is a production key. The demo player signs in anonymously, and the server refuses anonymous authentication outside development — so this could not seed a live economy even if it tried. It is refused at the click as well, because an error raised on the button reads as a rule and the same error four requests deep reads as a bug.

Cleaning up

The demo player is an ordinary player. Delete its containers, or ban it, from the dashboard — there is nothing special about it beyond a stable name, which exists so a second click finds the same stash rather than leaving a trail of abandoned demo players behind.