;fserve = fileserver ; Please read the instructions here. Load this to remotes. on 1:TEXT:!

TRIGGER*:*:/fserve $nick 6 C:\mirc\wavs\ ; --> --> --> CHANGE ----------------->"TRIGGER" to the actual word you want peo ple ; to type to access your fserve. The word "trigger" is just an example word. ; This one indicates a path of C:\mirc\wavs\ (the directory the person using you r fserve ; will be in when the fserve opens) because it would be dangerous to allow an fs erve ; to access your mirc folder, since people could request your .ini files (it is likely ; that you have a script line with your password(s) embedded into it.) Any path that ; does not contain files you do not wish to share is fine, but remember that any ; folders inside the directory you specify are also accessible through the fserv e. ; The number 6 indicates that someone in the fserve may get up to 6 files concur rently ; from the fserve. Change that number "6" if you like. on 1:SERVOPEN:/msg $nick Welcome to my fserve, $nick $+ , Enjoy! ; Alter this message, or add to, it if you like ; Then in dcc options, 3 things pertain to fserve: ; 1) a "time-out in seconds" (how long the fserve can be idle before it's autoclosed.) ; 2) "display fileserver warning" (if this is on, you need to approve ea. fser ve request.) ; 3) "Max no. of <fileservers>" (how many fserves that can be opened from your drive ; at the same time.) ; And finally, you'll want people to know you have an fserve and how to access i t. ; This ALIAS (or your own variation) can do that for you: alias /myfiles /say To access my fserve type: !TRIGGER ; ; ; ; --> --> --> change "TRIGGER" to the actual trigger word you specified in your remote event earlier. LadyWAVer, ladywaver@pipeline.com http://www.pipeline.com/~an_unusual_one/