Deprecated
This library is no longer maintained, and BYOND has better built-in solutions these days anyway. So I recommend you don't use it.
 |
FullBan ensures that once you ban someone, they stay out. Banning is permanent, and will not be revoked when the game is rebooted or you stop hosting. Unlike most banning systems, FullBan bans using a total of FOUR methods. It takes more than just changing your key and IP address to fool this library. Starting from version 2, there is also a limited IP-range-banning function.
All this means that FullBan is one of the best banning libraries out there. Better yet, it's free! |
If you find any bugs, please email me a thorough description of the problem. Email address is in my profile.
If you accidentally ban yourself (whoops!), log in with a different key that is not banned but does have admin access to lift the ban.
Alternatively, delete the file "cr_full.ban" and you will be able to log in again, *provided* you're hosting on the same machine that you log in from. Once logged in, use admin commands to remove the ban on your key.
If you're hosting on a shell account (if you don't know what this is, then you're not), delete the file and then run Dream Seeker
in your shell account to log into the game. Once logged in, use admin commands to remove the ban on your key.
A list of banned keys can be accessed using the variable crban_keylist. This variable is simply a /list containing the key names (in ckey()ed form) of everyone who is banned. (Actually, it's also an associative list; the associated value is the IP address that was last attached to that key.)
Changes in version 5: (15th August 2005)
- Fixed (hopefully) a bug where unbanning would fail under certain conditions. (Xooxer)
- Added an option, for advanced users, to use world/IsBanned(). (Deadron)
- In order to avoid catching innocent people in the bans, single-IP bans no longer re-apply all banning methods.
Changes in version 4: (29th December 2004)
- Added a new method of banning, to bring the total to four.
Changes in version 3: (13th August 2004)
- IP range banning has been made more intelligent; it now attempts to fix up incorrect IP ranges, and players falling within that IP range will be banned and booted as soon as the IP range ban is applied. (Previously, they had to log out and in again for the ban to take effect.)
- The included demo has been improved slightly.
I want to write games, not worry about getting computer_ids, and linked keys, and addresses, and "keyban" and "ipban" files all working together. I don't host my games, so I don't have first hand experience with the problem. I'd much rather include a library from an expert than stumble around trying to write my own solution.
Please bring back this library.