Replies: 1 comment 4 replies
-
This happens when the patcher's code cannot compile with the current Mutagen libraries you're trying to use them with. This is normal, and usually just means you have to set it to use older versions until the patcher developer updates. Make sure you are running on the newest Synthesis UI exeMake sure to upgrade to the newest UI Follow the Recommended Versioning Patternshttps://mutagen-modding.github.io/Synthesis/Versioning/ Try Setting the Patcher to "Match"This will tell the patcher to use the versions/libraries it was originally coded with. Upsides:
Downsides:
LockedIf you cannot interact with the above controls, it's likely that you received your profile from a distributor that locked the setup to avoid accidental modifications. You can override this by going to your profile settings and unchecking "Lock Versioning" Fall back to known working setupSynthesis has a button in a patcher's versioning area called: Assuming you've HAD a previously successful run on the patcher, it will be able to set all the settings to point to that setup explicitly. Try to Discern Why the Patcher is UnhappyYou can click the "Blocking Error" text, and usually it will give some detail text on why the patcher is unhappy. Usually, though, it just means the patcher can't compile against the newer code. In this case, setting a specific older Mutagen version, or selecting "Match" as described above is your best option, until the patcher devs do some work to upgrade. |
Beta Was this translation helpful? Give feedback.
-
So you upgraded something, and now your patcher won't run due to a "Blocking Error". What are your options?
Beta Was this translation helpful? Give feedback.
All reactions