Managing disruptive players can be a challenge, especially when they circumvent bans by simply changing a digit in their IP address. In some cases, this may even tempt server owners to consider blocking entire countries, which often comes at the cost of losing legitimate players.

IPDynamic offers a smarter solution by providing dynamic IP filtering, allowing server administrators to block problematic players more effectively without impacting innocent users.

• Dynamic IP Blocking:
  • Block IP addresses dynamically by targeting specific ranges, such as 127.0.0.* or 127.0.*.*, to prevent players from bypassing bans with minor IP changes.
• Whitelist System:
  • If a legitimate player has a similar IP to a banned user, IPDynamic allows access based on their username through a whitelist. Players can request to be added to the whitelist, and server owners can verify their identity to ensure they aren’t the same malicious user.

/ipdynamic list
View the list of players currently on the whitelist.

/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.

Example : /ipdynamic op1 192.168.1.1 Hacks
Ban: 192.168.1.* Hacks

/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.

Example: /ipdynamic op2 192.168.1.1 Hacks
Ban: 192.168.*.* Hacks

/ipdynamic reload
Reload the configuration and messages without restarting the server.

/ipdynamic reset <op1/op2> <ip>
Remove an IP from the blacklist that was banned with either op1 or op2.

/ipdynamic add <username>
Add a player to the whitelist, allowing them to log in even if their IP is similar to a banned one.

/ipdynamic del <username>
Remove a player from the whitelist.

/ipdynamic alts <username>
Verify all the ips that the player has logged in to, including accounts, ips, countries where he/she connects.

NEW We've added a new system for admin logs and alt detection. You'll now see a new option called "Connections," which will show the IP address that a player connects from most frequently.


The alt detection system tracks all account logins. If someone tries to access your account from another country, that IP address will also appear in your account. For example:

Searching data for the account SrNemesis:
127.0.0.1 | Alts: 0 | Connections: 15 | Country: Chile <- Suppose this is my main IP address; we know this because of the connections associated with it. I've played more than 15 times using the same IP, so it’s clearly the main address I use.

127.0.0.2 | Alts: 0 | Connections: 3 | Country: United States <- This is an IP address from someone who tried to access my account, or it could have been a friend. Since the connection shows only 1 instance, we can now determine that it’s not my main account.