- Added basic redstone activity tracking command as /mfm redstone which is disabled by default. When enabled we will keep track of last 60 seconds of redstone activity and record top 10 most active chunks. Keep in mind that this only records most active chunks and not exact locations of every single redstone trigger for efficiency sake, so teleportation will only be to specific chunks center point at 100 altitude and you will need to do more in dept manual check of actual redstone contraptions causing all those ticks.
- Fix for an issue with hoppers command usage in some cases.
- Some small optimizations relating to hopper checks and their transfer rate updates
- Added option to show all entities in list command with /mfm list -all which will include chunks with entities like dropped items or item frames
- Special exception to existing MUSHROOM_COW records which no longer gets recognized properly or could cause issues with correct MOOSHROOM entity type setting
- Added option to toggle hopper handling on/off with in-game command, so /mfm hoppers on will turn it on, which can allow you to have more "on demand" feature toggle if you need to nerf down hoppers or allow them to run at full speeds
- Added some tab completes for commands for more convenient usage
- Fix for vehicle placement not being accounted for when it hits defined limit, now it should properly block placement of vehicles if those are over the limit.
- Added new command as /mfm limits which will output basic information about surrounding chunks. This will provide information about mob type limitations or group limitations based on what you have setup for auto cleanup. By default it will only provide names of entities and groups with some colors to indicate that its under limit (green), at the limit (white) and over the limit (red) without indicating exact numbers. This is mainly to prevent usage of this command to be used as scanning tool, still provides basic information about entities in area which are under limits. For more detailed information you will need to have mfm.command.limits.full permission node, which will provide amount of entities detected in that area and max allowed amount
- Internal update for permission handling mechanics
- Internal update for message handling mechanics
- Small code cleanup
- Small fix for item frame count handling when it comes to invisible ones, usually originating from plugins like ItemsAdder which uses one as custom items base. Now it properly excludes invisible frames from general count