Home A - Z
Page Index

Blame

e23584 Dan Alexander 2026-09-14 10:46:55
Add company wiki standards and VoxelCore docs This change establishes the shared company knowledge structure, governance, engineering, security, and incident/change standards. It also adds the VoxelHorizons product tree with a complete VoxelCore documentation set covering architecture, operations, authoring, version support, resource pack compilation, runtime reloads, and testing/release workflows.
1 
# Configuration
2
3
4
> **Documentation baseline:** VoxelCore `main` at `452b569` ยท 14 September 2026.
5
> **Repository:** [https://github.com/VoxelHorizons/VoxelCore](https://github.com/VoxelHorizons/VoxelCore)
6
7
8
The bundled configuration schema is currently version `1`:
9
10
```yaml
11
version: 1 # DO NOT CHANGE
12
game:
13
bedrock_support: false
14
```
15
16
## `version`
17
18
`version` is managed by VoxelCore and should not be manually changed. At startup VoxelCore compares the current file with the bundled schema version.
19
20
When the schema changes or the version is missing, VoxelCore:
21
22
1. creates an incremental backup (`config.yml.old`, then `.old.1`, `.old.2`, ...);
23
2. merges newly introduced defaults;
24
3. preserves existing user values;
25
4. writes the new schema version;
26
5. reloads the configuration.
27
28
This is intentionally non-destructive; current migration logic does not replace an operator's whole configuration merely because a schema version changed.
29
30
## `game.bedrock_support`
31
32
This setting exists as a future integration point. Setting it to `true` **does not currently implement Bedrock support** in the item/content MVP. Bedrock/Geyser presentation and mappings remain roadmap work.