Any text editor will do. Try vi or emacs.

You may be stuck, sorry.

(See above)

Try "propspot" from the Botbot.

Different palaces use different room numbers. Ziprand is designed for use at TPI's main palace. Other palaces would need a different list of room numbers.

It has a timer -- after firing it once, you must wait 120 seconds before firing it again. This was installed to keep people from being auto-killed for flooding.

You can always use a script to load macros, but it's beyond the capabilities of simple scripting to reprogram the function keys themselves.

See here.

Sadly, this is something of a holy grail for pserv script writers. There's just no way to send a message between rooms, except as ESP or a Wizard ~page message...

Well, some other time then :)

Perhaps the bot is just too bog, and those features (toward the end of the list) were simply ignored by your client? They do work in my own testing....

Use bulkhi2, which will let you change the initial greeting string: as in:
bhi So long

I recommend trying the BotBot first, and add only those scripts you can't find there. Then again, maybe you could just send me the scripts and perhaps I'll add them to the bot...

Actually, this user came from infi.net but I don't think he wants me to know that.

My guess: bot too big.

Maybe you should meet Rory Koster....

Are you sure you're installing the cyborg correctly? Does any part of it work, or are you still using the original default cyborg?

Try "blanket" with a black prop.

Sounds like something wrong with your browser? Too many windows open already, perhaps?

The macMIDI script is part of The BotBot. Spot GIFs use the standard GIF transparency scheme. I believe you're better-off if you turn interlacing off for spot GIFs...

To turn it off, type ";ap 0 0"

1. As they say in NYC, "back up yours!"
2. See here.

It'll cost you.

It sounds like a corrupted prop (.prp) file. You may have to revert to your last backup.

That's correct. "Jihad" uses allscray to perform its magic. The spank problem is more squirrelly. It appears that the palace software gets confused about who to unpin, depending upon what WHOTARGET is set to. The best workaround I've found is to say "spank" and then immediately unselect the victim.

Sounds like you were using the wrong CLUT, and are now experiencing contrast shifts. Try shifting the images to 24-bit (16 million colors) in PSP, then select Load Palette from the PSP Colors menu and apply your Palace color map. Then copy and paste into the Palace.

As a god or wiz, try ~clon or ~clone depending on the client version. As for script errors, the most-common cause of that is featuritis. Try a simpler script.

Look here for zombie information. You may also want to look here for related info on "allscray" and its kin.

See below. BTW, you shouldn't get upset simply because more than 6 hours have gone by, at night, on the weekend, before I leap up to respond...

Once again, it sounds like script-size overflow. Try a smaller script... are you sure you weren't in a cyborg-free zone? Did the characters "??" appear in the log?

Charming idea.

Ack! Yes, there was an ftp addressing problem, now repaired. One of these days I will have to add information on that animation stuff.

