Configuration Schema
JSON schema for rooomAvatars avatar settings used by URL parameters, config messages, and the REST API.
Are you an LLM? You can read better optimized documentation at /docs/rooom-avatars/editor/configuration-schema.md for this page in Markdown format
The rooomAvatars Editor uses a JSON settings object to represent the current avatar configuration. You can provide it via the URL parameters, via a config message, or in the body of a POST /avatar request.
Overview
The top-level object has a required version field and optional sections such as body, head, hair, and cloth.
Fields
version(string, required): currently"1.0.0"body(object, optional)gender("masculine"|"feminine")skinColor(string, hex color)
head(object, optional)id(string)eyeColor(string, hex color, optional)
hair(object, optional)id(string)color(string, hex color, optional)
beard(object, optional)id(string)color(string, hex color, optional)
cloth(object, optional)id(string)coatColor,topColor,pantsColor,shoesColor(string, optional)
hat(object, optional)id(string)
Example
Here is a complete avatar configuration including the required version field and optional sections for body, head, hair, and cloth:
json
{
"version": "1.0.0",
"body": { "gender": "feminine", "skinColor": "#c58c85" },
"head": { "id": "F_Head_1", "eyeColor": "#6b8e6b" },
"hair": { "id": "F_Hair_05", "color": "#8B4513" },
"cloth": { "id": "F_Set_18" }
}