AntiGuest
AntiGuest
Description
AntiGuest prevents players from doing specific things like building and fighting, which can be used to grief.
Every prevention has its own configurable message which will be printed to the player. This message supports color codes (&0, &1, ..., &e, &f, &k)
How does this work?
AntiGuest uses permissions to determine whether a player is allowed to do a specific action. So you should (not necessarily needed, but recommended) install a permission manager like bPermissions or GroupManager along with AntiGuest. Usually you only want to prevent your guests from doing things like breaking and placing blocks (griefing), so you should not give your guests' group the permission to do so. However your accepted players should by able to do these actions. That can be achieved by adding the permission "antiguest.preventions.*" or a action specific permission to the player or his group.
As you might see, this system allows more than just "guests can nothing, members everything". You could for example stagger the permissions like "guests can nothing but chat; trails can chat, place and break blocks; members can everything" and even more complex setups, it's completely up to you.
Watch out! Tips for common mistakes
- All preventions are disabled by default since version 3.0 (3.2 changes that, see the table below)
- All preventions have their own configuration file since 3.1, since 3.2 the old configurations will be converted
- The permissions are all lowercase, check that before you report AntiGuest not working
Preventions
Name | Prevents from ... | On by default | Filterable | Punishable | Loggable |
---|---|---|---|---|---|
ad | posting server addresses (also enables link, see below) | yes | no | yes | yes |
afk | idling players by kicking them after a configured time | no | no | no | yes |
anvil | using anvils | no | no | yes | yes |
beacon | opening beacon inventories | yes | no | yes | yes |
bed | sleeping | no | no | yes | yes |
bow | shooting bows | yes | no | yes | yes |
breakblock | breaking blocks | yes | yes | yes | yes |
brew | brewing | no | no | yes | yes |
button | pushing buttons | no | no | yes | yes |
cake | eating cakes | no | no | yes | yes |
caps | writing all-caps messages | no | no | yes | yes |
changesign | changing signs | yes | no | yes | yes |
chat | chatting | no | no | yes | yes |
chest | accessing chests | yes | no | yes | yes |
command | using specific commands | no | yes | yes | yes |
damage | getting damaged | no | yes | no | no |
dispenser | accessing dispensers | yes | no | yes | yes |
door | opening or closing doors (including fence gates) | yes | yes | yes | yes |
dropper | opening dropper inventories | yes | no | yes | yes |
drop | dropping specific items | no | yes | yes | yes |
enchant | accessing enchantment tables | no | no | yes | yes |
fight | damaging other players | yes | no | yes | yes |
fish | fishing | no | no | yes | yes |
furnace | accessing furnaces | no | no | yes | yes |
guestlimit | getting too many guests | no | no | no | no |
hopper | opening hopper inventories | yes | no | yes | yes |
horse | interacting with horses/mules/donkeys | no | no | yes | yes |
hotbar | changing the selected hotbar slot | no | no | yes | yes |
hunger | starvation | yes | no | no | no |
itemframe | changing item frames | yes | no | yes | yes |
item | using specific items | no | yes | yes | yes |
jukebox | using jukeboxes | no | no | yes | yes |
lavabucket | using lava buckets | yes | no | yes | yes |
lead | using a leash | no | no | yes | yes |
lever | using levers | no | no | yes | yes |
link | posting clickable links | yes | no | yes | yes |
milking | milking cows | no | no | yes | yes |
monster | getting targeted by monsters | yes | yes | yes | no |
move | moving too far | yes | no | yes | no |
noteblock | using note blocks | no | no | yes | yes |
pickup | picking up specific items | no | yes | no | no |
placeblock | placing blocks | yes | yes | yes | yes |
pressureplate | triggering pressure plates | no | no | yes | yes |
repeater | changing the repeater delays | no | no | yes | yes |
shear | shearing animals | no | no | yes | yes |
sneak | sneaking (hiding the name above his head) | no | no | yes | yes |
spam | spam | yes | no | yes | yes |
spawnegg | using spawn eggs | no | yes | yes | yes |
swear | swearing | yes | no | yes | yes |
tame | taming animals | no | no | yes | yes |
trading | trading with villagers | no | no | yes | yes |
trample | trampling crops | no | no | yes | yes |
tripwire | triggering trip wires | yes | no | yes | yes |
vehicle | using vehicles (entering, placing, destroying, pushing) | no | no | yes | yes |
waterbucket | using water buckets | yes | no | yes | yes |
workbench | accessing workbenches | no | no | yes | yes |
Filtering
How does filtering work?
Filtered prevention allow you to filter the action which will be prevented.
For example the command preventions which can either prevent the usage of all commands or just a specific set of commands based on a whitelist or blacklist
Filter configuration
- mode:
- none: everything will be prevented (aliases: -1, nolist, all)
- whitelist: the listed entries are NOT prevented (aliases: 0, white)
- blacklist: only the listed entries will be prevented (aliases: 1, black)
- list:
- the list of entries. this might be commands, item names or anything else depending on what the prevention does
- this list will be ignored if the mode is set to none
Punishments
Since version 3.3, AntiGuest allows to automatically punish players. These punishments are configurable per prevention.
You can specify multiple punishments per violation, you can look at the default punishment values in the configs
Punishment | Description | Configuration |
---|---|---|
ban | Bans the player | reason: the ban reason |
burn | Sets the player on fire | duration: the burn duration in seconds |
dropitem | Drops the held item | pickupDelay: the pickup delay in seconds |
explosion | Creates a fake explosion and damages | damage: the damage to deal |
kick | Kicks the player | reason: the kick reason |
kill | Kills the player | none |
lightning | Strikes a fake lightning on the player | damage: the damage to deal |
message | Makes the player send an awkward message | message: the message to send |
potion | Poisons the player | duration: effect duration, effect: type |
rocket | Shoots the player in the air | height: the number of blocks |
slap | Slaps the player | damage: the damage to deal |
starvation | Lets the player starve | none |
No configuration is specified as {}
Commands
General syntax: /antiguest <command> or /ag <command>
Command | Description |
---|---|
help | prints a help text |
can [player] <preventionname> | checks whether the player (or another player) passes a prevention |
list [-a] | lists the active or all registered preventions |
reload [prevention] | reloads the plugin |
setmessage <prevention> <message> | sets the message of a prevention |
language [language] | shows or sets the language |
badword <word> | adds a bad word to the swear prevention |
disable <prevention|*> [-t] | disables a specific prevention or all at once |
enable <prevention|*> [-t] | enables a specific prevention or all at once |
reset | resets all configurations |
Installation
AntiGuest 3 needs at least Bukkit 1.1-R5!
Steps
- Just put the AntiGuest Jar-File into your plugins folder
- If you're upgrading from an older version you might remove your config to get a fresh one
- restart/reload your server
- The configuration files will be generated/updated as soon as the plugin gets enabled
Permissions
Permission node | Description | Default |
---|---|---|
antiguest,violation-notification | The player will receive violation notifications | not assigned |
antiguest.* | Allows the player to do everything | operators |
antiguest.commands.* | Allows the player to run all commands | operators |
antiguest.commands.<command> | Allows the player to run the specific command | operators |
antiguest.preventions.* | Allows the player to pass all preventions | operators |
antiguest.preventions.<prevention> | Allows the player to pass the specific prevention | operators |
Base configuration
Entry | Default value | Description |
---|---|---|
debug | false | Enables or disables debug output |
language | system value | Sets the language of all texts |
punishments | true | Globally disables or enables punishing |
log-violations | false | Globally enables violation logging |
prevent-npc | false | Enables the preventions for NPCs |
Developer Notice
Plugin developed by Quick_Wango - Cube Island
- You want new features?
- You want the plugin to be always up to date?
- You want good support?
I'm doing this for literally nothing in my free time, so keep me interested in my plugins and help pay my bills by simply donating a few bucks.
Thanks in advance!
Talk to the developers (#cubeisland-dev on EsperNet)
Updated for 1.6.2:
http://dev.bukkit.org/bukkit-plugins/antiguest/files/21-anti-guest-v3-9-0-1-6-2/
Version 3.9.0
@skookiesprite
Sounds like a permission issue, so I'd check bperms first.
I'm not sure if the issues i';m experiencing with this and 1.6.2 are the plugin's fault or bperms, but is anyone else having problems with users suddenly not being able to do things? Been an antiguest user for like 8 months now; love it. Thanks for the great plugin. 1.6.2 version uneccessary or is it being worked on? Thanks so much!
Are those the only permission nodes? How would I restrict single items/blocks?
is it possible to add a global kick message?
"kick by antiguest because blockbrake"
Any progress on the separate yml files for animals, mobs + pvp (fight.yml) and adding filter to animals (need those wolves and ocelots to remain killable) ?
@dulceice
http://nexus.cubeisland.de
^ Search my nexus for "antiguest" and you'll find antiguest 3.9.0-SNAPSHOT which has all the new stuff and some other minor changes.
Any word on protection for hoppers/other new things added in 1.5?
@pilvimaa
Thank you for you donation. You may also join my IRC channel on esper.net: #cubeisland-dev (webchat is linked at the end of the description above) to discuss your requests in more detail.
edit: the actual channel is #cubeengine
@QuickWango
Donated 5 euros. Keep up the good work
@pilvimaa
I'm not sure how much you already looked at AntiGuest, because some of these features are already implemented (at least in the latest dev build: http://nexus.cubeisland.de search antiguest). And for the rest: I'm currently in the break between my final exams and I'm also taking a break from programming (mostly). However there is a donate button which might be able to motivate me.
to your question: yes, arrows (all projectiles) know their sender (this is already used in a prevention)
Hello QuickWango.
I need you to add these features as quickly as your nimble fingers can code (listed in order of importance):
1. Prevent damaging animals (with filters) 2. Prevent damaging npcs 3. Punishments: Run a custom command as a punishment! (As a console command) 4. Prevent damaging others players (filters/support for permissions so that you can allow/prevent some players from damaging other players who have the permission node.) 5. Prevent damaging mobs (with filters)
And is it technically possible to also prevent damage from the bows (and not just disable shootings bows altogether)? Because that would be awesome.
Thank you. If you can add these features AntiGuest will be a very nice replacement for ModifyWorld which has fallen out of repair.
@brohoof
fixed and will be released with version 3.9.0 next week
chest protection doesn't protect trapped chests (block #146).
And one more for those of you that use Citizens or another NPC plugin on their server:
http://dev.bukkit.org/server-mods/antiguest/files/20-anti-guest-v3-8-2-1-5-1-r0-2/
Version 3.8.2
Thanks for all updates! :D
And just another update: http://dev.bukkit.org/server-mods/antiguest/files/19-anti-guest-v3-8-1-1-5-1-r0-2/
Version 3.8.1
New version awaits approval: http://dev.bukkit.org/server-mods/antiguest/files/18-anti-guest-v3-8-0-1-5-1-r0-2/
Version 3.8.0
3.8 coming in the next few days (probably) with 2 new preventions: link prevention (prevents posting clickable links) and ad prevention (prevents posting server addresses).
If you have any issues with AntiGuest right now, make a report or contact me on IRC
Placement is already possible, ignition is not that simple. As soon as the player uses Redstone to ignite the tnt there is no way I can track that back to a player. It would be better to prevent the player from getting certain blocks or prevent the interaction with the world.