customwrits.xml being deleted

[Jeromis]

In the last few days, every time my craftbot encounters a writ with an item that it does not recognize, it appears to be resetting the customwrits.xml file to basically blank. So even if I edit the file with the recipe name that craftbot expects and the actual recipe name, it still gets blocked from completing writs because the file is deleted over and over.
I have tried copying over the blank file with a good file, but same thing happens, it just keeps getting reset. Is there a setting or something that I'm missing?

Here's what the file looks like after it hits the recipe it doesn't recognize:
<?xml version='1.0' encoding='UTF-8'?>
<!-- Generated by LavishSettings v2 -->
<InnerSpaceSettings>
</InnerSpaceSettings>

That's the whole file.

 

[mycroft]

In the last few days, every time my craftbot encounters a writ with an item that it does not recognize, it appears to be resetting the customwrits.xml file to basically blank. So even if I edit the file with the recipe name that craftbot expects and the actual recipe name, it still gets blocked from completing writs because the file is deleted over and over.
I have tried copying over the blank file with a good file, but same thing happens, it just keeps getting reset. Is there a setting or something that I'm missing?

Here's what the file looks like after it hits the recipe it doesn't recognize:
<?xml version='1.0' encoding='UTF-8'?>
<!-- Generated by LavishSettings v2 -->
<InnerSpaceSettings>
</InnerSpaceSettings>

That's the whole file.

Question , are you editing the file while craft is running?

it could also be you are writing the data format incorrectly causing the file to be miss-read , this will then make the script fail to read any information and when craft exits it will write out a blank file.

 

[Jeromis]

I was not editing the file while craftbot was running.

I'm pretty sure I got the format right because I've added custom recipe names many times in the past and never had a problem until this week. The problem actually originated not with me making a change, but with the file being essentially erased. The first time I discovered it was not because I had been recently editing the file; instead it was when I went to edit the file because it wasn't working and I found that the file was empty.

I tried making the file be read-only but that didn't help (go figure) and like I said, I tried replacing it with a good file. I'll keep trying things.