• Add functionality to pull/push punishment protection status from the API

Fixes the following issue: Prevent repeat / simultaneous / accidental punishments against a single user

Allows spectators to use /tp as a tool for spectating.

(Note: Some of this code is definitely redundant, and the message feedback is formatted in plain-white text, but other than that, the functionality works).

See ( https://github.com/PGMDev/PGM/commit/f4e3827d112375a140a680b94fc0e29c2998ef15#diff-fe197d73af5c4c80dd8d2181881669a030886c0a3c144e09b8545e64147167b8L29 )

whether its competitive -> whether it's competitive

Player, match and map statistics -> Player, match, and map statistics

Two examples of this is -> Two examples of this are

Please raise any questions or issues on the Issues page or on the Warzone Discord -> on the Issues page or the Warzone Discord On is redundant in the sentence above.

Issue:

Although Minecraft 1.7 is regularly limited to a select few PvP-oriented users, some players and staff members still choose to connect using this version. However, some commands provided by Mars do not produce a properly formatted output

Background:

1.7 support was never provided officially or intentionally before. With the switch to PGM, there is now full gameplay support with it. Mars should then match such functionality where possible.

Some commands, like /puns, /rank player <player> list, or /tag player <player> list seem to be unaffected by this regression.

Visual examples:

/stats 1.7.10

/stats 1.8.9

/lookup or /lu 1.7.10

/lookup or /lu 1.8.9

/notes 1.7.10

/notes 1.8.9

Affected areas / files:

• Stats command
• Lookup command
• Notes command etc.

Issue:

Members of the "Infected" team during an Infection game or map can no longer be provided with a compass that will point towards remaining humans.

Background:

A TGM pull request converted a compass given to a member of the "Infected" team into a human tracker, increasing the chance of winning (necessary for cases where lots of players are online).

It was up to the mapmaker to include a compass in the kit, but compasses could also be given to players through the command /give @a[tag=infected] compass.

Proposed / potential solution:

Note: ince Infection was previously hardcoded for Warzone, compasses were rather "exclusive" of TGM, so it may be undesirable to introduce the feature to upstream PGM.

1. Mars could read through the loaded map's XML and find if it has been labeled as Infection through the game="" attribute of the root <map> tag, or also through the <game> sub-element.
2. If true, then check if a compass is provided through a <kit>
3. Convert such compass into a human tracker

With the power and versatility of PGM, mapmakers could then be able to decide when to give Infected the compass through the use of time filters, making it unecessary to provide it from the beginning or to manually give it through commands.

Example XML snippet:

# Initial Infected kit
    <kit id="infected-kit-start">
        <helmet locked="true" unbreakable="true" color="00FF00" material="leather helmet"/>
        <chestplate locked="true" unbreakable="true" color="00FF00" material="leather chestplate"/>
        <leggings locked="true" unbreakable="true" color="00FF00" material="leather leggings"/>
        <boots locked="true" unbreakable="true" color="00FF00" material="leather boots"/>
        <item slot="0" unbreakable="true" material="iron sword" name="`2`lInfection Sword"/>
    </kit>
    
# Infected kit with a compass (human tracker)
    <kit id="infected-kit-compass">
        <helmet locked="true" unbreakable="true" color="00FF00" material="leather helmet"/>
        <chestplate locked="true" unbreakable="true" color="00FF00" material="leather chestplate"/>
        <leggings locked="true" unbreakable="true" color="00FF00" material="leather leggings"/>
        <boots locked="true" unbreakable="true" color="00FF00" material="leather boots"/>
        <item slot="0" unbreakable="true" material="iron sword" name="`2`lInfection Sword"/>
        # Include human tracker
        <item slot="1" material="compass" name="`1`lHuman Tracker"/>
    </kit>

# Infected team first spawns with initial kit, no compass
    <spawn filter="before-10s" team="infected-team" kit="infected-kit-start">
        <regions yaw="90">
            <point>-1080.5,40,-1015.5</point>
        </regions>
    </spawn>
    
# After 6 minutes, infected are given the kit with a compass (human tracker)
    <spawn filter="after-6m" team="infected-team" kit="infected-kit-compass">
        <regions yaw="90">
            <point>-1080.5,40,-1015.5</point>
        </regions>
    </spawn>

Issue:

The list, playerraw and playerpreset broadcast commands no longer exist.

Background:

TGM had commands which allowed staff members with the respective permission(s) to:

• /broadcast list List available preset broadcasts

• /broadcast playerraw <player> <message> Broadcast raw text to a target player, with support for color codes and decorators (bold, italics, etc)

• /broadcast playerpreset <player> <broadcast id> [args] Broadcast a preset to a target player

Desired solution:

Add these commands to Mars

Affected areas / files:

• Broadcast commands

Issue:

Broadcasts are only governed by a time interval and cannot be triggered by events, but only by executing commands.

Background:

Broadcasts in TGM allowed server administrator to configure several events that triggered a broadcast.

Such events are no longer available with Mars.

Desired solution:

Server owners should be able to specify some event(s) that will trigger the broadcast(s). Lack of the events property would mean the broadcast is just periodically sent in accordance with the fixed global interval.

Some events extracted from TGM:

• onFirstJoin (when the player first joins the server)
• onJoin (when the player joins the server)
• onMatchResult (when the match ends)
• onTeamJoin (when the player joins a team)
• onMatchLoad (when a match is loaded)

Example config:

- name: broadcastOnJoin
  message: This broadcast is sent every time you join the server!
  events: onJoin # Broadcast is sent to the player every time they join the server

- name: epicBroadcast
  message: This broadcast is sent every minute, but also when you first join the server!
  # This broadcast is sent when the player first joins the server, 
  # then periodically (every 1 minute according to the global broadcast interval)
  events: onFirstJoin, interval

Affected areas / files:

• Broadcast
• Broadcast feature
• (API) Broadcast model
• (API) broadcasts.yml

Issue:

Automatic broadcasts using Mars use a fixed, global unmodifiable one minute interval.

Background:

Broadcasts in TGM allowed server administrator to at least configure a desired global interval for any loaded broadcasts. This interval could be changed at any time from the server panel.

Currently, with Mars, only the following properties are available: name, message, permission, newline. Broadcasts are also managed from the backend (API) by manipulating the broadcasts.yml file.

Desired solution:

Server owners should have the ability to configure a default global interval for all broadcasts, as well as an individual interval property for each broadcast.

Example config:

global-interval: 60 # One minute
broadcasts:
- name: vip
  message: This is a VIP broadcast!
  permission: broadcasts.vip
  interval: 30 # Broadcasted every 30 seconds, overrides global setting
  newline: false

Affected areas / files:

• Broadcast
• Broadcast feature
• (API) Broadcast model
• (API) broadcasts.yml

Issue:

Punishments may only be issued or reverted by staff members connected to the server. Server administrators and staff with access to the server's console should be able to execute such commands as well.

Background:

The /pun command and the /revertp command will only take a player as a sender, preventing the console from using them at all (will output "You must be a player to use this command").

Desired solution:

Allow the use of /pun and /revertp through the server's console. Note that these commands require GUI interaction if some flags or fields are not provided by the sender.

For example, executing /revertp <punishment id> without any input for the optional [reason] field will open a confirmation GUI in-game for the staff member to manipulate. Since this is not possible through the console, the lack of a reason should default to a pre-defined message such as "No reason provided".

The same applies to the /pun command, avoiding interference from GUI-required interaction.

Affected areas / files:

• Punishment command
• Revert punishment command

Issue:

The /stats command provides little information to the player about new tracked stats.

Background:

Mars and the Mars-API now track a plethora of new statistics that are of interest to players and members of the community. Development of the plugin initially chose to only display / match those statistics previously displayed by TGM so as to not confuse new or existing players. Only some new additions like "First bloods" and "Win %" were included.

It has now been a considerable amount of time that should be enough to introduce these new stats to players.

Desired solutions:

The /stats command should simply display more stats to make it more attractive and feature-complete. The image below is a proposal of what the new output could include:

Affected areas / files:

• Stats command