Reference¶
All · reference · No code
Look-up pages: every class, setting, node, tag, message and command XenoCore adds. Use them with the editor open beside you. For how to do something, start with the recipes; for why a system works the way it does, read the concepts.
Pages marked generated are listed straight from the plugin's source, so they match the version you have. The others are written by hand.
Quick answers¶
| Question | Go to |
|---|---|
| Where is the setting for X? | Folder map › Where is…? |
What kind of asset is GE_… / DA_… / ID_…? |
Asset naming › Quick lookup |
| What does this field on a data asset do? | Data assets |
| What does this Blueprint node do? | Blueprint nodes |
| What is this console command? | Console commands |
| What does XenoCore add to the Tools menu? | One entry: Apply XenoCore Project Settings |
| Can I delete this folder? | Folder map |
Designers¶
| Page | Use it to… |
|---|---|
| Data assets (generated) | Fill in an art, quest, shop, trade table, drop table, party member, weapon type, gem registry or item fragment: every field, its type and default |
| Blueprint nodes (generated) | Find a node: the latent nodes (Show Dialogue, Offer Quest, Open Shop…) and every function-library node by category |
| Curve tables | Rebalance level-driven numbers: stats, kill EXP by enemy level, reward and damage level-gap multipliers, and what reads each row |
| Gameplay tags (generated) | Look up a tag: what sets it, what it means, and whether C++ names it |
| Asset naming | Tell an asset's type from its prefix, and name your own |
| Folder map | Find where something lives, and which folders are sample content you can replace |
Programmers¶
| Page | Use it to… |
|---|---|
| C++ classes (generated) | Every class, struct and enum: base class, editable properties and Blueprint-callable functions |
| Gameplay messages | Listen for changes: every message channel, its payload, who sends it and who listens |
| Console commands (generated) | Test quickly: console variables, commands and cheats, and which ones actually reach the console |
| Editor tools | Apply XenoCore's project settings, and automate editor work with the editor-only function libraries |
| Compatibility | Check engine version, platforms, dependencies and the upgrade position |
Descriptions on generated pages are short on purpose
Each entry shows only the first plain paragraph of its source comment. Where nothing suitable remains, the page says No description. The concept page for that system explains it properly.
For programmers: regenerating the generated pages
The generated pages are produced by Docs/Manual/tools/gen_reference.py (Python 3 only) from
the plugin's C++ headers, in the repository the manual is built from. If you change XenoCore's
C++ in your own copy, the published pages no longer describe your changes; the headers are the
source of truth.