Bukkit

I've been coding for a while... but I'm working so it takes a lot of time... should be done really soon. -BadCall

A plugin that allows your staff to easily perform their duties, it records the offences in the value you provide, and performs an action based on the number of times that value has been broken/performed. For example, if you do /em xDrapor 1, where 1 is the value for griefs, it will perform an action based on the number of times that action "griefing" has been performed by xDrapor. If xDrapor griefed 10 times, and the value set in the config is IP-Ban for 10 times, then xDrapor will be IP-Banned.

Features:

• Allows functions to be performed based on a value and a database.
• Update notifications
• Own jailing, muting,kicking and banning system to prevent conflicts, jails can be set into EssentialsJail locations, our jail system basically spawns a jailed person to an area
• Configurable option to hook into essentials/commandbook.
• Functions can be created by the user, so "Grief" with a list of levels with values that are defined by this plugin to perform, for example: level_1: mute, with optional time values for certain values, like mute, and ban.
• Stores data, warn level in each region to each player into a database

Note: These are just initial planned features.

Developers currently working on this project:

• xDrapor
• BadCall

Planned command layout

• /em (value) (player) So, /em xDrapor grief would check the config for the player defined value "grief". Check the times the player has been warned in the grief field. If the player has been warned two times, and this is the third, then the action of: level_3, so if level_3 is level_3: ban then the player will be banned. If it was level_3: ban 10 min then the player will be banned for 10 minutes.
• em check (player

Planned values

• mute (with optional time and unit)
• kick
• ban (with optional time and unit)
• kill
• jail (optional time and unit, will be unjailed once the player moves and the time has passed)
• msg (message)

Planned config layout

The config will allow a max of 5 levels that have to be added.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13

#Planned Config layout (subject to change)
"Grief":
     level_1:
              - msg Don't grief, this is your first warning
              - jail 100 min
     level_2:
              - mute 120 min
     level_3:
              - ban 20 min
     level_4:
              - ban 50 min
     level_5:
              - ban

Further examples and information

(Rules used and values) This will show you, in a text form, what can be in the config.

1- No swearing (Warn, Mute(5m), Mute(15m), Jail(30m), Ban)

2- Have decent grammar. (Warn, Warn, Mute(5m), Mute(10m), Jail(15m), Ban)

3- Have an appropriate name. (Instant ban)

4- No racism, even if it's a joke. (Warn, mute(30m), mute(1h), jail(3h), ban)

5- No spamming. (Warn, mute(30m), mute(1h), jail(3h), ban)

6- Respect of everyone. (Warn, mute(30m), mute(1h), jail(3h), ban))

So warning for BadCall at value <1> added into his "offence files".

In chat, it would be something like this:

[EasyModeration] BadCall as been warned for breaking rules #1 1 times.

Others example, using the same rules code:

/easymoderation xDrapor 3

[EasyModeration] xDrapor as been banned for breaking rules (value) 1 times.

Also

/easym xlxgnrxlx 4

[EasyModeration] xlxgnrxlx as been muted 1 hour for breaking rules #4 3 times.

More commands:

/em (And all other abr for it) check <name>

It would be like:

==[<name>('s) rules broken]

Example: /em check BadCall

==[BadCall('s) rules broken]

1: 3 times (Next is Jail(30m). 6: 1 times (Next is Mute(30m).

This could be modified by commands like

/em rb ( rules broken) <name> remove <rules value> <warning value>

Example:

/em rb BadCall remove 1 1

So I would be like this after the command:

==[BadCall('s) rules broken]

1: 2 times (Next is Jail(30m). 6: 1 times (Next is Mute(30m).

(Look above to compare. Too lazy ? I just removed 1 warning from the rules "1").