@twilit badge uploaded a log, Axiom version: 2.7.0
Environment: Windows 11, 1.20.1 & 1.20.4
Mode: N/A
Description
After about a month of attempting to figure out what was disallowing me from launching more than one instance of MC with Prism, due to a very cryptic error that was thrown, I tried selectively disabling mods as a last ditch effort, and Axiom ended up being the issue, with Axiom installed on both instances (completely separate files, the instances are in separate .minecraft folders, and I even tried using different installations of Java 17 while attempting to debug.) it appears to crash.
I then tried launching with just Axiom and FAPI on both, and the second instance crashed. With Axiom just installed on one it works, and without axiom at all it works as well.
The order in which the instances are launched does not matter, its always the 2nd instance that tries to load with axiom that ends up crashing about 1/3 of the way through initializing. The other instance loads up and works fine, with all axiom features fully functional, and other than this both instances of minecraft work perfectly alone.
Logs from each crash:
Log 1, 1.20.4 launched 2nd
Log 2, 1.20.1 launched 2nd
Steps to Reproduce:
Install PrismMC,
Create 2 instances, one for 1.20.1 & 1.20.4
Install fabric, FAPI, and Axiom on both.
Launch both instances.
The instnace launched last will crash.
- Fabric 0.15.10 on 1.20.4
Possible Solutions:
- Update Fabric from 0.15.10 to 0.15.11
Recommendations:
- Update Axiom from 2.7.0 to 2.8.1
- Update Yet Another Config Lib V3 from 3.3.2+1.20.4 to 3.4.2