lethargiclion / informaban Goto Github PK

• Example config file should auto-generate with sensible defaults

Initial options should include:

• Language selection
• Selection of preferred storage backend (currently only sqlite)
• Default ban length (if no length is specified with /ban)
• Maximum tempban length for those without informaban.permaban permission
• Kick message format
• Tempban message format
• Permaban message format
• Verbosity of console logging
• Server name (for insertion into messages)
• Whether or not to allow kicks/bans with no reason
• Default reason to use if reason isn't given

• Implement /kick and /ban commands that kick a user with an appropriately formatted message
• Implement sqlite3 database backend
• Implement storage of kicks and bans in the database via abstract database layer
• Check for bans at logon and disconnect user with an appropriate message if any apply

• MySQL backend
• Flatfile YAML backend

• Ensure that all messages are internationalized

• Add support for importing CommandBook's ban log
• Add support for importing Essentials ban lists
• Add support for importing banned-players.txt (vanilla ban system)

Some servers allow players to be jailed. This information should be part of their record as well as kick and ban information.

Whether the plugin should provide jailing functionality, or allow use of existing jail plugins but record their use is something to be considered.

Certain major griefing clients are able to load lists of compromised accounts from a text file in username:password format. Many of these account lists can be easily found via a Google search.

InformaBan should have the ability to load these lists, in username:password format, and deny login to these accounts with a message explaining that the account is compromised.

Optionally, this feature could attempt a Minecraft login with the compromised credentials, and allow login if they are no longer valid (e.g. password has been changed).

Reviewing kick and ban history is good but being able to add comments as well would be helpful. This could allow for an admin to add info where a player is warned but not punished, or has been given something (grief rollback for example) where their rights are limited.

It would be a good option to allow editing/removal of comments. Perhaps even other erroneous database entries.

• Allow IP-banning of an online player by name via /ipban
• Allow banning of an arbitrary IP via /ipban (and kick any matching players when ban is placed)
• Check player IP for matching bans upon login, and disconnect player with appropriate message
• When looking up a player's history, display any past IP bans that match player's current IP
• Upon regular kick or ban, store the current IP of the player being kicked/banned, for future reference
• When looking up a player's history, display any regular kicks and bans (including records for other players) where the IP at the time of kick/ban matches player's current IP, which allows ban evasion to be detected

• Implement basic retrieval of the requested data
• Present data to the user in a clear, informative manner