Cyrodiil Combat Bug: An Interesting Example

gameswithaspoon · March 2021

So a guildmate had made a new add-on called Thank A Healer. The purpose of the add-on is to work like a Kill Counter, but for healers, tracking how much you were healed for in a fight, and giving you the opportunity to thank your healer.

Tonight in Cyrodiil, while one member of the party was AFK at the Allessia transit, and the rest of the group was fighting at Nikel, the templar healer was registering a heal on the AFK party member and placing that member in combat. In and out, over and over. Even after combat at Nikel had ended, and the group was waiting for the outpost to unflag, the combat bug persisted, registering a heal, and placing the AFK party member back into combat for a second.

Screenshots of the add-on data below:

The templar wasn't casting any abilities when the add-on was registering a heal and placing the AFK warden into combat. Just thought that was interesting.

HowellQagan · March 2021

Cyrodiil performance, huh.
Bet this adds to the pile of issues in there.

gameswithaspoon · March 2021

This is the same “combat bug” that has existed for years. But the idea was that you remained in combat.

However, if the data that the add-on is working off is correct, you are entering and exiting combat. And this is occurring when Combat Logs isn’t recording combat, so we’ve no idea what this cross-map heal is. How does one player not in combat, and not using any abilities, heal a player considerably away and place them in combat?