Mais bien sure. Whisper `mute at them. You won't hear another peep.

Did you try it alone? Maybe your cyborg is too big (the #1 problem).

Sounds like a script-free or paint-free room. Can you be more specific?

ROOM
	ID 90
	NAME "Nameroom"
	PICT "X.gif"
	PICTURE ID 1 NAME "Xa.gif" TRANSCOLOR 0 ENDPICTURE
	SPOT
		ID 1
		OUTLINE 108,259  405,260  407,368  105,362
		SCRIPT
ON SELECT {
    [ bla bla bla ] SETPROPS
  }
		ENDSCRIPT
		ENDSPOT
	SPOT
		ID 2 (a script of a light that turns on and off)
		OUTLINE 219,47  218,86  295,88  295,49
		PICTS 1,0,0 ENDPICTS
		SCRIPT
 ON ENTER

        { 120 ME SETALARM  }

        ON ALARM 

        { ME GETSPOTSTATE NOT ME SETSPOTSTATELOCAL

          120 ME SETALARM  }
		ENDSCRIPT
		ENDSPOT
	SPOT
		ID 3
		OUTLINE 0,0  91,0  91,22  0,22
		SCRIPT

The ON ENTER, ON OUTCHAT, ON INCHAT Scripts of the "Mosh"
}
		ENDSCRIPT
		ENDSPOT
	ENDROOM

There's a limit of 32 scheduled ALARM and ALARMEXEC events. "Mosh" uses ALARMEXEC, and your light script uses a fairly-rapid chain of ALARMs. My guess is the buffer was overrun and so the next-in-line spotstate change event was unable to be scheduled. This light script, while functional, is a bear to restart. Reducing the number of Mosh steps may solve your problem.

You were using it in a room that doesn't allow painting. Try another room.

; Large Iptscrae Block Here

;Cyborg Script Serial# 38080197142128
;Created by BotBot (support: natpix@natpix.com)

ON SIGNON {
;;	HUGE CYBORG FILE OMITTED HERE - X
}

;end of cyborg.ipt Ser# 38080197142128

Careful attention to the "defaults" group can give you all the original functionality, but yes, a botbot cyborg doesn't look like the default cyborg. It's built differently for some very real reasons, and in the humble opinion of this X, that's all to the good. Most of those reasons are described elsewhere around this site, particularly at The House o Bots.

ON INCHAT
{
   {
        116 GOTOROOM WHOTARGET "" CHATSTR =
   } CHATSTR "convict" == WHOCHAT WHOME == NOT AND 1 ISGUEST ==  NOT AND IF
}

CHATSTR ";convict" == WHOCHAT WHOME == 1 ISGUEST ==  NOT AND IF

the other problem occurs if i forget to select a person for whisper. what happens then is it sends everyone but me to the jail ( kinda like an allscray command i saw) . this obviously should not happen, and is too easily abuseable : ) The reason i don't go with a simple ISWIZARD is that i want this script available to any registered client . Hopefully you can help me... i know this unsolicited mail, and i don't mean to annoy, but i really need and experts help..... thanks in advance, john aka terminus p.s. feel free to tell me to piss off.....
john benjamin <terminus@islandnet.com>
Victoria, BC Canada - Fri, 07 Feb 97 at 16:41:26

In addition to ISWIZARD, did you try ISGUEST NOT?
Your iptscrae clause above is incorrectly built. Try

ON INCHAT {
    {
	"" CHATSTR =
	116 GOTOROOM
    } CHATSTR "convict" ==
	WHOCHAT WHONAME "^Guest" GREPSTR NOT AND	IF
}

...which will work better for some subtle reasons, such as the GOTOROOM halting the script before your CHATSTR line was even reached.

As I understand it, ratbot is partly a client plugin. The plugin development kit can be obtained from The Palace, Inc.

Ah, the old "global array" problem. You can't assign an array as a global variable, but fortunately you can assign the values to a string, and then assign that to a global. Use STRTOATOM to extract the values.

    myArrString GLOBAL
    [ 1 2 3 4 5 6 7 ] myLocalArray =
    ;
    ; to load myLocalArry array into a the string myArrString
    ;
    0 i =
    "[ "
    {
	myLocalArray i GET ITOA & " " &
    } { i myLocalArray LENGTH < } WHILE
    " ]" & myArrString =
    ;
    ; to get any value back out of this array....
    ;
    4 whichElement =
    myArrString STRTOATOM whichElement GET

that should do it for most simple arrays.

You can always replace your - X

See above - X

Because the props are accessed by name, and whatever the most-recent "Flower1" seen is, it's the one that the palace client will select from your .prp file (see the stupid palace tricks section for more info on .prp files).

Sounds like your cyborg is just too big. Try building it with a few features removed -- you can always come back and get them if they're really necessary.

Did you put in a string for the palace name? There's an entry for it near the bottom of the botbot checklist page.

Sad to say, this is a "botbot versus the client" bug. An old version of Botbot's "jihad" script could generate code that, while syntactically correct, caused parser errors in the palace client. It's now fixed. - X

Hit Ctrl+Q, a.k.a. "Paste Multiple Props." The menu item will appear when the satchel is open.

The technique changed in the 32-bit client. Is this what you're using? Hit Ctrl+Q, a.k.a. "Paste Multiple Props"

See here... Be forewarned that removing them from your cyborg will have ZERO effect on globals defined by server-side palace scripts the scripts that you describe when you talk about "insidious information." The only way to flush-out that sort of data is to select "Disconnect."

Blondie normally needs you to have props "Flower1"... through "Flower5" loaded somewhere in your .prp file. My guess is... you don't. Try running it with an explicit prop name. I'm surprised the Win client would actually complain, however. In the absence of correct props, the Mac client merely does nothing.

Sounds like your ap offsets are shooting off to outer Quazululu Land. A new version (as of botbot 38) will do more work trapping those cases. Try ;ap 0 0 to reset ap.

Your first two ideas require that iptscrae can access the file system, which it really can't. I suppose you could use Netscape via NETGOTO to list the sounds directory, but since the newer clients split things up according to palace name, that gets tricky; Iptscrae can't get at that information.

As for "setface" avs, that would require analysing both the botbot code itself (or more specifically, the parts that you had altered by hand...) plus reading and breaking-down the entire .prp file again, a file system request, and really beyond what iptscrae can do.

Selecting props by name in the satchel window, however... Yeah, I'd really like to see that feature in the Palace client too.

Use the god command `wizardsonly on when in that room.

