Server Implementation

Spigot

Server Version

1.19.2

Describe the bug

Using #saturate in any instance where it would be applicable, such as replacing some existing terrain with a saturation effect, (//r #saturate[156][100][0][120]), results in an error. After looking at console, there were various blocks that the plugin tried to check for in fawe's texture folder and it could not find apparently. These can be seen in the debugpaste I've provided. I double-checked that the jar I provided was the latest, and it was (1.19.2.jar). It appears that what all of the blocks share in common is that they all have some form of block state. I looked into the jar file through winrar to see if some of these block states were in the blockstates folder (1.19.2.jar\assets\minecraft\blockstates) and they were.

I suppose either my textures folder I uploaded was incorrect, although I obtained it from my own .minecraft/versions folder, or the plugin is just looking for the incorrect json files for the proper saturation. To counter the former, I deleted the textures jar I provided and let the plugin download the jar from mojang (https://athion.net/ISPaster/paste/view/5ccd411609ff47a3825b4afa1aaa0b1b). The same error seemed to persist.

To Reproduce

• Select an area
• Try and apply some saturation pattern to it (//r #saturate[156][100][0][120])
• Receive error

Expected behaviour

The saturation effect should work as normal, instead of giving an error.

Screenshots / Videos

No response

Error log (if applicable)

No response

Fawe Debugpaste

https://athion.net/ISPaster/paste/view/3f1b1ddc83eb44779f10f29eda6a31ce

Fawe Version

FastAsyncWorldedit version 2.4.5-SNAPSHOT-275;5da558e

Checklist

• I have included a Fawe debugpaste.
• I am using the newest build from https://ci.athion.net/job/FastAsyncWorldEdit/ and the issue still persists.

Anything else?

No response