-
-
Notifications
You must be signed in to change notification settings - Fork 120
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
Bug: Issue on request interface com.aetherteam.aetherfabric.pond.IRegistryExtension #2382
Comments
Can you try removing farmersdelight and relaunching as I might have a hunch to what is occuring |
Will try and come back with update |
Had disabled Farmers Delight and all addons from it, here is the issue persistend, |
Hmm ok, can you next try removing automodpack temporarily. If such persists it will requires some investigation why this occurs as this shouldn't be happening |
Will try it tomorow, automodpack does only make mess on client side, Because it load mixin 4.1 and not the beta mixin, what cause the mixin Injektion problems. I'm work on debuging the issue and tomorow should be come a new automodpack update. But i will try more tests after work tomorow |
@Dragon-Seeker had disabled also Automodpack, but the error occurs again. Will look on other mods, but i don't know, what coult be the issue here, had no problems before |
oh wait, had not seen this issue before ->
|
Tested on Windows 11, same issue, had added again all mods |
@Dragon-Seeker if you had an build to test, i could test it on my enviroment ;) |
Ill see about getting you one later today/tomorrow (Time zones are fun). |
Time zones are really fun, here it is 09:00 am |
@Dragon-Seeker did you found something about this issue? |
Got a new Issue
|
Sorry for the delay on this but I don't exactly know how to send a prerelease build that may fix the issue and some Cumulus rewrite stuff has gotten a bit staled but hopefully such can be dealt with soon. |
@Dragon-Seeker if you had an commit, that finished it, or an pull request, that should be fixed it, you could send me the link there, then i could buid it for me with gradle |
would test the build tomorow, got no time this weekend. |
same issue again
|
@suerion Can you send the latest full log? |
yeah, @Dragon-Seeker here you get it -> |
Hmmm something about this pack seems to conflicting with Aether some how and I don't know what exactly |
Had tried to disable all mods and get allways the same issue of the iregistry, could try again to disable all. But it takes time, will come back again. |
had only looked there fore the class -> https://maven.fabricmc.net/docs/yarn-1.21.1+build.3/net/minecraft/registry/SimpleDefaultedRegistry.html could it be a help? |
@suerion I understand the classes that are involved but I believe you need to binary search your modpack for conflicting mod(s) to figure this out as it is 700 mod pack and by itself the aether dose not have this issue in prod or dev |
Will check in the next few days the pack, to find any mods |
@Dragon-Seeker had found the Culprit... pruhhh |
The conflicting mod (Serilum's Spawn Bundle) is actually a bundle of several mods; can you please bisect through the following possible conflicting mods to further narrow down the cause?
|
@James103 @Dragon-Seeker it has nothing to do with the Mods itself, i think it is only the bundle himself |
What Feature Types Apply to This Bug?
World-Gen
Other Type
No response
What Type of Bug Is This?
Crash
Mod Loader
Fabric
Mod Loader Version
0.16.9
The Aether Version
aether-1.21.1-1.5.1-beta.4-fabric
Is This Bug a Conflict With Another Mod?
Don't know yet
Client Log
Warning on Datapacks: https://mclo.gs/qorkWQ8
Crash Report (if applicable)
No response
Steps to Reproduce
Add Aether on a Huge Modpack Server and try to start on clean modpack, (Mods, config, no world)
What You Expect To Happen
Generate world with datapacks
it has worked a few times, but this time there is the issue
What Actually Happened
Server Stop on Startup
Additional Details
latest server log:
https://mclo.gs/HrF8XJq
Please Read and Confirm The Following
The text was updated successfully, but these errors were encountered: