rpgjs-studio

Resolve the target map first, search media for a matching spritesheet and faceset, then POST to /api/events with the mapId and position. For scripted behavior, create a block collection and link it through the event's onAction trigger.

Call POST /api/map-generations with action prepare, an objective describing the visual style, dimensions, and optional terrain references. After the user confirms the credit estimate, call the same endpoint with action execute and poll the returned instance until finalized with a mapId.

Requests use an x-api-key header read from the RPGSTUDIO_API_KEY environment variable, scoped to one project. The key value must never be printed or stored, and 401 or 403 responses stop the task immediately.

Yes, generation debits metered API-key credits on execute. The workflow always calls the unified media endpoint with action estimate first, reports the cost, and only proceeds after explicit user confirmation; failed executions are refunded.

New Actors require a valid classId referencing a Class record in the same project. Create or search the Class first via /api/database/classes, then pass its _id when creating the Actor.

A character whose only behavior is one dialogue can store it directly in triggers[].typeData.dialogue on an onAction trigger. Use a block collection only when the interaction includes choices, rewards, state changes, shops, or movement.