Registry

The World Object manages everything relating to the overworld in Kristal.
A globally available instance of World is stored in Game.world.

Actors are a type of data class that represent the visuals of a character - anything that is some type of character, be it the player, an NPC, or an enemy in battle, it will require an actor.
As a data class, actors are stored in scripts/data/actors/, and extend this class. Their filepath starting from here becomes their id, unless an id is specified as an argument to Class().

The class that all Battle bullets in Kristal originate from.
Generic bullets can be spawned into a wave with Wave:spawnBullet(texture, x, y)
Files in scripts/battle/bullets will also be loaded as bullets and should Extend this class. Extension bullets can be spawned into a wave with Wave:spawnBullet(id, ...) - their id defaults to their filepath, starting from scripts/battle/bullets. Additional arguments ... are passed into the bullet type's init function.

Events are used as the base class for objects in the Overworld (in most cases) Custom events should be defined in scripts/world/events and extend from this class. They will receive an id based on their filepath from this location. Custom events only ever recieve a data argument in their init() function that contains all of the data about the object in the map. Included in the data table is the properties table, which contains every property in the object's Custom Properties in Tiled. Events can be placed in maps by placing a shape on any objects layer and setting its name to the id of the event that should be created.

Encounters detail the setup of unique battles in Kristal, from the enemies that appear to the environment and special mechanics.
Encounter files should be placed inside scripts/battle/encounters/.

EnemyBattlers are a type of Battler that represent enemies, defining all their properties and behaviours.
Every enemy defined in a mod should be located in its own file in scripts/battle/enemies/, and should extend this class.
Each enemy is assigned an id that defaults to their filepath starting from scripts/battle/enemies, unless an id is specified as an argument to Class().
Enemies are added to battles in the encounter, with Encounter:addEnemy(enemy, x, y, ...), where enemy is their unique id, and all enemies for the current battle reside in Game.battle.enemies

Recruit data is separate to enemies, see Recruit for how to set up a corresponding recruit.

Events are used as the base class for objects in the Overworld (in most cases) Custom events should be defined in scripts/world/events and extend from this class. They will receive an id based on their filepath from this location. Custom events only ever recieve a data argument in their init() function that contains all of the data about the object in the map. Included in the data table is the properties table, which contains every property in the object's Custom Properties in Tiled. Events can be placed in maps by placing a shape on any objects layer and setting its name to the id of the event that should be created.

The Item class represents all types of item in Kristal.
Items are data files contained in scripts/data/items that should extend this class or one of its extensions (see below), and their filepath starting at this location becomes their id, unless an id for them is specified as the second argument to Class().
There are extensions of item that provide additional functionality when extended from: HealItem and TensionItem
Items that are Light World equipment should extend LightEquipItem instead of this class (it provides all of the same fields and functions as Item).
Items can be given to the player directly in the code through Inventory:addItem().

Stores and manages the currently loaded map.
If a map in scrips/world/maps is defined as a folder, map data can be placed in data.lua, and a file named map.lua can be used to define a custom Map object for that map.

The PartyMember class is a type of data class that stores information about a member of the party.
PartyMembers are stored in scripts/data/party, and extend this class. Their filepath starting from here becomes their id, unless an id is specified as an argument to Class().

Recruits are data files that define the properties of recruitable enemies.
Recruits are stored in scripts/data/recruits, and extend this class. Their filepath starting from here becomes their id, unless an id is specified as an argument to Class().
A recruit is linked to one enemy with the same id as it.

The class which all Shops in Kristal use.
Shop files should be located in scripts/shops, and will use their filepath relative to this location as an id by default.
Either World:shopTransition() or a Transition event with the property shop defined can be used to enter shops.

Spells are data files that extend this Spell class to define a castable spell.
Spells are stored in scripts/data/spells, and their filepath starting at this location becomes their id, unless an id for them is specified as the second argument to Class(). Spells are learned by PartyMembers, and they can be given a spell by calling PartyMember:addSpell() (likewise, PartyMember:removeSpell() removes a spell).

Waves are the bullet patterns that enemies use in battle.
Waves are defined in files in scripts/battle/waves/ and should extend this class.
Each wave is assigned an id that defaults to their filepath starting from scripts/battle/waves, unless an id is specified as an argument to Class().
Wave ids can be placed into an EnemyBattlers waves table, or Waves returned from EnemyBattler:selectWave() or Encounter:getNextWaves() to to be used in battle.
Multiple waves can run in a single defending turn, but if multiple attackers select the same wave only one instance is created; see Wave:getAttackers() for determining how many enemies are using a particular wave.

The class that all World bullets in Kristal originate from.
Generic bullets can be spawned into the world with Game.world:spawnBullet(texture, x, y)
Files in scripts/world/bullets will also be loaded as world bullets and should Extend this class. Extension bullets can be spawned into the world with Game.world:spawnBullet(id, ...) - their id defaults to their filepath, starting from scripts/world/bullets. Additional arguments ... are passed into the bullet type's init function.