Java Update

IPDynamic is compatible with Java versions 16 through 22. There is no support for lower versions java 8 or 11, but if you need a lower edition, feel free to contact me on Discord as SrCodex.​

Discord Webhook Delete the config.yml or add the option WebhookURL: "" below time-zone.

In the config.yml, you can set up a URL that will notify you when an IP is added to the blacklist (Only op1). Additionally, if a player with a blacklisted IP tries to join the server, the following information will be sent to the appropriate channel:

Username:

IP:

Alts:

Reason for blacklist:

Notification that they attempted to join the server.

For now, only one Discord webhook is supported to notify about attempts to connect with banned IPs, showing the account being used and any alts associated with that IP.

####################################
#    Dynamic IP created by SrCodex
#        Discord Tag SrCodex
#
#####################################


lang: "en" # ru (russian) | cn (chinese) | es (spanish) | en (english) | kr (korea)
time-zone: "America/Los_Angeles" # Default Time Zone WEB: https://timezonedb.com/
WebhookURL: "" # Discord Webhook URL

##########################################################
#          Dynamic IP Penalty Option 2
#         Read this before making changes
# To understand the new Ban OP2 system, you need to read this to get acquainted with what the new feature does. First and foremost, I have fixed an issue that was
# causing massive lag when applying a rank ban with option (OP2), as it was applying nearly 63,000 bans per second, resulting in significant lag.
# Therefore, I have divided the sanctions into 15 parts, with each part applying a ban to 4,392 accounts every 5 minutes. This will make the performance more stable.
# Once the IP range ban for option 2 starts, it will continue unless your server is turned off. So, how long should you wait? Option 2
# will apply a dynamic ban ranging from 0 to 255 on the last two digits, banning nearly 63,000 IPs, and this may take around 3-5 hours to complete.
#
# PERFORMANCE WARNING: The longer you set the ban time, for example, from 5 to 10 minutes, the higher the performance impact, but it will take longer for the ban system
# to apply restrictions to that dynamic IP. However, if you reduce the ban time from 5 minutes to 1 minute, it could cause very high lag and potentially crash the servers.
# If you still experience performance issues with a 5-minute ban, consider increasing the time to better suit your server’s needs.
##########################################################
ban-op2-minutes: 5 # Default 5 minutes

You need to delete the config.yml & Message-RU.yml file to obtain the new content.

Improvements:​

Now, when you request account data, it will display the date, time, and the real IP address used to register on the server for the first time. It will also show the last date of activity on the server.

Each disconnection will display the IP address used at the moment of disconnection, including the date and time.

Time Zone​

We have now added a time zone feature that can be modified in config.yml to set the time zone for capturing specific date and time data for an account when they log in for the first time.

Message-RU.yml​

A Russian player named Reizi updated the message in their native Russian language, so you now need to delete the current file to receive the new content.

IPDynamic Alts, help command visually updated

We have improved the display of the alt accounts and added a blacklisting system that will show up when requesting account data to check if a previous IP is on the blacklist. Additionally, we enhanced the symbols used in messages.

We also updated the help menu to make it more visually appealing

I’ve added an enhancement to retrieve account information, which will now be displayed in a more detailed and well-organized manner.​

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.

We've changed the API we used to get information about a player's IP when verifying their account

We’ve added a new feature to the /ipdynamic alts <player> command. As you know, this command filters all IPs that have been used with that account, whether it's from lending the account to a friend or if someone else tries to log in with that account. Every IP is logged.

Now, we've introduced an additional feature: a section called "Connections." This will show you the IPs that the player has been using to log in. This enhancement will help you identify which IP the player uses most frequently, giving you a 90% certainty of their primary IP address.

Example

127.0.0.1 | Alts: 0 | Connections: 15 | Country: Chile <- Here we see that with this IP, the player logged in 15 times, which obviously indicates that it is their main IP.

127.0.0.2 | Alts: 0 | Connections. 3 | Country: Chile <- Here we see that with this IP, the player logged in 3 times, which could be a friend or someone who tried to access their account.