/baninfo

Estingray13

Let people see other peoples /baninfo. This could be useful for a number of reasons:

1. If people are hiring for a job in real life, they perform background checks. Why not have the same on meep?
2. Protect against possible scammers/greifers during trades or plot clearing jobs.
3. It is useful to know reasons someone may have gotten banned when you are giving someone assistant or a certain rank in your town.

Dat_Coffee

Darke_Amethyst

Toostenheimer

+1 It used to show if a player was serving a punishment or something, then they disabled the use of it.

Draqq

adlovesdogs

Ban history is for staff only for many reasons. Ban history is private because a lot of people don't want other people to see their ban history. So I completely disagree.

-1

Toostenheimer

Ban history is for staff only for many reasons. Ban history is private because a lot of people don't want other people to see their ban history. So I completely disagree.
-1
~ @adlovesdogs

No not banhistory. It's /baninfo. The original command for the players to check if a player is banned and how long it will be.

Draqq

Ban history is for staff only for many reasons. Ban history is private because a lot of people don't want other people to see their ban history. So I completely disagree.
-1
~ @adlovesdogs

Care to explain some of these reasons? IMO there are many reasons why bans should be public. I don't get your reason, if you don't want other people to see your ban history for whatever reason, don't get banned in the first place.

I'll post my reasons when any staff member can provide examples as to why it's a bad choice to hide bans from the public.

n00bslayer_99

If people could see my ban history I'd never be able to get any kind of job on Meep involving trust.

People are unbanned because they have served their punishment, they don't need past mistakes to completely screw up their time on the server.

-1.

Adam34falcon

People are unbanned because they have served their punishment, they don't need past mistakes to completely screw up their time on the server.
~ @n00bslayer_99

Ban history is for staff only for many reasons. Ban history is private because a lot of people don't want other people to see their ban history. So I completely disagree.
~ @adlovesdogs

Pmx728

Ban history is for staff only for many reasons. Ban history is private because a lot of people don't want other people to see their ban history. So I completely disagree.
-1
~ @adlovesdogs

This

SX1

I see more benefits seeing a ban than not seeing a ban. (If this makes sense)

Pros:
- Stop rank scammers (If they scammed, or chargebacked)
- Could stop luring if someone is asking for tp in wild.
- Griefers not being able to be co-owners because the mayor doesn't trust them
- Wow this person hacked in kitpvp 4 times! He shouldn't join your pvp team!

Cons:
- staff don't see any pros with this

For all I even care it could even start now and not keep hold of any bans until after this plugin is released. Even if everyone got a clean slate. (Yes, I know this would give terrible players another chance)

Muunkee

Ban history is for staff only for many reasons. Ban history is private because a lot of people don't want other people to see their ban history. So I completely disagree.
-1
~ @adlovesdogs

'many reasons'
Uhm... I can name one.... but eh.

People subject to unfair or mistaken bans can have this used against them.
However, if people didn't want a big banhistory, maybe they shouldn't have gotten banned.
I don't see any real reason to add this, but there's no real good reason not too either.

Deinen

I am personally against this idea, for a few reasons. As a staff member, I do feel our players, or customers, should receive at least modicum of privacy. While I do understand that a person should live with their actions, and the consequences of such, it also makes me uneasy. As a member of the community, I can see how mean people can be to eachother, on a fairly wide scale. I'm not so comfortable then handing out weapons, in this case reasons, to bash on someone.

However, I do understand there are many valid reasons for wanting this, and I think it does deserve another consideration, perhaps.

metr0n0me

I'd like to point out the distinction between banhistory and baninfo. Baninfo is the player's current ban information (eg. permed by Klutchdecals for duping). Banhistory is the player's full list of bans--(eg. permed by Klutchdecals for duping, temped for 1h by metr0n0me for spam, banned by Deinen for towny theft, etc.)

I think the compromise where /seen indicates a player is banned is good; however it would be useful if /seen also shows the time the player is banned for as well. A full banhistory, in my opinion, is way too much because having players access their peers' banhistory and holding that against them is counterproductive and can undermine staff authority. For example, if you view my banhistory, you'd see 10 bans for spam and language, and a ban for hacking. Personally I don't mind this--I view it as extra motivation :)--but making banhistories public can lead to counterproductive threads like "Why did [XXXX] get staff? He is so unqualified!!!111!1! If he got accepted with that banhistory why did I get denied??? Im better" and that would create tension within the community in a time where we don't need any more polarizing effects.

Kling

I find it unnecessary for players to have it. I have been banned for duplicating but it was a staff mistake, if some players see that duplicating was a past ban they probably would not trust me.
So it is nice to have that privacy. -1

buildmaster1000x

I'd like to point out the distinction between banhistory and baninfo. Baninfo is the player's current ban information (eg. permed by Klutchdecals for duping). Banhistory is the player's full list of bans--(eg. permed by Klutchdecals for duping, temped for 1h by metr0n0me for spam, banned by Deinen for towny theft, etc.)
I think the compromise where /seen indicates a player is banned is good; however it would be useful if /seen also shows the time the player is banned for as well. A full banhistory, in my opinion, is way too much because having players access their peers' banhistory and holding that against them is counterproductive and can undermine staff authority. For example, if you view my banhistory, you'd see 10 bans for spam and language, and a ban for hacking. Personally I don't mind this--I view it as extra motivation :)--but making banhistories public can lead to counterproductive threads like "Why did [XXXX] get staff? He is so unqualified!!!111!1! If he got accepted with that banhistory why did I get denied??? Im better" and that would create tension within the community in a time where we don't need any more polarizing effects.
~ @metr0n0me

Thank god you pointed out the confusion between baninfo and banhistory. It was making me mad. The only thing that would be useful on /seen would be to add the length of the ban. Nothing other than the red line and the length of the ban.

JoeK

No not banhistory. It's /baninfo. The original command for the players to check if a player is banned and how long it will be.
~ @Toostenheimer

++1

Thank god you pointed out the confusion between baninfo and banhistory. It was making me mad. The only thing that would be useful on /seen would be to add the length of the ban. Nothing other than the red line and the length of the ban.
~ @buildmaster1000x

Estingray13

Id like to make a revision! Maybe for bans that were fairly recent would show, that way people who made mistakes in the past could have privacy, but someone hiring for a job could know if the person has committed any wrong-doings recently before they hire.

Dat_Coffee

Non-staff should be able to see important bans, such as rank scamming or hacking, as these are important in deciding wether to trust someone, but players don't really need to see how much someone has been banned for spamming or tpa killing.