Trusted /tb

I have applied for guard, twice. I guess ill just record griefing as well and pray those 10 minutes result in a /tb that doesn’t get reset when they quit and rejoin.

As did I. It’s not the end when you get denied the first time.

How about adding a /votebuild that is only seen and voted by the members of the team affected?
Similar to the already accepted votekick, but less disruptive and easier to pass.
I often suspect (unproven) opposing team members of a votekick from not voting because the cheater / griefer is helping them or not affecting them.

I agree

Also useful (if at all possible) would be an interrogate block (/ib) command, allowing players to determine who built a certain block.
It is often hard to determine for sure who is griefing the tower without stoppng to look for a longer time. This tool would help.

Neat idea, I’m not sure how that would work or if it is even possible. I’ll ask BR about it.

The person who got voted to get tb’ed would just leave and come back and grief again. Might as well kick him and give him the 30 minute ban.

If votekick scripts can prevent logout/login, then a voteblock script should be able to re-apply togglebuild to a voteblocked player doing the same?

What if that person isn’t logged in the first place? I would assume the server would have to re-apply a tb based on IP then, but I have no experience in creating a command.

I meant “leave and come back”.
Basically same bit of script that prevents a votekick and come back could be used to re-apply togglebuild to a votebuild-ed griefer.

I’d like the power to disable pure evil grieffers building rights. But now you even get “trusted” users grieffing and abusing their trusted status to avoid being votekicked.
:smiley:

Trust me, if these get properly reported, then they will get decomissioned and permabanned so fast that they will never know what hit them.

The fastest way to fix a problem is to provide us with evidence or if you are unable to the time and server when it happened and a heads up.
We do look into these things.

I really only read the first page, but by the logic I was seeing in support of trusted getting /tb, why wouldn’t trusted also get /tk in case of hackers? At that point, why don’t you just apply for guard?

Maybe read the other 3 pages, it has already been said on them, trusted are not going to get /tb, nor /tk

I thought why not about a /votetogglebuild but that would be better to do a /votekick directly on a player that is really griefing (so he would not evade directly, but the problem is as always false votekick)
There is already a script to check how many blocks a player has destroyed (even if it doesn’t mean all the time it’s a griefer), i don’t know if everyone playing has access to it or if it’s active on servers (blockinfo.py with /griefcheck or /gc); if not maybe it should be something, so you can check before voting /yes at least ; if yes just remember to verify a player with that command before voting and as always warn the admins or provide evidence, as Scipio said

Sil, Torch is saying you might as well apply for guard if you want to get access to /tb as trusted. He was jokingly suggesting adding /tk into the mix to deal with hackers, making a point that trusted are not guard lite or part of staff, which is a good point.

Oh thanks AEM ^^ I didn’t see it as a joke
And yes indeed that’s right

If you want to twist your slippery slope logic in to it, why not give trusted members the ability to perma-ban? The point was to prevent griefing, not to grab as much power as possible. This subject was closed a while ago and I was left agreeing that a separation in class was the better choice.

The whole point with suggesting a /votebuild command was that the voting group for this vote could be reduced to the members of the team being griefed, thus making a successfull /votebuild more likely because players of the opposite team can not oppose by not voting.
I often see members of the unaffected team not vote because the griefing benefits them.
This is one way to reduce the problems inherent to a /votekick for one specific subcase without going down any slippery slopes.

/edited for spelling