Forums Scripts & Popups Problem with ascii

I have made a small ascii word, which i want to echo when i join a channel, i don't know whether to use echo or put it in a file, the problem i have is that it contains (/) back slashes, so mIRC thinks it's a commands and gets messed up, how do i get around that? cheers.

mIRC should not treat it as a command unless the / is the first character on the line or follows a | and a space.

I'm calling my own alias as soon as i've joined the channel.
I tried it like this


and it doesn't work

| Unknown command
| Unknown command
| Unknown command
|___ Unknown command

the usual scenario

| is a command separator, normal that it should be interpreted as such when it's spaced out that way. also mirc strips consecutive spaces when you use them in commands

you can solve both of these problems by changing each space to a hardspace ($chr(160)), or if that's not feasible solution you can insert invisible characters (such as control codes) in between every consecutive space. there's also saturn's spaces.dll which would require a bit of a re-write, each line would need to be turned into $+() with $str($chr(32),N) inside etc.

Stick that into a text file and /play -e the file.

ah good call, although i'd go for /loadbuf -a as it resembles /echo's behavior of printing to the active window ;P

Everything is correct and present in the folder, IE: names.txt exists with the stuff inside
still i get * /play: cannot play to this window (line 12, script7.ini)
* /loadbuf: unable to open file 'C:\merk\names.txt' (line 12, script7.ini)

Show the commands you're using.

loadbuf -a $mircdir $+ names.txt

In this case you dont even need to include $mircdir. Its the default path.

loadbuf $mircdirnames.txt is valid

$mircdirANYTHING gets translated to C:\mirc'sdir\ANYTHING

you should use $scriptdir though, not $mircdir

$scriptdir is the directory the script file youre currently executing lives

$mircdir is the directory of mirc (or the user's appdata dir)

These are not always the same, specifically if you package/run a script and its loaded from C:\notmirc\somedirectory\yourscript.mrc because it would attempt to still load your packaged "names.txt" from mirc's home directory rather than "C:\notmirc\somedirectory" where it probably resides after unpackaging.

This isn't only a script distribution issue, but can affect you too, say, if you store your scripts inside a "scripts\" subdirectory in mirc, don't be surprised if you arent pointing to the right file anymore.

---------

bottom line: mIRC doesn't lie.. if it says the file does not exist, you're the one who's wrong -- double and triple check you're actually pointing to the right filename-- a change to $scriptdir might actually point it to the right place (but not necessarily)

type //echo -a $exists(C:\merk\names.txt)

If that's $false, it's definitely not there-- type /run C:\merk and go check for yourself..

/loadbuf -a $mircdirtesting.txt

* /loadbuf: unable to open 'C:\Troy\mIRC\$mircdirtesting.txt'

Edit: Ooops my mistake. Need to do //loadbuf from command line.

That's because you ran that from the command-line with only a single / at the start, so $mircdir wasn't evaluated.

Thanks dude.

It was $false
Strangely though, It was to do with Vista and those rascal roaming folders again lol cheers though much appreciated