Skip to content

Configuration Overview

Glamour uses a JSON-based configuration system that makes it easy to customize particle effects without modifying code.

All configuration files are stored in config/glamour/:

config/glamour/
├── particles/ # Pokemon sendout/ambient particles
│ ├── confetti_burst.json
│ ├── sparkle_aura.json
│ └── ...
├── persistent_particles/ # Condition-based persistent particles
│ ├── shiny_sparkle.json
│ ├── legendary_aura.json
│ └── ...
└── config.json # Main mod configuration

config/glamour/config.json controls mod-wide settings:

{
"debug": false,
"database": {
"type": "sqlite",
"path": "glamour_data.db"
},
"particleSystem": {
"maxRenderDistance": 32,
"defaultInterval": 100
}
}
  • debug: Enable debug logging
  • database: Database configuration for state persistence
  • particleSystem: Global particle system settings

Particle configurations are split into two types:

These are manually applied particles that players can select through the GUI or commands.

Structure:

{
"id": "confetti_burst",
"displayName": "Confetti Burst",
"description": "Celebratory confetti explosion on sendout",
"type": "SENDOUT",
"particleResourceId": "confetti",
"category": "celebration",
"rarity": "COMMON",
"settings": {
"intervalTicks": 100,
"delayTicks": 60,
"durationTicks": 20
}
}

2. Persistent Particles (persistent_particles/)

Section titled “2. Persistent Particles (persistent_particles/)”

These are condition-based particles that automatically apply when conditions are met.

Structure:

{
"id": "shiny_sparkle",
"particleResourceId": "sparkle",
"priority": 100,
"settings": {
"intervalTicks": 40,
"durationTicks": 10,
"particleCount": 3,
"radius": 1.0,
"followEntity": true,
"maxDistance": 32
},
"conditions": {
"isShiny": true
}
}
FieldTypeDescription
idStringUnique identifier for the particle effect
particleResourceIdStringCobblemon snowstorm particle ID
settingsObjectParticle behavior settings
  • SENDOUT: Plays when Pokemon is sent out from Pokeball
  • AMBIENT: Continuously plays while Pokemon is out

Rarity affects GUI sorting and can be used for permissions:

  • COMMON - Basic particles available to all
  • UNCOMMON - Slightly rare effects
  • RARE - Moderately rare effects
  • EPIC - Very rare effects
  • LEGENDARY - Extremely rare effects
  • MYTHICAL - The rarest effects
SettingDescriptionDefault
intervalTicksTicks between particle spawns100
delayTicksDelay before first spawn0
durationTicksHow long particles last20
particleCountNumber of particles per spawn1
radiusSpawn radius around entity1.0
followEntityAttach to entity vs world positiontrue
maxDistanceMax render distance in blocks32

Categories help organize particles in the GUI. Common categories include:

  • celebration - Party and celebratory effects
  • elemental - Fire, water, electric, etc.
  • magical - Mystical and arcane effects
  • nature - Plants, flowers, leaves
  • cosmic - Stars, galaxies, space-themed
  • seasonal - Holiday and seasonal effects

You can create custom categories by simply using a new category name in your configs.

After editing configuration files, reload them without restarting:

/particles reload

Or for persistent particles:

/persistentparticles reload

On first launch, Glamour creates example configurations. You can:

  • Edit these examples to customize them
  • Delete examples you don’t want
  • Create new files following the same structure
  1. Unique IDs: Use descriptive, unique IDs for each particle
  2. Test Values: Start with conservative interval/duration values
  3. Performance: Higher particle counts and shorter intervals impact performance
  4. Permissions: Match category/rarity structure to your permission system
  5. Backup: Keep backups of working configurations before experimenting