Integrated Legacy Minecraft Ban System: Difference between revisions

From RetroMC
Jump to navigation Jump to search
mNo edit summary
m (Added some info regarding last letter in JBans ID URL)
 
(21 intermediate revisions by 3 users not shown)
Line 1: Line 1:
The '''Legacy Minecraft Ban Database''' ('''LMBD'''; [https://bans.johnymuffin.com/ https://bans.johnymuffin.com]) is a public list of banned players on Minecraft servers runnning on legacy versions.<br />
[[Category:Server internals]]
If a player gets banned & placed on the LMBD, that player cannot connect to other servers which are using the LMBD plugin.
The '''Integrated Legacy Minecraft Ban System''' ('''LMBS'''), formerly '''Johny Bans''' ('''JBans'''), is a centralized, cross-server ban system for Minecraft servers running on legacy versions.<br />
It was initially released specifically for [[RetroMC (server)|RetroMC]] and [[BetaLands]] on 28th December 2020, and received an update on 26 January 2021, which added support for attaching evidence to bans.<br>
Later on, other servers were added.
<hr>
Its primary interface, the '''Legacy Minecraft Ban Database''' ('''LMBD'''; [https://bans.johnymuffin.com/ https://bans.johnymuffin.com]) is a public list of banned players on servers using the LMBS.
Players banned on one server using the LMBS can't join others using it.
On [[RetroMC (server)|RetroMC]], there is a dedicated subdomain that shows purely bans issued from there on the main list ([https://bans.retromc.org https://bans.retromc.org]), although other bans can still be seen.
<gallery>
File:LMBD-1.png|The main page of the LMBD.
File:LMBD-2.png|A player's ({{user|Noggisoggi}}'s) page.
File:LMBD-6.png|The disconnect message a banned player sees if they connect to a server using the LMBS.
</gallery>
== Commands ==
* <code>/jban <username> (reason) (duration)</code> - Ban a username on the LMBS.
* <code>/junban <username></code> - Unban a username on the LMBS - this will pardon any and all bans a specified username has across servers.
* <code>/jbcode</code> - Recive the authentication code for the LMBD.
* <code>/mbexceptions</code> - Manage server-specific ban exceptions.
== Ban ID page ==
== Ban ID page ==
[[File:LMBD-3.png|thumb|right|The page of a ban ID.]]
All ban ID pages use this format:
All ban ID pages use this format:
  <nowiki>https://bans.johnymuffin.com/b/xxxxxE</nowiki>
  <nowiki>https://bans.johnymuffin.com/b/xxxxxE</nowiki>
where <code>x</code> is a placeholder value.
where <code>x</code> is a placeholder value. The last letter can be changed to a <code>U</code>.
=== Information ===
{| class="wikitable" style="margin:auto"
*; Username
|+ Ban information
*
! Attribute !! Comments
*; Admin
|-
*
| Username ||
*; Reason
|-
- Fallback value is <code>Ban Reason Not Specified</code>
| Admin || The player who issued the ban (and the one with <code>/jban</code>)
*
|-
*; Expiry
| Reason || Fallback value is "<code>Ban Reason Not Specified</code>".
- Default value is permanent
|-
*
| Expiry || Default value is "<code>Permanent</code>".
*; Server
|-
*
|| Server ||
*; ID
|-
*
| ID ||
*; Time Issued
|-
*
| Time Issued || The time zone of the LMBD server is UTC -05.
*; Pardoned
|-
*
| Pardoned || It'll be set to "<code>Yes</code>" if the ban is pardoned or the player is unbanned via <code>/junban</code>.<br />It won't be set if the ban expiry time passes, if there is one.
*; Active
|-
== Ban modification ==
| Active || Same conditions as the above attribute, but it'll be set to "<code>No</code>" if the ban expiry date expires, if there is one.
Only staff members of servers participating in the LMDB can modify bans.<br />
|}
=== Ban modification ===
Only staff members of servers participating in the LMBS can modify bans.<br />
They need to run <code>/jbcode</code> to get an authentication code to login.<br />
They need to run <code>/jbcode</code> to get an authentication code to login.<br />
After authentication, they can modify the information (reason, pardon, expiry) on the bans they themselves have issued, but not bans someone else has issued.
After authentication, they can modify the information (reason, pardon, expiry) on the bans they themselves have issued, but not bans someone else has issued and on bans where they have themselves banned.
== Evidence submission ==
<gallery>
Authentication is also required to upload evidence, however, evidence can be uploaded onto bans issued by other staff members.<br />
File:LMBD-5.png|Ban modification modal.
Evidence deletion can only be done by the ban issuer.
File:LMBD-7.png|The error message a player recives if they try to modify their own ban.
</gallery>
=== Evidence submission ===
Evidence is required for bans to take place cross-server.<br />
Authentication is also required to upload evidence, however, evidence can be uploaded onto bans issued by other staff members on other servers, but evidence deletion can only be done by the ban issuer.<br />
The LMBD doesn't accept WebP images, so <code>&format=webp</code> (Discord) must be removed from the image URL.
<gallery>
File:LMBD-4.png|Evidence submission & deletion UI modals.
</gallery>
== Ban appeal methods ==
== Ban appeal methods ==
A player needs to contact the server that banned them to appeal their ban.<br />
They can also contact other servers for a server-specific exception.<br />
Should that server be currently offline, they can request other servers using the LMBD to unban them.<br />
For RetroMC, evidence is required for a ban to be valid; see [[RetroMC Staff Policy Manual#2. Documentation of Ban Evidence]].
<hr />
* '''Ban appeal form''': [https://forms.gle/SYwKDGK2FHEsHBV1A https://forms.gle/SYwKDGK2FHEsHBV1A]
* '''Email address (used for appealing Discord bans)''': <code>[email protected]</code>

Latest revision as of 10:20, 18 September 2024

The Integrated Legacy Minecraft Ban System (LMBS), formerly Johny Bans (JBans), is a centralized, cross-server ban system for Minecraft servers running on legacy versions.
It was initially released specifically for RetroMC and BetaLands on 28th December 2020, and received an update on 26 January 2021, which added support for attaching evidence to bans.
Later on, other servers were added.

Its primary interface, the Legacy Minecraft Ban Database (LMBD; https://bans.johnymuffin.com) is a public list of banned players on servers using the LMBS. Players banned on one server using the LMBS can't join others using it. On RetroMC, there is a dedicated subdomain that shows purely bans issued from there on the main list (https://bans.retromc.org), although other bans can still be seen.

  • The main page of the LMBD.

    The main page of the LMBD.

  • A player's (  Noggisoggi's) page.

    A player's ( 16.png Noggisoggi's) page.

  • The disconnect message a banned player sees if they connect to a server using the LMBS.

    The disconnect message a banned player sees if they connect to a server using the LMBS.

Commands

  • /jban <username> (reason) (duration) - Ban a username on the LMBS.
  • /junban <username> - Unban a username on the LMBS - this will pardon any and all bans a specified username has across servers.
  • /jbcode - Recive the authentication code for the LMBD.
  • /mbexceptions - Manage server-specific ban exceptions.

Ban ID page

The page of a ban ID.

All ban ID pages use this format: 

https://bans.johnymuffin.com/b/xxxxxE

where x is a placeholder value. The last letter can be changed to a U.

Ban information
Attribute Comments
Username
Admin The player who issued the ban (and the one with /jban)
Reason Fallback value is "Ban Reason Not Specified".
Expiry Default value is "Permanent".
Server
ID
Time Issued The time zone of the LMBD server is UTC -05.
Pardoned It'll be set to "Yes" if the ban is pardoned or the player is unbanned via /junban.
It won't be set if the ban expiry time passes, if there is one.
Active Same conditions as the above attribute, but it'll be set to "No" if the ban expiry date expires, if there is one.

Ban modification

Only staff members of servers participating in the LMBS can modify bans.
They need to run /jbcode to get an authentication code to login.
After authentication, they can modify the information (reason, pardon, expiry) on the bans they themselves have issued, but not bans someone else has issued and on bans where they have themselves banned.

  • Ban modification modal.

    Ban modification modal.

  • The error message a player recives if they try to modify their own ban.

    The error message a player recives if they try to modify their own ban.

Evidence submission

Evidence is required for bans to take place cross-server.
Authentication is also required to upload evidence, however, evidence can be uploaded onto bans issued by other staff members on other servers, but evidence deletion can only be done by the ban issuer.
The LMBD doesn't accept WebP images, so &format=webp (Discord) must be removed from the image URL.

  • Evidence submission & deletion UI modals.

    Evidence submission & deletion UI modals.

Ban appeal methods

A player needs to contact the server that banned them to appeal their ban.
They can also contact other servers for a server-specific exception.
Should that server be currently offline, they can request other servers using the LMBD to unban them.
For RetroMC, evidence is required for a ban to be valid; see RetroMC Staff Policy Manual#2. Documentation of Ban Evidence.

Retrieved from "https://wiki.retromc.org/index.php?title=Integrated_Legacy_Minecraft_Ban_System&oldid=6637"