In a game with combat, you would probably need to keep track of who is killing who, and this is done most of the time by inserting an ObjectValue tag into the humanoid who was killed, and then setting the value of it to the player who got the kill. To understand how to make an anti-combat logger, we will need to learn three things: Losing inventory items) from dying in your game, then you really don’t need to account for combat logging, unless you still want to punish the player for leaving the game mid-combat. This is why I’m making a tutorial on it so that games with PvP (especially if it’s a big part of your game) are secure against combat logging.
This would make PvP unfair and probably defeat some, if not a lot of its purpose in your game. This can get really annoying for genuine players looking for a fight because of the fact that the other player can just leave and not lose anything whatsoever. This can be a major issue for a lot of games if it isn’t accounted for, because it allows players to instantly leave mid-fight without any of the consequences of potentially dying.
This happens because if a player leaves mid-combat, they would be leaving at a point where they would have had no punishment, which means that it would be saved when they leave and loaded back into the next server they joined, since they left before they could potentially die in the first server. Combat logging is logging out on a game in a middle of a fight (in ROBLOX’s case, leaving a game) to avoid dying and potential repercussions from dying, like losing items.
0 kommentar(er)
