feature: updates to blizzard sorc

[jasorello]

I had accidentally polluted my commits in #695 with bad line endings, this is a cleaned PR with just the blizzard sorc changes

This PR attempts:

1. Better static field usage, porting the more complicated logic over from the nova sorceress character, as well as moving the distance logic to the common config so it can be more easily referenced across all other sorceress builds
2. Moved blizzard-specific configurations to a function within the struct, keeping the same ease of configuration but without polluting the rest of the character package with consts (i also fixed some other cross-character references that were caught up in this)
3. I did some optimization of the blizzard attack loop. The problem I'm trying to fix here is that on a faster machine, we're iterating through this loop much faster than the bot can actually perform any of the attacks. We can hit 200+ attack loops on a boss after just performing 6 or 7 actual attacks within the game. I think the issues here may also be present in other characters, but I'll wait for someone smarter than me to weigh in.

I also included the switch from sorceress to blizzardsorceress that was suggested in #691

[jasorello]

common configuration that can be leveraged via s.Data.CharacterCfg.Character.Sorceress.StaticFieldMinDist

[jasorello]

I noticed there were issues in the builds with accidental references across the characters which might have unintended results. I thought this might be a better pattern to make it more clear which settings are relevant for each character. Is there a better way?

[jasorello]

This is mostly stolen from the nova sorceress

[jasorello]

These values have a bit of a buffer over the bare minimum for the difficulty to minimize wasted casts

[jasorello]

I've noticed a few people in Help noting that their character is bailing early but not knowing why. I think many of them are from hitting this loop in their respective character. This log message should help identify those cases better.

[jasorello]

This avoids unnecessary attackloop iterations for bosses with an extended death animation like andariel

[elobo91]

Hello . Thats a good catch. There isnt any character using this yet but maybe it could be useful in that case?

could use npcmode 0 and 12 instead of life stat to determine if its dead if its problematic.

[CarlPoppa1]

Yes I've been testing with this after every attack in KillMonsterSequence, seems to work:

				if s.Data.PlayerUnit.Mode == mode.CastingSkill {
					attackSuccess = true
				}

Then at the bottom:

if attackSuccess {
			s.Logger.Debug("Completed attack loop", slog.Int("completedAttackLoops", completedAttackLoops))
			completedAttackLoops++
		}

[elobo91]

I meant using mode dead and death . Dead is when it just died, death is when its extremely dead ( after animation) or i inverted

[jasorello]

switched this to cast our leftskill until we're out of cooldown instead of just a single time. This should better leverage our activity during blizzard cooldown without resulting in a new attack loop.

I've pulled it ahead of the blizzard self-cast because otherwise we were usually hitting the self-cast block while blizzard was on cooldown.

New behavior should be:

while on cooldown:
	cast leftskill
	
if timeToCastSelfBlizzard:
	cast selfBlizzard
else
	cast regularBlizzard:

[jasorello]

This function was no longer being called