- Changes internal logic on how enum test hordes are handled for the dev environment
- Reported to multiloader template
- Decreases odds of entities spawning in walls
- Utilizes vanilla game techniques to determine if mob spawns are valid, which may increase reliability of hordes (decreasing how much they despawn due to missing spawn points)
- Small optimizations
- Updates to use the new dependency format for Neoforged
- More gracefully handles the error when a JSON horde has an entity that isn't a pathfindingmob (Kills the horde and throws an error in the logs, instead of crashing)
- Mobs in hordes will now spawn as expected. (Skeletons have their bows, vindicators have their axes, etc.)
- Json Hordes can now specify how many retries for finding spawn points they want to do.
- Refactored how some of the horde types are handled
- Fixed a crash that can happen when a spawn was invalid.
- Json handling is supported for custom hordes! You can now have you own (basic) horde without needing to make your own mod.
- For information on how to make your own hordes, see the github page.
1.20.1 port
Changes from 0.4:
- Fixes the EntityEnumHorde not detecting horde members
- Refactored names from CartoonishHorde to VillainousHordeManager
Changes from 0.3:
- Port to 1.19.4
- Splits Hordes into two types. EntityTypeHorde, which is the equivalent to 0.3's horde class, and EntityEnumHorde.
- EntityEnumHorde is meant to make a system like ColdSnapHordes better supported and less janky, where Cold Snap Horde has to rewrite large portions of the code base for custom spawn rules. Using the enums, the consuming mod is expected to provide their own spawn method and is given the method to do so in.
- EnumHordeData can support any enum that extends RuleEnumInterface.