Removed mob_light_table, simplied loop, changed return values and
fixed dimension priority error in loop. Slimes also don't have a
hardcoded exception for their light levels anymore, and instead
are apart of spawn specific.
There is now a call to mcl_mobs:mob_light_lvl that returns a table for the name of the mob that you pass to it that contains
the light levels for that mob.
The non_spawn_dictionary will cover all mobs that don't spawn naturally, and holds the the minimum and maximum light values for each of them.
A function has also been created that will go through both the spawn_dictionary and the non_spawn_dictionary and determine which one
a mob exists in, with the execption of slimes which cannot spawn from a custom spawner at the moment.
Mobs who don't have light levels for the world that you are currently trying to set your custom spawner in will default to their overworld values
This addresses the edge case where fire is set to the top of a non-water
block that represents water (such as kelp).
Note this is forbidding theoretically legitimate setups for fire over
water where fire is set to the side of a block diagonally from the
water.
Fire is still permitted next to water (so it can be set to the face of a
block diagonally from a water column).
This commit adds a couple of lines to the `mcl_mapgen_core:fix_foliage_palette_indexes"` LBM, which ensures that player leaves which were placed before this update get converted into the new player leaves.
I would have included mangrove leaves, but decided against it because of an issue where the `param2` of mangrove leaves was accidentally set to 1 (in the schematics?). This meant that if I included mangrove leaves, the LBM would have converted the natural leaves as well.
This would have made it very tedious to clean up the leaves after chopping down a mangrove tree, since these would not rot by themselves.
