• Please make sure you are posting in the correct place. Server ads go here and modpack bugs go here
  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

Anyone know of a good antigrief/claim land mod

HeraBulldog said:
Anyone know of a good antigrief/claim land mod? :)
i have seen mytown2 but it's only in beta
Click to expand...

I have a difference take to anti greifing than "wresting" with those mods.

The first thing I do is prevent it from happening in the first place. A whitelisting application process coupled with decent "screening" is usually the end of "mass" greifers and other unwanted players. This "extra" layer of security also ensure you and/or your team knows who are even allowed to join the server.

Next I focus on containing damages. An active admin and/or quality mods will usually keep the server "contained" long before it get to a "beyond repairs" state. Even some responsible players can help you further with containment.

Provided you do those two steps WELL that should ends your days of dealing with greifers and unwanted players at a regular occurrence. However a few will be extra aggressive and will stop at nothing to burn your server through the ground. How do I mitigate these occurrences you ask?...

I have a logging mod called Trust is Nice But... and backups ran by Aroma's bi-hourly running. Should I ever have a "hardcore" greifer or otherwise very unpleasant player I can "pin point" who did it, ban him/her, stop server and reload the world to the latest "clean" state and/or replace materials in game, track down the player from the origin source and figure out what could be done to lower the chances the similar situation would happens or AT LEAST mitigate much of damages the next time around.

Rinse and repeat and your "pain" should be over. :)

I hope this help you somewhat.
 
Techly88 said:
I have a difference take to anti greifing than "wresting" with those mods.

The first thing I do is prevent it from happening in the first place. A whitelisting application process coupled with decent "screening" is usually the end of "mass" greifers and other unwanted players. This "extra" layer of security also ensure you and/or your team knows who are even allowed to join the server.

Next I focus on containing damages. An active admin and/or quality mods will usually keep the server "contained" long before it get to a "beyond repairs" state. Even some responsible players can help you further with containment.

Provided you do those two steps WELL that should ends your days of dealing with greifers and unwanted players at a regular occurrence. However a few will be extra aggressive and will stop at nothing to burn your server through the ground. How do I mitigate these occurrences you ask?...

I have a logging mod called Trust is Nice But... and backups ran by Aroma's bi-hourly running. Should I ever have a "hardcore" greifer or otherwise very unpleasant player I can "pin point" who did it, ban him/her, stop server and reload the world to the latest "clean" state and/or replace materials in game, track down the player from the origin source and figure out what could be done to lower the chances the similar situation would happens or AT LEAST mitigate much of damages the next time around.

Rinse and repeat and your "pain" should be over. :)

I hope this help you somewhat.
Click to expand...
How server administration is REALLY done people. Almost all good modded servers are private/whitelisted.
 
Inaeo said:
You're not wrong, but that wasn't the question...
Click to expand...

It still has to do with anti greifing so I say we are both on topic of the thread's original purpose. Just two difference ways to do the job.
 
FTBUtils is so ligheweight as to be useless.
MyTown2 is interesting, but still in beta, and actually relies on an underlying permissions provider - which it implements a "nice" town / plot system on top of.
Aroma backup is nice for SSP, but if you are managing a server using this mod you are doing it wrong.

The minimum you should be using on a server is a mod like ForgeEssentials. Unfortunately it hasn't seen updates in a while. But ForgeEssentials implements the permissions system that is (mostly) mod aware, including player claims - players can declare what level of interaction other players can have in their claims - access inventories, break blocks, open doors etc. A ticketing system that players can use to submit support tickets (which records the players position). A rollback system where chunks and areas can be rolled back (and forwards) by admins to reverse unwanted changes. Automatic backup. Logging. And more.

Also, if you are running a small / personal server, you can use a tool like McMyAdmin which can sleep the minecraft instance when its not serving players, automatically restart in case of crashes. And provide an external to minecraft system for maintaining rolling backups. Version 2 is free for small servers.
 
Last edited:
Lol managing a white list is a total pain in the ass. The only way to do it PROPERLY and not end up hating every thing Minecraft is to keep your server small, like 15 max small.

The main 2 I know about is Grief Protection that uses a flexible block based system. However it is really quite bad at protection. It will ward vanilla based mechanics but not much else. Barrels you need to punch to get items from will still drop stuff for unauthorized players.
Which is a shame as I like the flexible non chunk based system even if it is a little cludgy.

There's also MyTown, which is not in beta, it's robust protection wise even if heavy handed (will sometimes ban fake players as default) and has a whole host of configurable options and perks. MY PERSONAL problem with it is it's a chunk based region system. When you claim a spot it's gotta be in 12x12 plots bound to the chunk grid. It's tolerable but it can really affect your build style, you really start to realize your builds follow a grid amd become less natural. Plus if a server is stingy with claim space it can be really difficult to manage more natural builds.

Sent from my GT-I9100 using Tapatalk
 
This should be common knowledge for all servers, vanilla, bukkit, modded, whatever, but you need to have whitelists and screen players before they can join, and also make backups often. This way, if someone griefed or accidentally let a wither loose or something (whether on purpose or merely accidental) or anything else happens that flattened large land areas, then go to a backup and you're all set.

TL;DR: Use whitelists, screen players before inviting them, and constantly make backups.
 
On the Whitelist topic:
  • Whitelist is not the end all be all. It is not practical for servers with more then say the 100 players, or for networks.
How to prevent griefs? You can not 100% stop them. Not if you run modded, not if you run vanilla, not if you run vanilla with bukkit plugins.

The best you can do is reduce the ability to grief. How? Their are a few ways. Realize these apply to large server a or networks.
  • Block protection; This is realistically going to be factions, GPS, towns, or MyTown2.
  • Logging; This should be built into your block protection.
  • Staff. Having good staff is a must. Without staff, you really are up shit Creek.
  • Deligation. Realize you can't do everything yourself. You need to learn to trust your staff.
  • A good understanding of configs. A lot of dupes and griefing mechanics cam be negated with configuration changes.
If you really want a whitelist, dont. Go greylist and give people a chance to explore your server before applying. This is called spectators mode.
 
Booker The Geek said:
On the Whitelist topic:
  • Whitelist is not the end all be all. It is not practical for servers with more then say the 100 players, or for networks.
Click to expand...

I has never seen a modded server even reach to Bukkit players' densities. Even "large" ones are no more than ~50 constantly connected people since the last time I browsed server lists.

This is largely due to the fact...
You need to trust your fellow players to use much of modded stuffs.

Then you also need to account that modded contraptions eat considerately more CPU cycles than say a good bukkit setup.

In short modded servers are best going whitelist (coupled with logging AND backups) to mitigate much of greifing and unpleasant players. Otherwise your public server will either lag like no tomorrow, be "dry" of cool things (excessive banning items/blocks and/or even changing the configs to some extend), and/or be like your covered in bubble wrap when all you want to do is take a ride on a bike down at a local park.
 
Whitelists tend to stymie the growth of your server. Assuming people actually want to apply en masse, you or one of your admins will need to be on the ball to evaluate the applications. Depending on the number, chances are you or your staff will half ass an application and you end up letting in the riff raff making the white list pointless.

The only good reason to use a white list is if you WANT a small sub 20 player server. If this is your goal then use a white list. But if you for some reason want a bustling public server then Whitelists make that difficult.

Also a lot of decent players baulk at the idea of Whitelists in general. It seems elitist and the process can sometimes be like applying for a job.

Sent from my GT-I9100 using Tapatalk
 
You must log in or register to reply here.
Back
Top