Zugg Software :: View topic - Files still created in the CMUD data folder.

Posted: Thu Feb 08, 2007 2:10 am

Not sure if this has been mentioned anywhere - files created with #FILE are still created in the install directory rather than the data directory.

#file 6 test.test
#write 6 {this is a test} 1

was the code I used to test.

Also, %filesize doesn't report easy-to-understand line numbers for structured files - is there any other way to return the number of records in a structured file? I ask because this is a very useful way to import and export scripts that's also scriptable itself, but without a way for the script that's importing the file to know its size, it might miss information or try to read records that don't exist.

Posted: Thu Feb 08, 2007 6:10 pm

Thanks for catching this bug. I've added it to the bug list. And no, for structured files there is no way for CMUD to know what the record size is, so all it can do is return the filesize in bytes.

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

I am gonna expand on this a bit recently installed cmud on my desktop using the mydocuments/mygames setting and the logs were correctly going into the mygames/cmud/mudfolder/logs folder using #LOG mudfolder/logs/logname.txt after a few restarts log files were not getting created but if I were to put a mudfolder/logs folder in the cmud program files folder it would work correctly, somewhere along the way it got changed, same thing happens with saved files from the editor etc

Posted: Mon Feb 12, 2007 6:35 pm

It might be creating files in the "current working directory". Right-click your CMUD icon and go to Properties and see what the working directory is set to and see if changing that to the mygames/cmud directory causes this to start working.

It's possible that there are some areas in CMUD that just open the exact filename that you specified, and in the above cases, you are using a relative path, so Windows would make that relative to the current working directory.