2 suggestions

[Scedion]

I'm not currently sure what causes the combat bug.

I know that multiple "in combats" sent to the client stack, for some infernal reason, so if the client ever receives two "in combat" packets, two "out of combat" packets will need to be sent to remove them.

However, this was already happening. A fix I tried a couple of days ago was to ensure the client is always taken out of combat when teleporting (as happens when you change zones), in case the combat state is linked to the map you're currently in. It seems that didn't work either.

Can try editing WSCT to explicitly message when going in combat and out of combat, with the map ID, to see if something's going wrong there.

Fix everything

[Ley]

I'm not currently sure what causes the combat bug.

I know that multiple "in combats" sent to the client stack, for some infernal reason, so if the client ever receives two "in combat" packets, two "out of combat" packets will need to be sent to remove them.

However, this was already happening. A fix I tried a couple of days ago was to ensure the client is always taken out of combat when teleporting (as happens when you change zones), in case the combat state is linked to the map you're currently in. It seems that didn't work either.

Can try editing WSCT to explicitly message when going in combat and out of combat, with the map ID, to see if something's going wrong there.

Fix everything

It's not like twitching your fingers and **** gets fixed...

[mvazquez99]

Morfee, I understand the potential for "abuse" if the In Combat feature is gone. But this "abuse" is (a) uncommon and (b) not that big a deal (only slightly frustrating if you were about to kill someone). Whereas not being able to join Scenarios because of "in combat" is common and severely impacts game play. Seems best and easiest to eliminate the "in combat" feature entirely while it needs fixing.