We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Paper
1.19.4
If you first load a file and then a folder with "//schematic loadall", the wrong symbol is displayed for the folder. (see video)
"worldedit.schematic.load.symbol": "[L]", "worldedit.schematic.plus.symbol": "[+]", "worldedit.schematic.minus.symbol": "[-]", "worldedit.schematic.x.symbol": "[X]", "worldedit.schematic.0.symbol": "[O]", "worldedit.schematic.dash.symbol": " - ",
//schematic clear
//schematic loadall test1.schem
//schematic loadall test/
//schematic list
//schematic list test/
Show "[-]" in any case when the complete folder is loaded. No continuity mistakes.
https://redstoneworld.de/videos/intern/FAWE_Schematic-list-symbols.mp4
No response
FAWE, build 639
The text was updated successfully, but these errors were encountered:
Well actually, it should show any file / folder with a - when they are loaded, but it doesn't do that for me too, so it is a bug
Sorry, something went wrong.
No branches or pull requests
Server Implementation
Paper
Server Version
1.19.4
Describe the bug
If you first load a file and then a folder with "//schematic loadall", the wrong symbol is displayed for the folder. (see video)
To Reproduce
//schematic clear
//schematic loadall test1.schem
//schematic loadall test/
//schematic list
--> "[+]test"//schematic list test/
--> both files are loadedExpected behaviour
Show "[-]" in any case when the complete folder is loaded. No continuity mistakes.
Screenshots / Videos
https://redstoneworld.de/videos/intern/FAWE_Schematic-list-symbols.mp4
Error log (if applicable)
No response
Fawe Debugpaste
Fawe Version
FAWE, build 639
Checklist
Anything else?
No response
The text was updated successfully, but these errors were encountered: