-
Notifications
You must be signed in to change notification settings - Fork 11
Home
Documented here are the various data-driven options provided to developers, modpack creators, or other users to help properly display custom loot drops with EMI Loot!
Entity Fixers are .json files that can be used to fix how entities are displayed in the mob drops EMI category. Many entity models are inconsistent in how they are scaled, translated, or rotated, leading to them appearing improper in the recipe viewer. This file allows for providing offsets and other fixes in order to get mobs rendering properly.
(Not yet implemented) There will be a fixing system for blocks that aren't appearing correctly in the recipe-viewer. TBA!
If there are certain drops that aren't handled by a traditional block or mob loot table, these drops can be defined here. They will appear in-game with a condition icon noting that they are directly dropped without using a loot table. Some examples of this:
- Equipment spawned with a mob, like a skeleton's bow.
- Special items that are are hardcoded, like the Wither's nether star.
- Certain mods that handle all of their drops via hardcoding, rather than with tables.
If there are loot tables that for some reason you do not want the parser to parse, you can add an exclusion file as described in the wiki page that causes the parser to skip that file.
This is used by EMI Loot to skip certain fishing loot tables who's only purpose is to gather up several other loot tables. Including them would simply show the same information multiple times in the recipe viewer.
(Not Yet Implemented) A .json "scripting language" designed to allow developers a way to tell EMI Loot how to deserialize their custom loot conditions, functions, or predicates into a visual form EMI Loot can present to the user. TBA!