Maintenance for the week of February 23:
· [COMPLETE] NA megaservers for maintenance – February 23, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
· [COMPLETE] EU megaservers for maintenance – February 23, 9:00 UTC (4:00AM EST) - 17:00 UTC (12:00PM EST)
· [COMPLETE] ESO Store and Account System for maintenance – February 23, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
· [COMPLETE] NA megaservers for maintenance – February 23, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
· [COMPLETE] EU megaservers for maintenance – February 23, 9:00 UTC (4:00AM EST) - 17:00 UTC (12:00PM EST)
· [COMPLETE] ESO Store and Account System for maintenance – February 23, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
Lets fix the CC bug once and for all!!!
LuxLunae
✭✭✭✭✭
Thrassian Stranglers:
Still would have wished to see
"Upon being stunned, etc. CC immunity is granted IMMEDIATELY after and the duration is increased x amount. You will still have to break free (or whatever) to get out of the CC."
"Developer notes: We did this to fix the exploit that many ball groups in cyrodil used when they dropped multiple CCs in a location. It would cause their foes to have to break free twice and even three times or more sometimes. This was due to some type of race condition of the server receiving multiple CCs before the immunity could be set on the foe. So we decided to make the CC immunity top priority and instantly apply after the CC. Any other CC after the cc immunity was applied would be not added to/removed from the queue (or whatever it is). Thus removing the bug. This shouldn't really be a problem as the foe still has to break free, etc. from the CC. It is just that the server won't have to wait for that message anymore. "
It's time to fix the bug and stop those people from exploiting it... LETS GET IT DONE!!!
Edited by LuxLunae on July 15, 2020 2:24AM - Reduced the Spell Damage granted per stack to 92, down from 150.
- Reduced the penalties per stack to 1%, down from 2%.
- The stacks from this set now last 30 seconds and refresh every time you gain a stack, rather than being permanent.
- This set now also grants Weapon Damage.
Still would have wished to see
"Upon being stunned, etc. CC immunity is granted IMMEDIATELY after and the duration is increased x amount. You will still have to break free (or whatever) to get out of the CC."
"Developer notes: We did this to fix the exploit that many ball groups in cyrodil used when they dropped multiple CCs in a location. It would cause their foes to have to break free twice and even three times or more sometimes. This was due to some type of race condition of the server receiving multiple CCs before the immunity could be set on the foe. So we decided to make the CC immunity top priority and instantly apply after the CC. Any other CC after the cc immunity was applied would be not added to/removed from the queue (or whatever it is). Thus removing the bug. This shouldn't really be a problem as the foe still has to break free, etc. from the CC. It is just that the server won't have to wait for that message anymore. "
It's time to fix the bug and stop those people from exploiting it... LETS GET IT DONE!!!
0
-
Ratzkifal✭✭✭✭✭
✭✭✭✭✭I don't think it works the way you think it does. CC immunity is CC immunity. Granting it upon being stunned immediately has you ignore the effects of the CC, even the one you are currently afflicted by. I am pretty sure it's not as simple as writing what you said into the code as it is, because that would probably lead to bugs where you already have CC immunity but the game forces you to break free anyway.
They need to clean up how incoming CC is treated. Maybe give each type of CC a priority depending on its severity and always apply the CC of the highest priority only. That would essentially be the same to how it is supposed to work but make double CC impossible. But I am not a developer so idk how any of this actually works.This Bosmer was tortured to death. There is nothing left to be done.0 -
LuxLunae✭✭✭✭✭I don't think it works the way you think it does. CC immunity is CC immunity. Granting it upon being stunned immediately has you ignore the effects of the CC, even the one you are currently afflicted by. I am pretty sure it's not as simple as writing what you said into the code as it is, because that would probably lead to bugs where you already have CC immunity but the game forces you to break free anyway.
They need to clean up how incoming CC is treated. Maybe give each type of CC a priority depending on its severity and always apply the CC of the highest priority only. That would essentially be the same to how it is supposed to work but make double CC impossible. But I am not a developer so idk how any of this actually works.
That would bog down the servers trying to decide which one has higher prioroty.
The first one that comes in should be the one that grants us CC immunity is instantly and lock out any other ones.
As it is now you MUST break free to be granted immunity.
The server MUST get the break free command in order to tell it to place the immunity.
If the other incoming CCs are overruling that command being placed, it won't give us immunity..
Thus breaking free multiple times within seconds where you should have immunity.
There is NO problem with us getting the immunity after any CC goes to us. You would still have to break free to get out of it.Edited by LuxLunae on July 14, 2020 1:53AM0