Yeah, this is a huge problem. I would argue it would be more fair to add a timer like if you didnt get a direct hit last 10 seconds or didnt hit someone you can mount. Looks like there are more complicated calculations going on behind, which cause some players with certain classes or in certain situations to be stucked in combat forever.

For example magsorc with Lightning Form, Surge, Streak and Death Dealer Fete can almost never get out of combat. I dont know which skills or sets or situations causing this. This does not happen in Vengeance. You can mount there very predictably.

Maybe they could just not have hostiles not be quite so hostile. If you are just passing through they could leave you alone. It seems robotic and weird that all these creatures and entities want to kill you as soon as you are near.

ankeor wrote: »

Some people will come up and say "Just go find the mob and kill it"
Again my point is that being stuck in combat does nothing makee the player experience worse, especially overland. Why keep it?

At a guess, because it would require a significant recode. The same aggro code that applies to group dungeons applies to solo overland et al. The code is shared because it saved on initial development costs when first written.

The current state is a mish-mash of concepts. The original code was there to stop people just running passed mobs in dungeons. You had to kill the mobs so you coudl interact with a door or lever to progress. It was also a way to stop gear changes. "Joining Encounter In Progress" was added to DLCs as a way to combat speed runners, as the DLCs were a more open format, and mob packs were more easily skipped. To discourage skipping, but keeping the more open form of dungeons, requirements were then put on the higher achievements that meant all mobs had to be killed. "Joining Encounter In Progress" was then back-added to the earlier dungeons to address the problem of speed runners there too and provide uniformity.

All the while that original aggro code is ticking away. The problem with re-writing it is that it's spaghetti. Changing something could break the entire aggro system. The code needs fully mapping, the problem areas identifying, and then the code splitting so that "in combat" works differently in dungeons, overland, battlegrounds, and Cyrodiil/IC.

Rogue_Coyote wrote: »

Just allow mounting in combat. Thats the only change needed

Well it would be preferred if they fixed the runaway effect timers keeping you flagged as if in combat. You'd think zos would persue fixing these considering vengeance and overall performance testing.

Not too hard to pinpoint either, youd probably setup a system to determine who hasnt been hit by enemies for 15s or so and then record what effects or timers are ongoing after that. From there setup flags in the code of those skills or effects and start diagnosing.

ankeor wrote: »

"Just go find the mob and kill it"

Best is when its a player in pvp in a constant burning atate and you have no fire weapons but some random guy with a fire ballista is why you can't get on your mount rn

However what if we made combat not stop anything anymore?

Mob members stuck in walls. Hitting the borders of a WB encounter. Oops, didn't see that bear 1k meters back. Let's be stuck in combat! And that's just in PvE. The support system literally has a subcategory for being stuck in combat. That speaks volumes. Something's gotta give, because this hasn't worked properly for....ever.

Sincerely signed,
Player who sat stuck in combat for over ten minutes last night while staring at spot dead body used to be