What steps will reproduce the problem?1. Allow hard drive to fill up2. Come back a couple hours later3. Weep at the hundreds of hours of work that were lost because CommandSigns doesn't have proper safeguards when auto-saving
What is the expected output? What do you see instead?
I would expect that CommandSigns would leave the current signs.yml file intact if it can't write the new one, rather than overwriting the good file with an empty one!!
What version of the product are you using?
Do you have an error log of what happened?
Please provide any additional information below.
Is there any way to recover my hundreds of hours worth of configurations, or has CommandSigns completely shit the bed on this one?
You allowed your harddrive to be filled, if you were using a host then they mat of removed some thing.
To post a comment, please
or register a new account.