That way we don't need to test plugins on production...

Once again the discord chat forced my hands.

The combat logging system has one flaw that annoys many people. It's the fact that it triggers, literally always. People are scared of simply logging off as they think they might get attacked last second and die. One suggestion was to trigger the combat logging system only on player interaction, but that way players can abuse vanilla mechanics to survive lava, etc.

Combat logging should only trigger on direct player damage. When joining the Minecraft server gives the player 3 seconds of invulnerability -> Reduce the 3 seconds to 0.5 seconds. This way if a player falls into lava, they are guaranteed to not get out of it with repeat joining and quitting as they will eventually die. The players only option now is to wait out the reset, which in my eyes is a fair thing.

In addition to the above proposal, a command for logging of safely should be added with a countdown of 5 seconds cancelled by movement or damage. If players log off accidentally or their game crashes without using this command, their health should be lowered to 3 hearts.
If ping allows for this, the player should be kicked before being able to quit informing them to use the command next time.

I'm sure this is on the to-do already, but additional issue tracking never hurt anyone. Seems like an unintended bug?

The idea is that players outside of the game can monitor when other players die, without constantly being on the server. That way players can play when they feel safe on the server due to some threat having died. Additionally, those players who are interested in their own death reason (which due to a 1.20.1 bug does not appear in the disconnect screen) will be able to find out the reason they died or the player they got one shot by.

This issue was introduced by the PortalRunner Discord Community

Some methods are mislabeled. Discord saw this, of course.

Just in case the servers gets lost or re-hosted.

This is caused because after a server restart the list of remaining survivors is cleared

Players should be given 5 minutes of invulnerability only if they are freshly reset players. Also players with this invulnerability should lose it when attacking other players.

Every player kill will add the victims head into a head collection which will be viewable through a command. Players will lose all of their heads on death. The top 3 killers will have their head collections leaked at midnight on server reset in the discord webhook.

In addition to #2, players will know when the server has reset and who has kept their items into the next world. The message could also include all deaths of a session.

This feature has not been decided on yet!

Put bounties on a player will motivate people to kill a certain player as they will get a reward for it. This will also form temporary teams where multiple players team up to attack one player that may be many levels of gear above them.

Before this feature can be implemented however a few things need to be cleared up:

• Should the reward be an item, a title, or something else?
• Should the reward be given out by a player or the server?
• How is the reward spread out if multiple people teamed up?

As discussed in #4, the head and ranking system have been split into two different issues.

Three crowns (gold, silver and bronze) will be given to 3 random players. Similar to heads, crowns are held in a separate inventory viewable through a command. Killing a player holding a crown will transfer their crown to the killer. Each of the three crowns represents a rank on the server (gold=1st, silver=2nd, bronze=3rd). The leaderboard will be printed on each reset in the discord via webhook.
Note: A player can only hold one crown, meaning if they kill a player with a higher ranked crown, they will switch crowns with the victim.

The goal of this system is to motivate players to attack each other and ignore lower ranked players as they are not worth anything.

Easier to read and people forced me to do it.