[xii69]

What was wrong

Activation range used to keep entities active during melee attack cooldown via attackTicks. In 1.8 that field went away (cooldown moved into the melee goal), and Spigot left the check commented with “missed mapping?”. Mapping it to at would be wrong — that’s arrow hit timer. Without a real cooldown signal, mobs can deactivate mid-swing window under EAR.

What this changes

Restores an entity-level attackTicks (20 ticks), set from melee attack entry points, decremented like hurt ticks, and re-enables the EAR immunity check. Does not misuse at.

Why this is needed

EAR is a performance feature; it shouldn’t freeze combat timing by putting attackers to sleep during their cooldown. This puts back the immunity the TODO was pointing at, with the correct meaning.

Testing

ActivationRangeAttackTicksTest 5/5; server suite green; package OK.

[windcolor-dev]

This change doesn't really do too much right? We already have this check in there

			if (entity instanceof EntityCreature && ((EntityCreature) entity).getGoalTarget() != null) {
				return true;
			}

[kalibrieren]

This change doesn't really do too much right? We already have this check in there

			if (entity instanceof EntityCreature && ((EntityCreature) entity).getGoalTarget() != null) {
				return true;
			}

restoring attackTicks is way different and should be kept

[windcolor-dev]

Yeah you're right, I guess it's better to add it