AutoRegionGuard
AutoRegionGuard
I'm currently working on a lighter version of ARG but I can't tell a release date yet.
Why ARG?
- You do not need any commands to claim chunks
- You do not need to define areas which can be claimed
- You do not need any admins to (un)claim chunks
- You do not need any admins to share your chunks
- You do not need any admins to protect all your stuff.
- You do not need any extra plugins to protect chests and everything else.
- Economy support!
- Fully automated chunk claiming!
Features:
- Automatically claims a chunk by placing an configurable ammount of blocks in it.
- Claimed chunks are protected from other players editing.
- Others can't steal stuff in claimed chunks (Chests, Furnaces, etc).
- Also explosions and fire doesn't affect on claimed chunks.
- Nobody can pull/push blocks with pistons through claimed chunks. Just the chunk owner.
- All protections can be handled by chunk owners
- Inactive players (offline since xx days) will loose chunks + friendlist after a specified time.
- All data is stored in MySQL! No flatfiles which are causing high I/O load.
- Friendlist !
Version notes:
- Currently ARG supports all blocks/items up to Minecraft 1.7.5 !
- This plugin does not work together with other protection plugins !
Plugin requirements:
- ARG requires a permissions plugin otherwise it will not work!
- Also it requires a MySQL Database otherwise it will not work!
- OPTIONAL: Vault + any supported economy plugin
Plugin setup:
- Configuration - MySQL - Economy: Click here
- Permissions: Click here
- Commands: Click here
Protections:
- Building/removing Blocks
- Explosions
- Fire
- Doors/Trapdoors
- Beds
- Cakes
- All animals
- Bucket fill/empty event
- Piston Events
- Soundblock states
- Repeater states
- Buttons, Leaver, Plates
- Paintings
- All storage stuff (Chest, Furnace, Dispenser, Musicbox, Storage Minecart, Cauldron, Brewing Stand)
- And more
Changelog
Need help or new features?
- Do not post erros/bugs/suggestions in the comments - they will get deleted or just ignored. You have to open a ticket and provide all needed informations.
Feedback can be of course posted in comments.
Metrics & Updates
ARG is using metrics to collect stats! It only collects basic things such as version type, players online, version of craftbukkit, etc.
Go into /plugins/PluginMetrics/config.yml if you wish to disable that.
ARG also includes an update-checker and auto-updater. Go into /plugins/AutoRegionGuard/updater.yml if you wish to disable that.
@ravand
When it's done.
@recon88
Any estimated date on the next update?
@ravand
Will be fixed in v1.7
Is there a way to bypass the /arg confirm ? I tried setting claiming fee to 0 but it still asks the user for confirmation :/
@CaptainTanner
You don't know what the word "optional" means?
Hey. How can remove econy(I don't use it)
@recon88 I think that may have just done the trick... Installed, restarted, and defaults seem to be working as expected now. Thank you so much.
@poundfoot
Well I still can't confirm the problem. Tried it like 10 times now and it works for me.
There must be something wrong with your database I guess.
Edit:
I think it is a permissions problem.
If you join in a world on which ARG is disabled, it will not load your options because you don't have the arg.user node which is required for that.
Edit 2:
Try again please. I removed the permission check for the options loader.
That should fix it if you are using using worlds on which ARG is disabled.
@recon88
Still same problem. Restart toggles them both off.
@poundfoot
Try again... Same link.
@recon88
Hi again :) New players, old players, doesn't matter. The autoclaim and messages are OFF after every restart, and don't come on unless toggled in game. I've added a server message to prompt my players, but people are still missing out on it. Please look into this when you have a chance. Thank you.
@therealmccoy1234
Must be hard to read the last comments :/
Download this version: https://www.dropbox.com/s/ct8ytmmtom39mij/AutoRegionGuard.jar
Deny all permissions in the worlds you don't want to use ARG. If you don't know how this works, ask on the page of the permissions plugin you are using.
Please add "per-world-dis/enabling" This Plugin is awesome, just what I'm looking for. The users can protect totally easy, without needing an admin or typing commands. If you would add this feature it would just be Perfect. Thanks for your good work! Keept it up.
@recon88
Will do. Strangely we have messages, and autoclaim, defaulted to ON ... yet every restart myself and some other players need to re-enable both. Do you think regenerating the config will cause a problem for chunks already claimed? or do you think it's safe to try?
@poundfoot
Just ask a new player... It should be enabled for him.
@recon88
That seems to have done the trick, I possibly could have toggled it off inadvertently. Full config here: http://pastebin.com/cLR4CUQK
Thank you again for the excellent service. I will recommend your plugin anytime I get the chance. And you're more than welcome to come visit our server if you'd like to see your handy work in action. Just PM for the addy.
Take Care recon88!
@poundfoot
Well did you turn on the toggle for you (/arg message)? It's disabled by default (config)... I did not change anything on this part.
@recon88
Wow that was fast. awesome, and thanks. It seems to be working now to no longer show the "want to claim" messages.
However I did notice one other little issue since installing the previous version you posted for us. It seems now that we're no longer seeing the "chunk owned by poundfoot" and "no owned chunk" messages we got with the last release build. Any insights?
@poundfoot
Try again with the same link. Users should no longer get the "want to claim?" message without "arg.user".
@recon88 Thank you so much for your quick response. That file looks to have done the trick and the "arg.user: false" permission seems to be working in our Factions world, now. The only other thing I might add, is that the users are still prompted to claim the chunk after placing their blocks, even though in that specific world they can't. They can also not toggle off. If you think it's possible, could you consider adding a separate permission to use the command "/arg toggle" ? Thanks again :)