Imagine yourself, fighting someone you'd been fighting for ages and losing to. Losing gear, resources and your dignity. You've landed a good hit and you've turned the tides and are about to get your last stab to get your resources back, when all of a sudden, the player disappears into thin air and disconnects.
Combat loggers are a massive pain in the backside to competitive players in games, it creates unfair escape methods for players, and if servers choose to outlaw it, it takes moderators constantly online to circumvent it. This is where plugins like CombatLog and CombatLogX, plugins that kill and temporarily ban players doing it, come in with a strict defense against combat logging.
Whilst I dislike people who log out to escape fights or run away with gear, I'm also against the premise of outright banning for it, because this can affect their standing in the community and if they want to rise the ranks later on, which is why I invented SkeletalLog.
Skeletal Log
2. Skeletal log version designed for ObstructMC/Tribes based on Mineplex Clans
3. What the player sees upon rejoining after the skeleton is killed
Skeletal Log is a type of combat log defense plugin that instead of banning or instantly killing a player, it will spawn a skeleton where they stood with all of their gear for players to kill. This skeleton entity is a fake player and is designed to execute exactly the same events and stat changes as you would get if you actually killed the real player. Upon killing the skeleton, they drop all of the equipment that the other player had on them. It does not perform any bans or inventory wipes unless the skeleton is killed.
Skeletal Log went through various iterations of what entity should be used, how it should be displayed, and even a version where the entity would attack people around it, mimicking the player that left. In the end, a vegetative skeleton was chosen as this was the least intensive on servers. Servers that do actually used custom versions of SkeletalLog were able to mask the skeletons as fake player entities to make it more realistic.
In the second photo, you can see a different type of skeletal log. This is a version that was designed around a factions/clans type raiding system present in ObstructMC & Tribes during their development. When 2 factions, or clans, started fighting, they'd gain warpoints for killing each other. During a clan war, if a clan member was killed by another clan, they'd lose a warpoint, if they killed a member of that clan, they'd gain a warpoint. If a clan lost -25 or under warpoints, the enemy would be able to use cannons on their base and break/raid their chests. Making sure Skeletal Log worked with that system was important, so in the model you see, if a clan at war killed an enemy skeletal log entity, they'd gain a warpoint and the other clan would lose one. The skeletal log entity also would not expire until the war ended.
PVP Protection
In some versions of Skeletal Log (ObstructMC & Tribes versions for example), there was also a PVP timer system. This was a system that prevented new players from being attacked or killed by people on the server, but also stopped them from being able to pick up non-environmental items, participate in world events, or enter clan territories. This system was put in place because the gamemode was quite difficult to learn and get a hang of, so their leadership wanted a way to protect new players so they could explore before jumping into competitive play.
If a player had an active PVP timer, a combat log entity would never spawn, players could not attack them, and they could not be harmed by traps or cannons. The PVP timer that was custom built into certain copies of Skeletal Log featured a system where the player could disable their own PVP timer and join the fight early, but moderators could also remove them from players, set custom ones, and toggle if the player could toggle it or not. This was quite helpful for events and such.