Minecraft Version

1.20.1

Mod Version

19.0.4

Mod Loader

Forge

What environment are you running the mod in?

Client

Issue Description

Description of my observation:

• Using prism launcher
• Having 2 instances of mc 1.20.1
• A: had no open loader but was used earlyer to create datapack
• B: was setup directly with open loader and created datapacks in it

When i added the datapack from B to A, installed open loader before BUT not load the game in between,
added all config inside the proper folders, the game started normaly, but did not load the datapack.(at least in new world from the beginning)
Using another datapack was the same.

Then i removed all config files from openloader and started the game.
Closed it,
placed same files in same folders,
created new world again and open loader was showing the datapacks properly.

Summary:

1. If you dont run open loader once before adding datapacks it could make problems
2. Adding the same path & data from another instance dont work

All together, i think it is not intended like this and my wild guess is that on first init open loader is not checking properly for path or not initilaizing it properly, if there is teh right path but not inited from open loader.

Hello, thanks for reporting this issue. I am a little confused by what you mean though. If you're still having this issue could you make a step by step guide to reproduce the issue?

Sure.
If you use smth. like curseforge or prism.

1. Create a instance(A) with whatever mods you want, except open loader
2. Have a instance(B) allready ready with open loader and a datapack inside the config folder
3. On closed instance A, closed instance B, copy B's config ...minecraft\config\openloader with the datapack to instance A
4. Install open loader instance A
5. Open Instance A and the datapack wont be found

No matter if you now restart, delete the config folder and copy paste it new in.
The only solution is:

1. Delete the config folder
2. Start Instance A
3. Close instance A
4. Copy the exact same folder structure (or even only the datapack)
5. Start instance A again

And the datapack can get loaded normaly.

Kinda a edgecase, i think that happens cuz openloader thinks it is "initialized" allready, but smth. on the init is missing if only the config folder is in the correct path existing.

Hope that explains it properly.