Fix reach ring

[Shadow1590]

Fixes #18125
I kind of fixed this a while back but then forgot about it.

The problem was with how the reach ring gets applied on world load. It gets applied in onWornTick and adds the hash of the player to the ring. On a server this was fine because the data is not shared. In singleplayer the server part sets the hash first and when the client checks it it finds the player hash already set so it does not apply it.

Idk if this is the best way to fix it but it works :)

[wlhlm]

I've looked at this and it fixes the issue just fine as you say. Thanks! It's just I think, ideally, this wouldn't have to be stored in the NBT tags at all as it's just runtime information for the mod to know if it needs to run setup on first tick. There is the rare chance where the player hashcode could get reused between world loads.

I know this just does what Botania was already doing.

[Shadow1590]

Ok, so i thought about this and, first thing that came to mind was to add a method in baubles that gets called only on the first tick but that would be a much bigger task and i havent found another bauble that would benefit from that.
And with the saving it as a runtime information im not really sure how to do that.
Would that be some kind of i guess a static data structure that would know wheter the the given player was given the effect of the ring on the server/client?