Content Packs

Content packs and file layout

How VoxelCore discovers pack files, reads manifests and uses namespaced assets.

Documentation for VoxelCore v1.0.0. Home · Installation · Compatibility

Runtime directory

plugins/VoxelCore/
├── config.yml
├── render-allocations.yml
├── content/
│   └── <pack>/
│       ├── pack.yml
│       ├── content/
│       │   └── **/*.yml
│       └── assets/
│           └── <namespace>/
│               ├── models/
│               ├── textures/
│               ├── font/
│               └── sounds/
└── build/
    └── resource-packs/

content/ may be nested however you like. File and folder names do not define a ContentID; the key beneath items: does.

Pack manifest

schema: 1
namespace: mypack
dependencies:
  - core
  - shared

Supported keys are schema, namespace, and optional dependencies.

A cross-pack inheritance or model reference is accepted only when the referenced namespace is declared as a dependency. A pack may always reference its own namespace and Minecraft resources where appropriate.

Assets

Authored model reference:

render:
  model: mypack:item/ruby

maps to:

plugins/VoxelCore/content/mypack/assets/mypack/models/item/ruby.json

A model texture such as mypack:item/ruby maps to:

plugins/VoxelCore/content/mypack/assets/mypack/textures/item/ruby.png

Generated minecraft override/item-model glue is compiler-owned and is written only to build output.