1  |   Order by index

Feb 7, 2005, 10:29pm

Hi all,

I have for the last few weeks been playing about with botgrams, and I have
added extensive use of them in Evolution, however to avoid these messages
interfearing with other human-readable botgrams I have come up with the
following:

\BG-COMMAND#[command type]

This means that the message is for internal use, and should not be displayed
to the user directly to avoid filling up their main windows. The command
type is given after the #, already implimented are:

HREQ - Hail Request
HRESP - Hail Response
BRD - Broadcast
EWRN - Ejection Notice

The data is then given on a newline deliminated list, the \n char,

The second line of each message contains ses=<bots session number> and
tgt=<target session #>, ses is the sending bots session and target session
is that bot which should handle it (if known individually, -1 on session or
tgt represents all bots).

Standard Hail:

\BG-COMMAND#HREQ
ses={aw_session()}
tgt=-1
wld={world name}
ver={Bots Version}

This requests that all citizens it are sent to respond using their own
details, here is the response from Evo when responding to Matt888

\BG-COMMAND#HRESP
src=62742
tgt=61119
wld=awteen
ver=Eclipse Evolution 71, SDK 39

HRESP is called in response to HREQ, other info can be contained in them on
a new line, the only difference is one is HRESP and one is HREQ to avoid
infinte ping-pong.

Because of the nature of these, it would be beneficial if bot designers who
display botgrams filtered (or handled) these messages appropriatly so they
are not displayed to the user filling their bot display screens.

I will put extra specs on http://zetech.swehli.com by friday hopefully, feel
free to impliment any messages you wish to use. Ideally we need the botgram
type variable to seperate the bot-bot messages, but we don't have it, so
this will have to do.

- Mark R

1  |   Order by index