Plugin Free is back!!!!

For some reason, if the plugin is added to a "proxy" network on a specific server like the Lobby or Auth, when a banned IP enters the server, it sends 7 messages to Discord with the player’s data instead of just 1 message.

This has been fixed; it will now check the player's entry every 10 seconds. This means if a player enters, their data will be sent only once, and after 10 seconds, a new notification can be sent if they try to enter again, preventing duplicate messages.

This issue occurs only if the IPDynamic is added to a "bungee/proxy" network, but just to be safe, the entire problem has been addressed.

Discord Webhook - a notification has been added for when an IP is removed from the blacklist or when a player is added to the whitelist to evade penalties.

For some reason, if the plugin is added to a "proxy" network on a specific server like the Lobby or Auth, when a banned IP enters the server, it sends 7 messages to Discord with the player’s data instead of just 1 message.

This has been fixed; it will now check the player's entry every 10 seconds. This means if a player enters, their data will be sent only once, and after 10 seconds, a new notification can be sent if they try to enter again, preventing duplicate messages.

This issue occurs only if the IPDynamic is added to a "bungee/proxy" network, but just to be safe, the entire problem has been addressed.

Discord Webhook - a notification has been added for when an IP is removed from the blacklist or when a player is added to the whitelist to evade penalties.

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.

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.



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.

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

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.

/ipdynamic op1 <ip> <reason> (Recommended)

Warning: This method is more stable and recommended. You only need to add the player's IP, and a dynamic ban will be applied specifically to that IP. This approach is more effective if the player switches to a new dynamic IP; simply copy their new IP, and you will block all access to the server by applying the ban to the last digit of their IP.

Note: If the player continues to change their IP address after 2 bans, you can reapply their 3rd ban. If they bypass the ban again, you can use the option 2 ban as a last resort. This method is more complex and risky but will block an entire dynamic IP range based on the last 2 digits. I recommend reading about option 2 for more details.

/ipdynamic op2 <ip> <reason> (Not Recommended) (As a last resort)

Warning: This option is a last resort if (op1) still allows some people to bypass bans by not only changing the last digit but also the penultimate digit. For example, with (op1), a ban might cover 127.0.0.* but users can evade it by changing their IP to 127.0.1.1, thus bypassing the (op1) ban. Even if you reapply the restriction to that IP and they bypass it again, the purpose of option 2 is to blacklist the last two digits as a final measure. This blacklists IPs in the range from 0 to 255, completely blocking access to that IP, but be aware that this may affect multiple players in the process.

/ipdynamic op1 <ip> <reason> (Recommended)

Warning: This method is more stable and recommended. You only need to add the player's IP, and a dynamic ban will be applied specifically to that IP. This approach is more effective if the player switches to a new dynamic IP; simply copy their new IP, and you will block all access to the server by applying the ban to the last digit of their IP.

Note: If the player continues to change their IP address after 2 bans, you can reapply their 3rd ban. If they bypass the ban again, you can use the option 2 ban as a last resort. This method is more complex and risky but will block an entire dynamic IP range based on the last 2 digits. I recommend reading about option 2 for more details.

/ipdynamic op2 <ip> <reason> (Not Recommended) (As a last resort)

Warning: This option is a last resort if (op1) still allows some people to bypass bans by not only changing the last digit but also the penultimate digit. For example, with (op1), a ban might cover 127.0.0.* but users can evade it by changing their IP to 127.0.1.1, thus bypassing the (op1) ban. Even if you reapply the restriction to that IP and they bypass it again, the purpose of option 2 is to blacklist the last two digits as a final measure. This blacklists IPs in the range from 0 to 255, completely blocking access to that IP, but be aware that this may affect multiple players in the process.

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.

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.

I have fixed a translation issue across all languages except Russian and improved the visual quality of some features.

GeoIP is working quite well overall, though there are occasional dropouts. It shows all the data, but sometimes it fails to display the country of the IP address of the connecting player. This will be patched in a future update.

IPDynamic has received an update in several languages, including Russian, which was translated by Reizi.

We’ve added %username% to specify the player's name when requesting account data. You can customize the message in the messages file.

This is only valid for the alts section.

Exciting Plugin Update!

We’re thrilled to announce that our plugin now supports multiple languages for a more inclusive and personalized experience. With this update, you can interact with the plugin in the following languages:

• Chinese (中文) (cn)
• Spanish (Español) (es)
• English (English) (en)
• Korean (한국어) (kr)
• Russian (Русский) (ru)

What does this mean for you?

• Multilingual Interface: You can now use the plugin in your preferred language, making the experience much more comfortable and accessible.
• Easy Customization: All languages are organized in editable files within the messages folder. This allows you to customize the messages according to your needs and preferences.

To change the language, simply adjust the settings in the config.yml file or use the plugin's configuration command. It’s that easy!

We are committed to making your experience as smooth as possible and hope these new languages enhance your enjoyment of the plugin. Thank you for your continued support!

Fixed a visual problem with a specific message in English.

I've removed the Spanish language and focused on English. Although it may not be 100% accurate, you can customize the messages from the messages folder in the message-en.yml file.

Fixed something visual from 1.21

The alts system was added to the help command, and the alts command was added to the autotab.

[Update v1.2.7] - Improved Alts Detection and GeoIP

• Enhanced Alts Detection:
• Real-time display of all accounts (alts) associated with both previous and current IPs of a player.
• Provides a complete list of players who have used the same IPs, making it easier to detect alternate accounts.

• GeoIP:
• Added country detection for each registered IP. Each IP will now show the country from which the player connected, providing more information about player locations.