Module-Reference

# Module Reference


> **Documentation baseline:** VoxelCore `main` at `452b569` · 14 September 2026.  
> **Repository:** [https://github.com/VoxelHorizons/VoxelCore](https://github.com/VoxelHorizons/VoxelCore)


The root Maven reactor currently contains nine modules.

| Module | Responsibility |
|---|---|
| `voxelcore-common` | Content IDs, authoring models, parsing/compilation, runtime snapshots, render allocations, common item/platform contracts. |
| `voxelcore-pack` | Deterministic Java resource-pack compilation and exact pack-target profiles. |
| `voxelcore-plugin` | Bukkit plugin lifecycle, configuration migration, command framework, `PackManager`, platform discovery. |
| `voxelcore-v1_12` | 1.12.x–1.13.x legacy family, legacy NBT identity and distribution packaging. |
| `voxelcore-v1_14` | 1.14–1.19.3 family, PDC/numeric CMD path and distribution packaging. |
| `voxelcore-v1_19_4` | 1.19.4–1.20.4 family boundary. |
| `voxelcore-v1_20_5` | 1.20.5–1.21.3 data-component-era family. |
| `voxelcore-v1_21_4` | Exact 1.21.4 structured CMD/item-model implementation. |
| `voxelcore-v26_2` | Exact 26.2 Paper implementation compiled with Java 25. |

## `voxelcore-common` package map

- `content.ContentID` — canonical namespaced identity.
- `content.load.*` — deterministic pack/file loading and strict YAML parsing.
- `content.compile.*` — inheritance resolution and compilation.
- `content.item.*` — raw and compiled item models.
- `content.render.*` — persistent render allocation registry/store and structured indices.
- `content.runtime.*` — snapshot publication and safe reload result/runtime.
- `item.ItemManager` — definition lookup, item creation and identity lookup through the active snapshot.
- `platform.*` — version, capabilities, provider/adapter contracts.
- `platform.item.*` — item platform adapter and metadata flag support.

## `voxelcore-plugin`

The plugin module wires the pieces together in `org.voxelhorizons.VoxelCore`. Startup performs config migration, platform selection, content load, allocation reconciliation, platform validation, snapshot publication, manager construction and command registration before emitting `VOXELCORE_READY`.

## Version module service discovery

Each version module registers an `org.voxelhorizons.platform.PlatformProvider` in `META-INF/services`. This keeps version-specific classes isolated from common code and lets `VersionAdapterFactory` select a matching provider at runtime.