Beacon Stats Tracking

[Alpha268]

So, I’ll add my idea here:

In my opinion this game will have issues with griefing. That was always a problem in minecraft, and it will always be a problem.

One thing this game should adress early is said problem. Grieving will make players ragequit, which means that there are less testers and -afterwards- less players.

Often players can be made happy just by knowing who griefed them. Sometimes it turns into a hunting party for his head, but sometimes it is just enough to know who the troll was.

That’s where my idea comes in: Let beacons track the changes in the area they observe: If your beacon allows everyone to build or remove blocks, this method will give you at least the name/names of the griefers. If your beacon allows only members to build and remove blocks, you can see which member went full rampage on your building.

It could be implemented as a table, which is part of a menu that appears when you interact with the beacon. It could be realized this way:

Name        Blocks Added        Blocks removed

Alpha268    1902                5024
Some_Grief  5023                0
...

Filtering could be done in categories like: 24 hours, 48 hours, one week, two weeks, one month, since beacon construction, showing the changes in block numbers in the area during that time.

I do not know whether this game will Support mods, but minecraft has a ton of mods dedicated just to identify and eliminate griefers. If this game does not support any mods, the developers have to give us the tools we Need to supervise our home.

If you have any suggestions, feedback or ideas for improvement, just write it here, the stage is yours!

[drthmik]

beacons, (soon you’ll be able to place and control them yourself) are there to restrict access to building
why even have one if you want everyone to be able to build?
and why bother to do your tracking thing if you have one and only you (and maybe your trusted friend) can do anything?

[Alpha268]

Yes, I agree on what you say, but there is one point that actually convinced me to think about stat-tracking:

If you give others access to building and removing blocks, they might betray you. (It is something I experienced a while ago). With the servers being in the hand of those who host them, there is no administration for the players themselves.

The aim of Beacons is to give you your own “Kingdom” or say “area”. Which also means that you are responsible for everything that happens there, as you can not expect to call the server admin everytime something went wrong.

Giving the players adminstration information about the area they own isn’t contrary to the idea of restricting access to that area. As soon as beacons get additional content (which have been suggested), for example flying (I dont support that idea, but it shows my point), people might want to create a “Everybody-can-contribute-to-my-super-castle-while-flying” beacon, giving flight and access to every player.

Stat tracking can identify griefers, who desecrate your public construction site, but it also can keep track of the biggest contributors and will give you stats about your building (for example that a castle used around 26k blocks stone).

I do agree that this feature will not be useful for two people playing together on the edge of the world. But administration is necessary when a bigger group of people wants to work together. And you don’t want to call the server admin every two days, you want to solve problems on your own. At least that’s my approach.

[Heurazio]

I want to make a supplement to this. I DON’T think we need stat tracking for griefer detection (that’s like drthmik said covered with the current state of beacons) but for player comparison. Stated this in Oort Forum Post

[Author]

Posts