Thread

Botgram Type (Sdk)

Botgram Type // Sdk

1  |  

strike rapier

Aug 7, 2004, 8:33pm
Good whatever-it-is,

It seems that we are lacking a major portion of the botgram functionality
with the botgram type attribute. I am wondering if we could somehow create
our own version of it by thinking up some kind of protocol or header for
each message so that we know what is what, something that takes as little
space as possible out of the 512 chars?

The reason I ask is I intend to be sending a lot of information through
botgrams, of course if every other bot recives every message screens are
going to very rapidly will get flooded compared to some of the messages
which users will wish to read etc.

Now considering we are lacking the type attribute, it seems sensable to use
several bytes at the start of the message, presuming we don't go insane 2
logical bytes should be enough, so xxxx as hex maximum? That way we can have
different 'types' for different purposes allowing bots to deal with them
appropriatly...

For example if I wanted to send a message for the user to read in every bot.

0 - Display on all
1 - Display on bot with name
2 - Bot-Only Broadcast to all
3 - Bot-Only Broadcast to bot with name
4 - Status Requester
5 - Arrival Register
6 - Depart Register

So for example a general message to everyone could be:
"0#This is my message"

A message to a specific bot:
"0#[?Some Bot]#Hello this is my message"
Could be identified via name, session etc (if registered).

Bot-Only would be the same as above, but not direcly displayed to the
user...

Status requester would be this:
4#get#<session>
Responded to by bots as
4#return#<session>#Eclipse Nightwing 3.6.93#awteen#2750s 0w

Arrival Register would be much the same, but no request:
5#Eclipse Nightwing 3.6.93#<any other info>
This would be for CT's for example, so each bot has to log in.

Exit Register:
6#<session>

We could designate the rest of the 36,000 registers as we need them, someone
just needs to keep a tab on all of them.

I think its worth a try at least, so our bots don't get flooded by other
bots comm traffic.

- Mark R

strike rapier

Aug 7, 2004, 9:12pm
Of course if the Universe Server let us have access to the botgram type
attribute we could impliment any number of systems, for example we could
just put any comm traffic like this is channel 1. Keep channel 0 open for
normal bot traffic.

- MR

1  |  
Awportals.com is a privately held community resource website dedicated to Active Worlds.
Copyright (c) Mark Randall 2006 - 2024. All Rights Reserved.
Awportals.com   ·   ProLibraries Live   ·   Twitter   ·   LinkedIn