The Aether

The Aether

43M Downloads

Bug: Double Resource reload on initial instance start up [Fabric 1.20.1/0.16.10]

pokesmells opened this issue ยท 4 comments

commented

What Feature Types Apply to This Bug?

System

Other Type

No response

What Type of Bug Is This?

Unexpected Behavior

Mod Loader

Fabric

Mod Loader Version

0.16.10

The Aether Version

1.20.1-1.5.2-beta.5-fabric

Is This Bug a Conflict With Another Mod?

No response

Client Log

No response

Crash Report (if applicable)

No response

Steps to Reproduce

Merely load the game, and the loading restarts all over again and does a second resource reload when starting up the game, like it finishes loading in and does ANOTHER resource reload

What You Expect To Happen

For it to load up normally without doing another resource reload

What Actually Happened

Loaded into the game, the game had finished loading in, and at the end of loading, reloaded resources causing it to load even more and longer

Additional Details

No response

Please Read and Confirm The Following

  • I have confirmed this bug can be replicated without the use of Optifine.
  • I have confirmed this bug is on the most recently supported version of Minecraft.
  • I have confirmed the details provided in this report are concise as possible and does not contain vague information (ie. Versions are properly recorded, answers to questions are clear).
  • I have confirmed this bug is unique and has not been reported already.
  • If playing on a modpack, I have reported this bug to their issue tracker already.
  • I have confirmed that I'm reporting a bug in The Aether I, not The Aether II.
commented

Log?

commented

Log?

Sorry for the late reply.

latest.log

commented

@pokesmells This comes down to compatibility added here for tipsmod. As such will refresh the packs based on the config value here. @bconlon1 Any thoughts about this since this seems like a possible issue if a given modpack is quite big and/or has a ton of resources to load.

commented

I'm not sure if I will be able to fix this in 1.20.1 but I believe I may be able to fix it in 1.21.1+ at least with startup configs.