Interesting idea, but it won't work. It's not only beyond the scope of what palace and its scripts can do, but even beyond what any remote-control system can do.

I'm not sure what you mean by "prop programming." If you shut down the server, the props themselves can be listed in great detail in the server data file. Unfortunately, what's not included are who dropped them or when. You can, however, make a room self-cleaning: I'll add a page to the house o houses explaining the simple technique.

Due to a subtle client (server?) bug, you have to unclick the spank victim before they are unspanked.

Then you ave chosen too many options, and have overloaded you client memory. Try a simpler cyborg.

Although there was nothing obviously wrong with the toggle function, it's now been streamlined and should work better. Also (and this was true before), you can say either "blahblah on" to turn "blahblah" on, or "blahblah" alone to simply flip from on to off or back.

See here...

A good example can be found in the default mansion script look at the animating sign in Harry's Bar.

Sounds like a job for ResEdit...

Hang can be used as either a cyborg or room-script OUTCHAT feature.

They're running in wizard mode

You are trying them in a room tagged "No Painting" by the server. Try another room...

Tell a Friend

Could be. Certainly has voided your warranty =)

Warning No User-Serviceable Parts Inside

Do they play normally via the web browser without refering to them through Palace?

The "Dress" command was a user submission to the botbot. Perhaps it was faulty, or perhaps I have somehow corrupted it when adding to the botbot. The address of the original author can be found right in the cyborg file. In the meantime, try the zombie mode "dz" script as a more flexible alternative.

Look here.

You need to use GREPSTR and GREPSUB instead. Use the "." wildcard character to count spaces... so to get the rightmost five characters from CHATSTR:

CHATSTR "(.....)$" GREPSTR "$1" GREPSUB

...to get the leftmost four characters:

CHATSTR "^(....)" GREPSTR "$1" GREPSUB

...to get six characters indexed three into the string:

CHATSTR "^...(......)" GREPSTR "$1" GREPSUB

Good luck!

Any botbot spoke string can have sounds added ")yes like this" -- just like any other spoken Palace line. I have no plans to stockpile sound files, there are some other sites around the Palace ring that do a fine job at that sort of thing.

There's no way to do that except as a user, a room spot GIF (like the animated neon sign in Harry's Bar), or perhaps someone running a script that dumped consecutive props and did some sort of room cleaning in sync. A clever user might use QuicKeys or a similar macro program like Tempo to grab and place the props.

It moves in timed steps to avoid getting killed for flooding. You can tweak the delay in the script - reducing it will make the action faster but smoother.

If you're trying this the way I think you might be trying it, I hope you have a few hundred years ready to exhaust the possibilities... If you do, you can change the point at which the server kills you for flooding. With the server down, open the server script (named mansionscript or pserver.dat etc depending upon the OS you use) and look for the MINFLOODEVENTS line. The default is usually this:
MINFLOODEVENTS 200
just increase that value to 20000 or whatever and restart.

There was a bug that lasted for about 10 hours; it's now fixed. Thanks for the headsup!

The Love Shack is at port 9996 on the same server as House o Bots (jitter.rahul.net). The default port, 9998, is occupied by our very own Unpalace

Back to...
Book Entries for 1996
The House

(Adapted from an original guestbook script by Matt Wright, courtesy of Matt's Script Archive)