Null Guard Fix for Goety

A small patch (about 3KB) that fixes frequent crashes caused by Goety summons.

Problem

When a Goety summon (such as a Hellfire or a zombie servant) takes damage, the game may crash due to a "timing entity" null pointer exception. This happens most often when multiple summons of the same type are nearby, or when there are ownerless summons. The crash stack always points to Owned.java:186 -> Entity.java:2236.

Root Cause

Goety's Owned.isAlliedTo(Entity) forwards a null entity to vanilla Entity.isAlliedTo. The damage revenge target AI passes an already-cleared lastHurtByMob() value when spreading damage to nearby mobs of the same type, and vanilla 1.20.1 dereferences the parameter without a null check (p.getTeam()) -> causing an NPE.

Fix

A null guard was injected at the entry point of Owned.isAlliedTo: it returns false for a null argument (a null entity can never be an ally). It does not affect game balance and does not change AI behavior — it is purely a null-safety fix.

Compatibility

• Can be used together with RevelationFix, Goety: Revelation, and all Goety addons.
• Please install it on both the client and the server. For integrated servers, the host must install this mod.
• Contains only one mixin; does not include any Goety code. Licensed under MIT. Please remove the jar file to uninstall.

Thanks to Polarice3 for Goety (https://github.com/Polarice3/Goety-2).