Features of the MinetickMod - Poweruser/MinetickMod GitHub Wiki

just notes for now, will be properly written soon ...

  • Parallel processing of Entities and TileEnities of different worlds
  • Offloaded packet- creation, orebfuscation and compression to seperate threadpools which work independently of the main thread
  • Offloaded path searches for all mobs
  • Queued, limited and parallel chunk generation in different worlds (Generating in normal worlds is limited to 1 chunk every 2nd tick. In flat land worlds every tick a chunk can be generated)
  • Limited main thread execution: When the main thread needs longer than 45ms (which is nearly the limit it can reach to yet maintain 20 tps. 1s / 20 ticks = 50ms per tick), then it skips pending ticking of entities and generating of chunks, to try to stay within the 50ms boundary.
  • PreLoginEvents are working on offline-servers as well
  • stretched out autosaving of the worlds. There's a litte delay between each save, to lower the lag spike, created by saving multiple worlds at once. And the server does not go to sleep anymore while waiting for the files to be written to disk
  • the connection information in the player list (when pressing TAB) is activated again. Every 3s one player information is broadcasted
  • reduced lag from zombies with a workaround (reduction of search range and skipping of some searches after a failed one)
  • some optimizations around saving of structure data:
    • reduced lag from saving large nbt-based structure files like mineshaft.dat
    • lower memory usage of data about structures
  • built in AntiXRay, which operates by default in "light mode" (e.g. replaces invisible non-stone blocks with stone) to achieve a better packet compression.
  • Generating of new chunks can be turned off in certain worlds
  • customizable spawn rates of ores in the overworld, when using the default generator
  • A custom homebred code profiler, which logs the execution times of various code sections. In the bukkit.yml you'll find some settings for it. The logs will be written to the subdirectory \Profiler within the servers main directory
  • various new commands for operators for debugging and performance tuning
  • more to come ...