34 lines
1.5 KiB
Markdown
34 lines
1.5 KiB
Markdown
# Debugging
|
|
If you run into issues with respackopts and cannot find a solution here,
|
|
you may contact me through my discord server (look at the mod page)
|
|
|
|
## Look at the config file
|
|
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.
|
|
|
|
## Dump the internal representation
|
|
Running `/rpo dump config` will dump all data available about the enabled packs, including their config options (but not individual configurations like .rpo files)
|
|
|
|
You can use this if a conf.json isn't working as expected
|
|
|
|
## Dump GLSL code
|
|
You can run the command `/rpo dump glsl` to dump the shader code generated by respackopts to a file.
|
|
|
|
I recommend reading through it if your shader is misbehaving.
|
|
The content imported to your shader by the integrations will equal the dumped code.
|
|
|
|
## Verify that the option you are using exists
|
|
One common issue is that you removed an option but still use it somewhere.
|
|
The log will usually reference that option and the source.
|
|
|
|
## Ensure you are using the correct dots
|
|
Ensure conditions follow one of the following conventions.
|
|
Using dots, colons or commas where they don't belong will break your pack:
|
|
|
|
- `<pack id>:<entry id>`, eg `breeze16:bushyLeaves.full`
|
|
- `<entry id>`, eg `bushyLeaves.full`
|
|
|
|
## Avoid infinite loops
|
|
Ensure that you do not reference an original file or a previous fallback from a fallback.
|
|
Respackopts WILL crash if it runs into an infinite loop! |