Protecting Builds, Preventing Grief, and CanyonSMP Rules

Now that the SMP is open and people are beginning to build, explore, and make the world their own, we're also beginning to see how some of the systems we put in place actually work with a real community.

One of those systems is GriefPrevention and land claims.

I've heard feedback from both sides. Some players appreciate being able to claim their builds and know that their things are protected. Others have run into frustrating situations involving claims, including problems around Nether portals and access to certain areas.

I've also seen some uses of the claiming system that, while technically possible, don't really fit what CanyonSMP is supposed to be.

So I want to clarify what these systems are here to accomplish.

Claims are for protection, not control

The purpose of a land claim is simple: you should be able to build something without worrying that another player will destroy it or take your things while you're gone.

Claims are not intended to give players a way to control other players.

Using a claim to deliberately trap someone, block access to important shared infrastructure, interfere with another player's build, or otherwise use the protection system against another player goes against the purpose of the system.

Put simply:Claims are a protection tool, not a weapon.
For now, GriefPrevention will remain on the server. That doesn't mean its current configuration is permanent. I'll continue listening to feedback and adjusting things as we learn what works well for CanyonSMP.

Claims aren't what make something yours

There's another important distinction I want to establish early:

An unclaimed build is not an invitation to grief or steal from it.

Claims are a technical protection. They aren't what establishes ownership.

If someone obviously built something, stored their items somewhere, created a farm, or otherwise put work into something, respect it regardless of whether they remembered to claim it.

CanyonSMP should not become a game of finding things the plugins technically allow you to take or destroy.

Prevention, accountability, and moderation

As the server grows, we're putting several different layers in place rather than expecting any one plugin to solve every problem.

Rules establish what is and isn't acceptable behavior on CanyonSMP.

Protection systems, such as GriefPrevention and anti-cheat, prevent many common problems before they affect somebody else.

Logging gives us accountability. The server now keeps detailed records of changes made to the world, allowing staff to investigate what happened, who was involved, and when it occurred.

Moderation and rollback are the final layer. When something does go wrong, we can look at the circumstances, make a judgment, and when appropriate, restore damage rather than simply leaving another player to deal with it.

This also means that something being technically possible does not necessarily make it acceptable.

Minecraft and its plugins have plenty of strange interactions and edge cases. There will always be something I didn't think to prohibit ahead of time. Please don't treat an overlooked technical loophole as permission to do something that is clearly harmful to another player or the community.
What's next

Until now, CanyonSMP hasn't had a formal rules document. With the SMP actually open and a community beginning to form, it's time for one.

I'll be working on the first version of the CanyonSMP rules soon. The goal isn't to create a giant list of restrictions or police how everyone plays Minecraft. The goal is to establish a few clear expectations so everyone understands what kind of community we're trying to build and where the boundaries are.

In the meantime, the basic principle is pretty simple:

Play fairly. Respect other players and their work. Don't use server systems to make somebody else's experience worse.

And if you're genuinely unsure whether something is okay, ask.