2022-02-17 21:37:57 +01:00
# Debugging
If you run into issues with respackopts and cannot find a solution here,
2023-09-02 12:56:13 +02:00
you may contact me directly (details are at the bottom of this page)
2022-02-17 21:37:57 +01:00
2022-02-19 15:10:53 +01:00
## Look at the config file
2022-02-17 21:37:57 +01:00
Respackopts stores configurations next to their corresponding resource packs (`some pack.zip.rpo` usually)
This file contains all applied config options as saved by respackopts.
2022-02-19 15:10:53 +01:00
## Dump the internal representation
2022-07-28 14:10:59 +02:00
Running `/rpoc dump config` will dump all data available about the enabled packs, including their config options (but not individual configurations like .rpo files)
2022-02-17 21:37:57 +01:00
2022-08-28 20:43:13 +02:00
You can use this if a respackopts.json5 isn't working as expected
2022-02-17 21:37:57 +01:00
2022-02-19 15:10:53 +01:00
## Dump GLSL code
2022-07-28 14:10:59 +02:00
You can run the command `/rpoc dump glsl` to dump the shader code generated by respackopts to a file.
2022-02-17 21:37:57 +01:00
I recommend reading through it if your shader is misbehaving.
The content imported to your shader by the integrations will equal the dumped code.
2023-06-29 17:03:10 +02:00
## Dump scope
If your conditions aren't working as expected, you can use `/rpoc dump scope` to output muScript code representing the scope passed to your conditions.
Comparing this with your condition should help you figure out most issues.
2023-08-13 23:03:26 +02:00
## Dump asset
You can dump individual files with `/rpoc dump asset <identifier>` .
This allows you to see the actual file minecraft will use for a given identifier.
This is especially useful when using file expansion.
2022-02-19 15:10:53 +01:00
## Verify that the option you are using exists
2022-02-17 21:37:57 +01:00
One common issue is that you removed an option but still use it somewhere.
The log will usually reference that option and the source.
2023-06-29 17:03:10 +02:00
You can use the dumped scope as a reference for what actually exists for your condition.
2023-08-14 17:06:18 +02:00
Aditionally, you can use `/rpoc execute` to execute muScript snippets (be aware that you will need to prefix your entries with your pack id when doing so)
2022-02-17 21:37:57 +01:00
2022-02-19 15:10:53 +01:00
## Ensure you are using the correct dots
2022-06-04 19:43:49 +02:00
Respackopts only supports normal dots. If you write commas or colons by accident,
your pack WILL fail to load.
2022-02-17 21:37:57 +01:00
2022-02-19 15:10:53 +01:00
## Avoid infinite loops
2022-02-17 21:37:57 +01:00
Ensure that you do not reference an original file or a previous fallback from a fallback.
2022-06-04 19:43:49 +02:00
Respackopts WILL crash if it runs into an infinite loop!
2023-10-05 18:18:04 +02:00
If you get a `StackOverflowException` , you can enable `debugLogs` , which might help you figure out what is wrong.
2022-06-04 19:43:49 +02:00
## Contact me for support
If you are unable to identify the issue, you can try [contacting ](https://jfronny.gitlab.io/contact.html ) me.
As respackopts is a complex mod, there is a non-zero chance that your issue may be caused by a bug in the mod.
Even if the issue is in your code, I can still try helping you fix it.