[Slayer Helpers] Slayer Highlights, Blaze Helpers and Glow Caching

[BigloBot]

Remade this PR cause The merge conflicts were horrible

• Hitbox Slayer Mob Highlighting
• Glow Effect Slayer Mob Highlighting
• Blazeslayer Attunement highlighting
• Fire Pillar Countdown Notifiications

This PR Also reworks "ShouldGlow" Detection

• There's a "truesight" aura of 20 blocks - I think this is fine because this is just about in range of where nametags begin to shrink to the point of being undreadable, and thus could be reasonably argued you could tell this is where a mob is.
• Anything beyond this distance is raycast to ensure it can be seen
• caches "shouldGlow" for 50ms/1 ticks duration
• caches "canSee" for 100ms/2 ticks duration

[kevinthegreat1]

Btw should be the last review. I have also referenced Aaron's previous review.

[AzureAaron]

Looks good, in future we will need to optimize the glow/box calculations to not constantly run when an entity is rendered.

[BigloBot]

Looks good, in future we will need to optimize the glow/box calculations to not constantly run when an entity is rendered.

I'm sure there's a fair bit more optimisation that can be done, but I noticed that i go from ~0.7% doing these calcs while idling on my island -> 0.25% with these changes which was more than enough for me to be happy with lol

[AzureAaron]

Looks good, in future we will need to optimize the glow/box calculations to not constantly run when an entity is rendered.

I'm sure there's a fair bit more optimisation that can be done, but I noticed that i go from ~0.7% doing these calcs while idling on my island -> 0.25% with these changes which was more than enough for me to be happy with lol

I was talking about iterating the scoreboard to check if we're in a slayer or not. My idea is roughly to create an event for when the mod updates the scoreboard, check the updated scoreboard value and set a static boolean that can be read from. I wasn't talking about anything beyond that though

[BigloBot]

Looks good, in future we will need to optimize the glow/box calculations to not constantly run when an entity is rendered.

I'm sure there's a fair bit more optimisation that can be done, but I noticed that i go from ~0.7% doing these calcs while idling on my island -> 0.25% with these changes which was more than enough for me to be happy with lol

I was talking about iterating the scoreboard to check if we're in a slayer or not. My idea is roughly to create an event for when the mod updates the scoreboard, check the updated scoreboard value and set a static boolean that can be read from. I wasn't talking about anything beyond that though

ahh, well technically that's getting cached too so it's not every frame render, but ur suggestion definitely a far better implementation than the current mechanism