[BUG] The scarce treasure loot table uses stone_key for iron key entry
Wabbit0101 opened this issue ยท 1 comments
Snipped from treasure/scarce.json:
"name": "scarce_keys",
"rolls": 1,
"entries": [{
"entryName": "iron_key",
"type": "item",
"name": "treasure2:stone_key",
"weight": 15,
"functions": [{
"function": "set_count",
"count": {
"min": 1,
"max": 2
}
}]
},...
I think that's supposed to be a 'treasure2:iron_key'.....and while we're digging around loot tables,
treasure/rare.json also has a weird entry for its skull_sword item (it gives a gold_coin for 'skull_sword' entry...the item just above is a gold coin entry so I'm thinking a cut-n-paste whoopsies there too.
