AntiBranchMining

Removes all ores that can only be found by branch-mining while retaining all ores that can be found by caving and exploring

File Details

AntiBranchMining v0.4

  • R
  • Jun 26, 2013
  • 26.53 KB
  • 2.2K
  • 1.7.4+2

File Name

AntiBranchMining-0.4.jar

Supported Versions

  • 1.7.4
  • 1.6.4
  • 1.5.2
  • Automatically schedules checking of chunks after a server restart that had been queued but not completed beforehand
  • Automatically schedules rechecking for chunks that have not yet been populated with ores
  • Ore stats are maintained between server restarts and are stored in the completed.log file for the world
  • Full logs of all chunks checked for ores are stored in the completed.log file for the world
  • Removed the debugstats property in the config file as it is no longer needed
  • It is now possible to force chunks to be checked manually by adding their chunk coordinates to the queued.log file for the world before starting the server
  • It is also possible to force rechecking of chunks by manually removing their chunk coordinates from the completed.log file for the world before starting the server
  • If your server crashes during world generation, any changes made by AntiBranchMining to remove ores in the moments before a crash may not have been saved to the world files. You can force rechecking of those chunks by removing those entries from the completed.log file in plugins/AntiBranchMining/[world], and restart the server. It will detect them as queued chunks not yet checked and schedule them for checking.
  • Force rechecking large areas of the world at once can cause lag for the duration of the rechecking
  • Force rechecking areas that have had all of their ores removed already can spam your console and server logs with warnings about not finding any ores
  • The larger the world, the larger the queued.log and completed.log files will get