-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't I register DynClientResourcesGenerator
in client init hook on fabric?
#181
Comments
DynClientResourcesGenerator
in client init hook in fabric?DynClientResourcesGenerator
in client init hook on fabric?
Send log |
|
whats that better ui texture mod? tis somehow conflicting with it. i cant even find it around |
oh wait its your mod |
so i think my assert init code is a bit busted atm. What i usually do is skip fabric client entry point and just do if(PlatHelper.isGetEnv().isClient() ClientStuff.run() which is virtually identical to the initializer one as fabric itself runs one right after the other |
But I can't do client stuff with fabric loom EDIT: EDIT2: |
After thinking, I can't touch things in the client in the common source set. |
Anyway, reflection magic just works. Should I close this issue? |
oh interesting i didnt know that was a thing. im not sure if i can geet a good fix for this. i have to see if i can make my code run after the client initializer instead of in it |
I've removed that restriction. should work for client stuff once again |
The moonlight not init phase
Method has to be called during mod initialization phase
The text was updated successfully, but these errors were encountered: