IPDynamic

It is recommended to delete the config.yml to set up the new configuration.

• Changes and Improvements ​ We have improved the optimization of using op2. Now, after applying a ban, there will be a pause during which mass banning will stop for a period of time while the IPs being blacklisted are processed. This can be customized in the config.yml; I recommend setting it to 5 minutes or more for better performance.

• If the bans exceed 7000 IPs per second, there will be a random interruption in the banning process to stabilize and process the sanctions.

• Now, op1 can ban a dynamic IP from 0 to 255 in 2-3 seconds without crashing the server.

• Additionally, both systems operate on separate threads to prevent saturation of the main thread when applying mass bans, especially when using op2.