RangeBans - Ban IP Ranges;
This plugin was mainly made for offline-mode servers, where you cant really deal with dynamic IPs users.
- Ban IP Ranges, hostnames
- Except nicknames from these bans or use them as whitelist
- Support for 'wildcards' (ex. 192.168.*.*, 90.120.128-192.*)
All you need is just to simply grab .jar file into /plugins folder.
Additionally, u can set some values via config file (generated automatically):
- broadcast-kicks: (true/false) Broadcast a message to operators player with banned IP range tries to join the server
- broadcast-passes: (true/false) Broadcast a message to operators when player passes range ban due to an nickname exception
- ban-msg: Message to show to banned player, supports colorizing
- use-hostnames-as-whitelist: (true/false) Should plugin use hostname bans as whitelist?
Bans and exceptions are stored in .txt files.
How to check somebody's IP range?
For example, for inetnum: 192.168.128.0 - 192.168.192.255,
correct command would be: /rb ban 192.168.128-192.*
or simply /rb ban 192.168.128.0 - 192.168.192.255
- rb.* - full access
- rb.reload - reload the plugin
- rb.ban - ban and unban both IP Ranges and hostnames
- rb.exception - add/remove exceptions
- rb.check - check somebody's IP
- rb.list - list bans/exceptions
- rb.broadcast - receives message when a player is found on bans/exceptions list
- Hostname bans are now optional - no more freezes on playerjoin
- Performance tweaks
- Fixes critical bug with wrong IP parsing
- Feature to ban hostnames (ex. countries, providers - easier)
- Added config option to use hostname bans as whitelist (ex. only whitelisted countries can join)
- Updated to 1.1-R3, still compatible backwards
- General code tweaks
- Date created
- Dec 31, 2011
- Last update
- May 07, 2012
- Development stage
- GNU General Public License version 3 (GPLv3)
- Curse link
- Recent files