Switching over to Prism

[thesillychicken Profile]

With the news that the server will be switching over to prism fully users are going to lose the ability to look block changes without a mod's help
I plan on bring this up at Town Hall this weekend.

So the permissions I'm requesting are:
prism.wand.inspect
prism.lookup

This will give us the /lb tool functionally back when we get rid of logblock.

So the question I'm asking you guys is:
Do you think we should get these basic permissions for Prism?

[PosterAnonymous Profile]

Yes, because it allows the average user to determine if they have been griefed to begin with. Many-a-night a mildly inebriated Poster breaks his own blocks, forgets, and later tries to modreq the "griefing".

[asim0v Profile]

First of all, I'm not even sure that we are switching over to Prism. I personally like it and the functionality it brings. That's not to say all the mods feel that way. There has not been a discussion yet regarding getting rid of one. Prism was installed because it offered features LogBlock did not, namely entity tracking to kills to animals/villagers/broken item frames can be rolled back. Prism and LogBlock are run in tandem because we were testing out Prism. The LogBlock data has not been imported into Prism, so we have to use LogBlock for changes older than Prism's implementation.

Prism has some issues too, such as not being able to do a global rollback (unless Curley changes the max radius from 100), which is LogBlock feature I have used before to roll back everything a griefer had done. I'm sure there are some other drawbacks too (maybe), but I can't think of them off the top of my head -- I'm a huge fan of Prism.

Now on to whether or not the players should have access to Prism features the way they currently do with LogBlock, that I am undecided. As a player (before I was a mod), having basic usage of LogBlock was a enormous boon to running Sky5. But then it wasn't widely known as it is today. As I understand it, and Curley could tell me for certain if I asked, he was fine with certain players using it before as long as it remained a secret. It has not.

[Timberwolf1777]

I completely understand your and curley's view on this, asim0v. However, I have to agree with PA on this. I cant even begin to state the value of being able to determine what happened to a block before doing a modreq. For example: If I hadn't had logblock, there would have been dozens of modreq's for water griefing from me alone post 1.5.1 due to the water source block spawn glitch. For your, vantes, and the other mods sanity, leaving the power to check block history in the hands of the players seems like a no brainer. Up to you guys though. Seems like the value of preventing most modreq's before they happen would outweigh whatever issues that letting players check block history would create.

-Timber

[abigail Profile]

whatever block changes mod is being used from now into the future, there are also changes i have looked at that i /lb tooled on my first builds. "oh yeah, i did that" so that i only /modreq'ed the actual griefing (including the time the vines griefed my house, which have been removed to never again).

i will stand by what the mods can agree on. I just wanted to say that being able to use the log look-up allows me to give the mods an easier time to work on the /reqs that need working.

(it was a 4 month or so old house, that i modified 3 months before, i though someone had gone it and redecorated 9.9 )

[Inertpyro Profile]

Being able to use log block to try and solve problem before modreq is helpfull. I've also used it to look up who's property I am building near so I can contact them to see if things are ok with me building there.

[abigail Profile]

thats the other reason inert. that and when something was epic i could tell them so if they were online

[TehRage Profile]

Being able to use log block to try and solve problem before modreq is helpfull. I've also used it to look up who's property I am building near so I can contact them to see if things are ok with me building there.

I agree. The logblock access has to have cutdown on modreqs considerably. I use it all the time and don't want to think about getting along without it.

[Curley]

I am completely for having players be able to lookup block changes, the only time I ever blocked it was during the discovery of the exploit to place the bedrock block down. If we move to prism I will maintain the same level of abilities to the players, whatever prisms equivalents are.

As for prism features, as of now it is still running on the default generated config(hence the global rollback limit and missing features). We have a discussion thread running as we use prism more and more to decide what setting would be good for the server. I believe when we are done prism will handle all that logblock did and more.

As for now you should not worry, logblock will stay active till we're good and ready to switch and when we switch you'll have the same abilities you have, just potentially a slightly different way to access them.