Prevent crashing on servers

[JulianVennen]

When attempting to start a server with oculus installed it causes a crash because oculus attempts to access client-only code.

According to the forge documentation client-only mods should work on servers: https://docs.minecraftforge.net/en/1.20.x/concepts/sides/#writing-one-sided-mods

This PR changed oculus to only listen for events on the client and therefore prevents this kind of crash.

This supersedes #367.

[JulianVennen]

Hey, any update on this?

[dima-dencep]

There are unnecessary changes in this PR that I don't want to merge

[JulianVennen]

Which unnecessary changes exactly are you referring to?

I think I accidentally clicked optimize imports in my IDE, which removed a few imports that were unrelated to the PR. Is that what you mean?

[Veynam]

Also waiting for updates

[JulianVennen]

I rebased the changes to resolve conflicts and undid any unnecessary changes to the import.
Please let me know if there's anything else you want me to do.

[JulianVennen]

Any update on this?

[dima-dencep]

First make a good pr that we can merge
There's a lot of unnecessary code

[JulianVennen]

Please explain to me which part of the code exactly is unnecessary.
The iris class uses various client only classes directly, which results in exceptions when it is loaded at all.
That's why I added the Oculus class and added the EventBusSubscriber annotation to the Iris class, which means it is only loaded on the client.

If you think there is an alternative way to prevent this issue, please let me know

[rilakuma123]

Is it possible to do something like CaffeineMC/sodium#2773

[JulianVennen]

That option does not exist on 1.20.1 (and might be neoforge exclusive).

[dima-dencep]

You moved the initialization to the FMLClientSetupEvent, which may be too late

[Veynam]

Please implement this feature, makes doing some things so frustrating only because of this mod

[JulianVennen]

You moved the initialization to the FMLClientSetupEvent, which may be too late

Too late for what exactly? Keeping the initialization in the constructor is unfortunately not possible, as the EventBusSubscriber annotation does not create an instance of the class (unlike the Mod annotation).
I can use FMLConstructModEvent instead, which is fired "directly after mod instance construction". Would that be better?

[dima-dencep]

Keeping the initialization in the constructor is unfortunately not possible

Then use a static block

[JulianVennen]

Unfortunately, that doesn't work as the mod list is not loaded yet: https://mclo.gs/FmmTXjq
Using the FMLConstructModEvent should result in the same timing as before