Bug: Loot tables are read as Gameplay Loot not Chest Loot (or Entity Loot) by loot table viewers
Qwerty97475 opened this issue ยท 0 comments
What Feature Types Apply to This Bug?
Gui
Other Type
No response
What Type of Bug Is This?
Unexpected Behavior
Mod Loader
NeoForge
Mod Loader Version
21.1.209
The Aether Version
1.5.10
Is This Bug a Conflict With Another Mod?
Potentially Advanced Loot Info (ALI) v1.3.7
Client Log
No response
Crash Report (if applicable)
No response
Steps to Reproduce
Load up game with Aether and ALI (and EMI)
Check "Gameplay Loot" tab, compare this to "Chest Loot" and "Entity Loot"
For some reason, most Aether loot tables display as Gameplay Loot rather than the correct type - loot chests, mob loot tables, etc are all grouped under Gameplay loot
What You Expect To Happen
All Aether loot tables should be grouped under the correct heading - gameplay loot is for stuff like Cat morning gifts and Slimeball sneezing Pandas and stuff
What Actually Happened
Explained above
Additional Details
Screenshot of Chest Loot - for some reason Ruined Portal loot tables are Chest Loot not Gameplay Loot (which is a good thing, but inconsistent)
Screenshot of an Aether chest loot table being grouped under the gameplay loot table
Another screenshot
I do have DEEP AETHER v1.1.4 installed as well, which has the same problem
This may be a problem with how the Aether implements loot tables, or a problem with ALI, but I assume it's the Aether's fault as most other mods work normally.
Please Read and Confirm The Following
- I have confirmed this bug can be replicated without the use of Optifine.
- I have confirmed this bug is on the most recently supported version of Minecraft.
- I have confirmed the details provided in this report are concise as possible and does not contain vague information (ie. Versions are properly recorded, answers to questions are clear).
- I have confirmed this bug is unique and has not been reported already.
- If playing on a modpack, I have reported this bug to their issue tracker already.
- I have confirmed that I'm reporting a bug in The Aether I, not The Aether II.