Yeah, also
echo -a $file(c:\mircstats\Stats.ini) $nick $($+(%,questioncounter,$nick),2) $1-
About the $mircdir/$scriptdir debate.
I choose to not use $scriptdir because it is not stable. It can change. I do not use $mircdir because it doesn't support a file path with spaces. I receive errors like
"C:/Documents" no file (example, not exact error msg)
The script I am developing I have named SoulFly. So the main folder is named SoulFly_v1. In this folder is my mirc.exe file with it's neccesary .ini support files. Logs & Sounds folder is also in my SoulFly_v1 directory. My personal scripts neccesary files are in their own folder called SoulFly. SoulFly.mrc and SoulFly.ini are two files for example.
I was having issues with mdx and other dll's using $mircdir when people wanted to run the script from their desktop "C:Documents and Settings\USER\Desktop\" or from My Documents or Program Files. Now I point to the dll's like this:
Now users may put my script wherever they like and it works.
This is my personal experience and solution. Sorry to go off topic, I just wanted to be clear about errors I have found using $mircdir and $scriptdir and why I do not suggest using them.
