Thread

SDK 37: Botgram event (Sdk)

SDK 37: Botgram event // Sdk

1  |  

xelag

Apr 11, 2004, 10:21am
I miss one important thing in this event: AW_BOTGRAM_FROM_SESSION.
This is the one attribute that could help pinpoint the sender
accurately, but it does not exist :(

xelag

Apr 11, 2004, 10:24am
Similarly for the USERLIST: a session number (=0 maybe if not logged
in) would be excellent.

[View Quote] >I miss one important thing in this event: AW_BOTGRAM_FROM_SESSION.
>This is the one attribute that could help pinpoint the sender
>accurately, but it does not exist :(

ep0ch

Apr 11, 2004, 7:12pm
Ah well, AW never thinks things through, much like my previous lawyer.

-Ep0ch

[View Quote]

strike rapier

Apr 11, 2004, 8:00pm
It was never intended to exist...

Botgrams were origionally designed to invite a user to enter the universe at
another persons location, without them needing to have AW open to recieve
it, only the bot invite.exe. This feature was intended for a different
universe.

The general idea is to send from one citizenship to another, not from one
session to another.

While I agree that one to one session methods would be absolutly brilliant,
this is not what the feature was designed for.

- MR

[View Quote]

xelag

Apr 11, 2004, 10:48pm
You confuse me: botgrams go from one bot to other bots, they have
nothing to do (in the current practice) with invite, although maybe in
origin they come from the same thought... at least, that is the
current implementation in the SDK, as far as I can understand it.

Alex

On 11 Apr 2004 17:00:41 -0500, "strike rapier"
[View Quote] >It was never intended to exist...
>
>Botgrams were origionally designed to invite a user to enter the universe at
>another persons location, without them needing to have AW open to recieve
>it, only the bot invite.exe. This feature was intended for a different
>universe.
>
>The general idea is to send from one citizenship to another, not from one
>session to another.
>
>While I agree that one to one session methods would be absolutly brilliant,
>this is not what the feature was designed for.
>
>- MR
>
[View Quote]

strike rapier

Apr 11, 2004, 11:20pm
'Invite' as it first existed was a seperate application, 'invite.exe' which
was installed with the alpha browsers that I still have kicking about
somewhere. When you invited someone to join you who was not in-world the
universe server would send a botgram with a specific type (hence the type
id) to identify who sent it, and their coordinates. Hence allowing the user
to join them even if they did not have the browser open to recieve the join.

In alpha browsers you do not launch aworld.exe... you launch invite.exe...
which logs in then launches aworld.exe... if you get what i mean... uh....

- MR

[View Quote]

xelag

Apr 12, 2004, 1:02am
Thanks for the explanation, I was not invited or allowed to
participate in the alpha period. If you read the SDK notes, you will
see that the current bot SDK 27 specifies an ID of 0 for botgrams, and
from what I could experiment in DLP (not in AW, they have this
disabled), botgrams are from bot to bot... Invite is still available
in the browser, although I've never tested it.

Alex

On 11 Apr 2004 20:20:52 -0500, "strike rapier"
[View Quote] >'Invite' as it first existed was a seperate application, 'invite.exe' which
>was installed with the alpha browsers that I still have kicking about
>somewhere. When you invited someone to join you who was not in-world the
>universe server would send a botgram with a specific type (hence the type
>id) to identify who sent it, and their coordinates. Hence allowing the user
>to join them even if they did not have the browser open to recieve the join.
>
>In alpha browsers you do not launch aworld.exe... you launch invite.exe...
>which logs in then launches aworld.exe... if you get what i mean... uh....
>
>- MR
>
[View Quote]

xelag

Apr 12, 2004, 1:13am
Strike, AW has invite (from browser to browser) active, in the message
of the invite you receive (a standard message) it even mentions the
world you are invited to go to. Botgrams are disabled in aw, and the
botgram code only mentions citnum of the bot, and a telegram style
message (you dont have a message = telegram style) in invite. The
botgram message can be up to 1000 bytes long. So I think it's two
different things... but the devil knows, AW is not very informative
lately.

[View Quote] >Thanks for the explanation, I was not invited or allowed to
>participate in the alpha period. If you read the SDK notes, you will
>see that the current bot SDK 27 specifies an ID of 0 for botgrams, and
>from what I could experiment in DLP (not in AW, they have this
>disabled), botgrams are from bot to bot... Invite is still available
>in the browser, although I've never tested it.
>
>Alex
>
>On 11 Apr 2004 20:20:52 -0500, "strike rapier"
[View Quote]

strike rapier

Apr 12, 2004, 1:21am
Invite was later integrated directly into the browser as origionally
planned, however invite.exe still works to request you join people elsewhere
in the universe that requested the feature in the first place as far as i
know.

- MR

[View Quote]

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