Config Editor

The Config Editor provides a specialized interface for editing your skin’s config.json file. It works in both Simple Mode (visual form) and Expert Mode (raw JSON).

Opening the Config Editor

Single-click config.json in the Explorer

Simple Mode

Simple Mode displays config.json as an editable form.

Config Editor form interface

Screenshot ID: config-simple-mode

Visual form for editing configuration

Form Fields

Field	Input Type	Description
Name	Text input	Your skin’s display name
Description	Text area	Skin description
Includes	Folder picker	Asset folders to process

Editing Basic Fields

Click on any text field
Type your value
Save your changes (Ctrl/Cmd + S)

Editing config fields

Screenshot ID: config-editing-fields

Edit fields directly in the form

Managing Includes

The Includes section shows which asset folders will be processed:

Includes management UI

Screenshot ID: config-includes

Add and remove include paths

To add an include:

Select folder from picker (shows your project structure)
Or check Include All Folders

To remove an include:

Find the include in the list
Check the box off next to it

Common include paths:

graphics/icons
graphics/backgrounds
fonts
styles

Expert Mode

Expert Mode gives you direct JSON editing.

Config Editor in Expert Mode

Screenshot ID: config-expert-mode

Raw JSON editing with syntax highlighting

Code Features

Feature	Shortcut
Format document	Shift + Alt/Option + F
Toggle comment	Not supported in JSON
Duplicate line	Alt/Option + Shift + Down
Find	Ctrl/Cmd + F

Direct JSON Editing

Edit the JSON directly:


{
  "schema_version": 1,
  "name": "My Custom Skin",
  "author": "Your Name",
  "version": "1.0.0",
  "description": "A dark theme with blue accents",
  "includes": [
    "graphics/icons",
    "graphics/backgrounds"
  ]
}

Validation in Expert Mode

Expert Mode validates JSON syntax and schema:

JSON validation errors

Screenshot ID: config-validation-expert

Syntax and schema errors appear inline

Common errors:

Syntax errors (missing commas, quotes)
Invalid field types

Config Schema

Complete Example


{
  "schema_version": 1,
  "name": "Dark Theme Pro",
  "author": "John Doe",
  "version": "2.1.0",
  "description": "A sleek dark theme optimized for night gaming",
  "includes": [
    "graphics/icons",
    "graphics/backgrounds"
  ]
}

Common Tasks

Setting Up Asset Includes

When you add icons or backgrounds:

Simple Mode:

Click “Add Include”
Navigate to graphics/icons
Repeat for graphics/backgrounds

Expert Mode:


{
  "includes": [
    "graphics/icons",
    "graphics/backgrounds"
  ]
}

Bumping Version

When releasing updates:

Expert Mode:


"version": "1.0.1"

Troubleshooting

”Invalid JSON syntax”

Common mistakes in Expert Mode:


// Missing comma
{
  "schema_version": 1
  "name": "My Skin"  // ← Add comma above
}
 
// Trailing comma
{
  "includes": [
    "graphics/icons",  // ← Remove trailing comma if last item
  ]
}
 
// Wrong quotes
{
  'name': 'My Skin'  // ← Use double quotes
}

“schema_version must be 1”

Ensure it’s a number, not a string:


// Wrong
"schema_version": "2"
 
// Correct
"schema_version": 1

“Include path not found”

The folder doesn’t exist:

Create the folder in your project
Or remove it from includes

Changes not saving

Make sure you press Save (Ctrl/Cmd + S)
Check for validation errors blocking save
Try switching modes to force a refresh

Best Practices

Keep It Simple

Only include fields you actually use:


{
  "schema_version": 1,
  "name": "My Theme",
  "version": "1.0.0",
  "includes": ["graphics/icons"]
}

Use Meaningful Descriptions


"description": "Dark theme with blue accents, optimized for reduced eye strain during night gaming sessions"

Version Consistently

Update version when you make changes:


// Initial release
"version": "1.0.0"
 
// Bug fix
"version": "1.0.1"
 
// New feature (added icons)
"version": "1.1.0"
 
// Major redesign
"version": "2.0.0"

Next: Mapping Editor - Configure per-stylesheet targeting.