Steps before creating a bug report

\n
\n\n- Check the [issues](https://github.com/Malcolm-Q/LC-LateGameUpgrades/issues) page of the repository and check if there's any already reported issue. If there is one, use that one instead of making a new one.\n- Ensure that the issue you are reporting is not an intended feature of this mod.\n\n

\n\n

Steps when creating a bug report

\n
\n\n- Locate the ``LogOutput.log`` file in the ``BepInEx`` folder and post it in the bug report.\n - This file will always contain the logs of the **last** game instance.\n - It will help me find where the root of the issue might be.\n- Post the list of mods (or profile-code relevant to the modpack) if they are relevant to the issue\n - E.g a feature works without a mod, stops working when that mod is present. Also applies to the other mod's features.\n - If unsure if a certain feature is affected by some other mod, post the list regardless. Better to have more than less.\n- Try to be as descriptive as possible when creating the bug report.\n - Saying only that something isn't working might not always be sufficient. I might need more details about the state of the game or the configurations used when the issue occurs.\n\n

Optional Steps

\n
\n\n- List of steps to reproduce the issue if the issue is consistent\n - Having a list of steps can help further figuring the cause of the issue to resolve it.\n - This won't always be a case for inconsistent issues so try to be as descriptive when it happens\n\n- Suggestion to resolve the issue reported\n - This would require coding / game code knowledge\n - The suggestion has to be reasonable and objectively better or equivalent than the current implementation\n - You can make [pull requests](https://github.com/Malcolm-Q/LC-LateGameUpgrades/pulls) for these suggestions rather than make an issue and I will be able to review it and possibly accept it if it's all good.\n\n

\n\n

","actionData","errors"]

Log in to Thunderstore

Details

Categories

Bug Reporting