-
-
Notifications
You must be signed in to change notification settings - Fork 49
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
1.16.5 (Forge 36.2.20) mod compatibility - Mods I found messed with or crashed Vivecraft #125
Comments
Most of these are known issues, even if they aren't in the compatibility sheet (found at vivecraft.org/forge-mod-compatibility). |
The DefaultOptions one is weird, and Performant is on my todo list for investigation. GUI sizing is a "fix this someday" thing because it's a total pain in the ass. Modded tool visuals being wrong is a known issue and can't really be fixed. |
can't write there, that's why I came here. Also, update on the 3rd person model. While it works, the placement of the rendered model is behind you and about 300 blocks tall lol. Not sure what incompatibility is causing that one to act odd |
I actually found that it is just mods with modular tools that mess up the visuals, which is why I claim they aren't tools behind the scenes |
I'll keep updating this list if I find other mods that break. I've already found that the library Blueprint (abnormals-core) is a crash, which means any mod by TeamAbnormals will crash |
I found one:
Minor Issues: |
So I've been building a little modpack for me and my buddies to play, but I've encountered a few disasterous mods that will crash before Forge has time to create a crash log file. I recommend testing these with MultiMC, as it can display any fatal fault even if the exit code is 0 (which is the reason Forge isn't making a crash log).
Oh, by the way, Vivecraft runs perfectly fine on the newest version of 1.16.5 Forge, 36.2.20!
Crashes
DefaultOptions - If mods are changed when DefaultOptions has saved defaults, Forge itself will crash before Vivecraft even has a chance to start up. Strangely, running the same thing on Desktop works fine... Workaround is to update your default configs before adding it to your launcher (If you've used a CurseForge profile as your modpack directory, just run the CurseForge modloader, as it does not run Vivecraft at all for any reason. This only works using the default launcher.)
Performant - What is supposed to be an amazing helper mod for performance crashes Vivecraft, presumably a mixin issue due to the structuring of the crash log (Thank god for -1 exit codes).
Any mod that makes the game render a 3rd person body - I've been completely unable to make any mod that renders the 3rd person body run in Vivecraft. I don't know what the problem is.
Edit: The mod "First Person Model (Forge/Fabric)" by tr9zw seems to be working. I will be testing further!
Minor problems
Structurize + MineColonies - Structurize works perfectly fine, but in Creative there are extra buttons in the bottom right of the GUI that aren't present in Vivecraft. Potentially a GUI sizing issue.
Tetra, Tinkers' Construct - These mods have the reversed and wierd tool visuals, and I think I know why - They're not actually treated as normal tools at all (I have mods that make sounds when you switch hotbar slots, and they are different for tools. Tetra and Tinkers' Construct tools make the regular swapping to a block sound.) , just items with specific mining tiers, and as such aren't rendered properly by Vivecraft. This is not fixable from what I understand, we just have to hope the creators figure it out.
Contribute
If you guys have any more problematic mods for this Forge version, feel free to add them to this board! It's good to look into these as some mods have easy fixes and some are unfixable completely, and it's nice to know which have workarounds!
The text was updated successfully, but these errors were encountered: