Repository navigation
Data Packs
RPG Gods registers five datapack registries (synced to clients automatically, no custom packets):
| Registry key | Folder in the pack | Entry ID example |
|---|---|---|
deity:deity |
data/<ns>/deity/deity/<name>.json |
my:athena |
deity:altar |
data/<ns>/deity/altar/<name>.json |
my:athena_altar |
deity:offering |
data/<ns>/deity/offering/<deity>/<name>.json |
my:athena/apple |
deity:sacrifice |
data/<ns>/deity/sacrifice/<deity>/<name>.json |
my:athena/zombie |
deity:perk |
data/<ns>/deity/perk/<deity>/<name>.json |
my:athena/blessing |
The registry key has the form <namespace>:<path>; the folder is the key's
namespace and path (deity/offering). The entry ID is the file path relative to
that folder, without .json, prefixed with the pack namespace.
Naming rule: offerings, sacrifices and perks are associated with a deity by their ID path. A perk at
data/my/deity/perk/athena/blessing.jsongets the IDmy:athena/blessing, whose path containsathena/, so it belongs tomy:athena. Keep the folder name equal to the deity path (without namespace).
{
"pack": {
"pack_format": 15,
"description": "My RPG Gods data pack"
}
}Put the pack in saves/<world>/datapacks/<pack name>/ (or a zip), then run
/reload. Datapack registries are synced to connected clients automatically.
- Deity:
nameinside the JSON must equal the entry ID (data/my/deity/deity/athena.json→"name": "my:athena"). Favor lookups use this value, while the registry key uses the file path; a mismatch breaks offerings, altars and perks for that deity. - Altar:
nameis either a deity ID ("my:athena") or a plain custom name ("Guardian of the Gate"). A string that parses as a resource location is treated as a deity. - Offering/sacrifice/perk: the folder under the registry folder must be the
deity path.
my:athena/applebelongs tomy:athena.
- Items:
rpggods:altar(statue),rpggods:scroll(opens the favor GUI),rpggods:brazier(automatic offering block). - Altar item NBT:
/give @s rpggods:altar{altar:"my:athena_altar"}. The mod's creative tab (RPG Gods) generates one altar item for every registered altar. - Custom recipes: use recipe type
rpggods:altar_shapedorrpggods:altar_shapelessand add an"altar"field with the altar ID. See Altars. - Functions: the
favorcommand is available to functions and works with the usualfunctionperk action. Functions run with permission level 4 when triggered by a perk.
- Deity display name: translation key
deity.<namespace>.<path>(e.g.deity.greek.athena), optional subtitle keydeity.<namespace>.<path>.title. - Altar entity texture:
assets/<deity namespace>/textures/altar/<deity path>.png(forgreek:athena:assets/greek/textures/altar/athena.png). - The altar item uses a generated model by default;
rpggods:altarexposes anindexitem property (0..1) if you want to add model overrides for custom altar textures.
- Check
logs/latest.logforCouldn't parse/Failed to parselines — they include the file that failed. -
/favor listshows every registered deity with its enabled/unlocked state. - Use
/reloadafter editing JSON; a world restart is not required. - If the pack does not appear, enable it in Options → Data Packs (world creation/modification screen).