We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Using ATlauncher and Bisect Hosting.
On startup after modifying the enigmaticlegacy-common.omniconf, the file changes into an ERRORED file and a new file generates with default values.
Problem produced on modpack server, reproduced on singleplayer instance with only Enigmatic Legacy and required dependencies.
Crash Log: No crash experienced.
The text was updated successfully, but these errors were encountered:
Removing added mobs from the S:CursedRingNeutralAngerBlacklist section prevented error and other config changes work as intended.
Example: S:CursedRingNeutralAngerBlacklist <minecraft:iron_golem, minecraft:bee, minecraft:wolf>
What would be the proper way to change this field?
Sorry, something went wrong.
Aizistral
No branches or pull requests
Using ATlauncher and Bisect Hosting.
On startup after modifying the enigmaticlegacy-common.omniconf, the file changes into an ERRORED file and a new file generates with default values.
Problem produced on modpack server, reproduced on singleplayer instance with only Enigmatic Legacy and required dependencies.
Crash Log: No crash experienced.
The text was updated successfully, but these errors were encountered: