NewNet's #Services - Pirch Scripts

Here are some Events and Popups you may want to use. I have the event's spread out here and some duplicates (mostly because I'm not sure which one did actually work, so I have both in my events). The ones on two lines need to be on ONE line in events, and of course any directory name changed to match the directory you are using. Also make sure to enable events so these will work (lower right hand corner of events make sure there is a check in the box next to the word "events") and also the level you are putting these in, make sure that box has an X in there.

ON NOSOUND:*.*:*:/notice $nick !DCCSEND $filename

ON NOTICE:!DCCSEND*:*:/dcc send $nick c:\pirch\download\ $+ $2

ON DCCDONE:*.*:/notice $nick Thanks for $filename ...... rate was $rate

ON INCOMING:/playmedia c:\pirch\download\kiss.wav

PING:/display > nexcontrol \12 Pinged by \2 $nick \2 on $date at $time from $address \12 |/notice $nick next time, ask first please !! Those pings can hurt !!! :+

ON DCCDONE:*:/notice $nick Thank you for $filename at $rate CPS.

ON SOUND:*.*:#:/display > $host \-11 $nick played $filename | /display > # \-11 \-3 Sound: \-3 \-2 \-31 $filename played by $nick \-2 \-31

ON NOTIFY:/whois $nick

ON SOUND:*.wav:#:/display \-11 $filename played by $nick

ON TEXT:!hangman*:#:/runscript [hangman] play # $nick *2

ON TEXT:password:?:/invite $nick #channelname

ON CHAT:password:/invite $nick #channelname

TEXT:password:#:/invite $nick #channel

ON INVITE:#:/autoinvite $nick

ON JOIN:#services:/notice $nick Hi, welcome to NewNet's #services.

Popups: Channel [name list] & Private Msg/DCC Chat

Slam!:/me slams a frying pan on $$1 $+ 's head. That's gotta hurt... but then again... where there's no sense... there's no feeling!
Hugs:/me {{{{{{{{{{{{ $$1 }}}}}}}}}}}}
Slap:/me slaps $$1 with her..................well you figure it out :)

HUGS

.Fancyh:/me {з{з{з{з{з{з{з{з{ $$1 }з}з}з}з}з}з}з}з}
.Fancyh1:/me з{з{з{з{з{з{ $$1 }з}з}з}з}з}з
.Fancyh2:/me з{з{з{з{з{з{ $$1 }з}з}з}з}з}з
.hug1:/me з*з*з*з*з $$1 з*з*з*з*з
.hug2:/me ееееееееее $$1 ееееееееее
.hugall:{{{{{{{{{{ \-2 $1 $2 $3 $4 $5 $6 $7 $8 $9 \-2 }}}}}}}}}}
.Hug:/me {{{{{{{{{{{{{{{{{{{{{{{{{{{ $+ \-2 $$1 $+ \-2 }}}}}}}}}}}}}}}}}}}}}}}}}}}
.Hug3:/me {з{з{з{з{з{з{з{з{ $+ \-4 $$1 $+ \-4 }з}з}з}з}з}з}з}з}
.Hug4:/me {д{д{д{д{д{д{д{д{ $+ \-4 $$1 $+ \-4 }д}д}д}д}д}д}д}д}
.Hug5:/me {л{л{л{л{л{л{л{л{ $+ \-4 $$1 $+ \-4 }╗}╗}╗}╗}╗}╗}╗}╗}

Popups: Channel [Main Pane]

Chaninfo:/msg chanserv info #
Chanaccess:/msg chanserv access # list *
Nickinfo:/msg nickserv info $$1
ChanJoin:/msg chanserv join #
ChanOps:/msg chanserv ops #
Nickident:/msg nickserv identify (password)
Chanident:/msg chanserv identify # (password)

The NickServ and ChanServ ones work great if you have multiple nicks and channels, and you set them up with the same password.

HOW TO ADD PIL SCRIPTS TO PIRCH {PIHeart update 01/01/97}

{PIL = PIRCH Interpreted Language} PIL is really just another form of Scripts.

1. If PIL is zipped then unzip it. (Suggestion would be to unzip it into your Pirch directory).

2. Open the PIL (you can do that by hiliting the *.pil file and then 'RIGHT click on the mouse and click on OPEN in the dialog box OR double click on PIL icon in Explore) and read the instructions. Most PIL's instructions are located in the TOP part of the PIL itself. Some PIL's contain HELP files and as a rule you should check the files contained in the zipped program by looking in the WinZip progam window before unzipping.

a. You may be instructed to place the PIL file or other file(s) in a certain directory.
b. You may be instructed to change directories (for sounds or text or other files) in the PIL.
c. You may be instructed to place files into your events. If so you can copy and paste them.
d. You may be instructed to make an aliases to run the PIL. I have found that Popups work just as well but that is your choice.

3. Open your Aliases window by clicking on the Aliases button in the top toolbar of Pirch.

4. With the cursor in the 'LEFT' window (under Aliases) of your Aliases window 'RIGHT' click on the mouse. A menu will pop up.

5. Click on "Add PIL Script". A dialog box will popup. It may be defaulted to your PIRCH directory, which may be the best place to store your pils. The default value for the file type is Pil Script (*.pil) and a list of pils should appear.

6. Locate the Pil Script and click on OPEN. (or double click). Then hit "SAVE" on the Aliases window.

7. Scroll down to the bottom of the aliases name list and locate the pil [name] within brackets. The Pil script will appear in the command window. There are instructions located there [this will be the same as you saw in step #2 above and will give you a chance to review required actions.]

8. Now you can make an aliases or put into your POPUPS the /runscript command that is given in the PIL file.

As a rule I install a PIL and try it. If it does not work then I just do not attempt to use it until I can get help from the author. As a rule the OPS in #Pirch will not help you with a PIL. At this time most PIL are not provided by the Autor of Pirch therefore Pirch does not endorse any PIL scripts. In other words 'use at your own risk.'

Questions?

You are visitor #

since 7/17/97