Folder Structure Reference — Galaxy Strike Online Wiki

The tree below shows the folders the game recognizes. Items marked [Required] must exist. Everything else is optional — only include what your pack actually adds.

Organization sub-folders are optional and exist purely for human readability. The game scans all .json files recursively inside each mandatory top-level folder.

<your_pack_id>/
│
├── manifest.json                     [Required] — Pack registration file
│
├── assets/
│   ├── languages/                    [Required if you have display text]
│   │   ├── en_US.json
│   │   ├── fr_FR.json
│   │   └── <any_locale>.json
│   │
│   └── textures/                     [Optional — image files]
│       └── *.png / *.gif
│
└── data/
    ├── dungeons/                     [Required if adding dungeons]
    │   └── *.json
    │
    ├── enemies/
    │   ├── hostiles/                 [Required if adding enemies]
    │   │   └── *.json
    │   └── rooms/                    [Required if adding enemy rooms]
    │       └── *.json
    │
    ├── items/                        [Required if adding items]
    │   └── *.json
    │
    ├── recipes/                      [Required if adding recipes]
    │   └── *.json
    │
    └── skills/                       [Required if adding skills]
        └── *.json

Mandatory Data Folders

Folder	Required when…
`data/dungeons/`	Your pack adds dungeons
`data/enemies/hostiles/`	Your pack adds enemy units
`data/enemies/rooms/`	Your pack adds encounter rooms
`data/items/`	Your pack adds any items
`data/recipes/`	Your pack adds crafting recipes
`data/skills/`	Your pack adds skills

Sub-Folder Rules

Sub-folders inside the mandatory category folders are entirely optional. The game scans all .json files recursively — it does not care about folder names or nesting depth.

All of these are equally valid:

data/enemies/hostiles/my_robot.json                    ✅
data/enemies/hostiles/robots/my_robot.json             ✅
data/enemies/hostiles/chapter_1/zone_2/my_robot.json   ✅

Load Order

When the game starts, it reads datapacks in this order:

Reads manifest.json to register the pack and its categories
Reads all assets/languages/*.json files to load translation keys
Reads all JSON files under data/items/, data/enemies/, data/dungeons/, data/recipes/, and data/skills/
Resolves all cross-references (e.g. recipe inputs pointing to item IDs)

If a cross-reference points to an ID that does not exist, the game logs an error for that entry and skips it.

Texture Path Convention

Texture paths in JSON files are relative to the datapack root, not the JSON file itself:

"texture": "my_pack/assets/textures/materials/ore/uranium.png"

The path starts with your pack ID as the first folder segment. This prevents collisions between packs that both have a file called ore.png.