docs: mention dump scope
ci/woodpecker/tag/docs Pipeline was successful Details
ci/woodpecker/tag/jfmod Pipeline was successful Details

This commit is contained in:
Johannes Frohnmeyer 2023-06-29 17:03:10 +02:00
parent 4e5510757b
commit 796bbe40e6
Signed by: Johannes
GPG Key ID: E76429612C2929F4
1 changed files with 5 additions and 0 deletions

View File

@ -18,9 +18,14 @@ You can run the command `/rpoc dump glsl` to dump the shader code generated by r
I recommend reading through it if your shader is misbehaving.
The content imported to your shader by the integrations will equal the dumped code.
## 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.
## 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.
You can use the dumped scope as a reference for what actually exists for your condition.
## Ensure you are using the correct dots
Respackopts only supports normal dots. If you write commas or colons by accident,