1  |   Order by index

Apr 24, 2004, 5:41pm

Hello Devteam,

I have noticed a serious problem for universe caretakers using the bot
SDK to set universe options. Not only in the latest beta build 37,
but earlier 3.4 and maybe 3.3 ones too. If uni caretakers use the AW
Browser, this problem does not occur.

The bot SDK reads and writes Latest Browser using the values of Latest
2.2 browser:

aw_int(AW_UNIVERSE_BROWSER_RELEASE) does not give me the value of the
Latest Browser, it gives me the value of the Latest 2.2 Browser.

Further, if I do aw_universe_attributes_change() without changing any
of the values of the Browser parameters, the universe server changes
the value of Latest Browser to match that of Latest 2.2 Browser. If
both values were originally the same, you do not notice the problem,
of course.

I think this problem is serious, because bots are being used to change
universe options, often only the world message... if they have
different values for Latest Browser and Latest 2.2 Browser, they will
be unknowingly changing the Latest Browser value.

As I said, this problem does not occur when you read or set options
using the browser.

Alex

Apr 25, 2004, 12:37pm

Hi again,

I did some more testing with the bot SDK, and I think I can pinpoint
where the error is.

When the aw.dll decodes the packet received from the universe server,
it makes a mistake, and assigns internally the value received for
"Latest 2.2 Browser" to "Latest Browser" (as well as assigning it to
the correct field). Therefore, when the bot retrieves
aw_int(AW_UNIVERSE_BROWSER_RELEASE), it gets the wrong value.

The encoding to send back universe attributes to the server works
correctly in this respect. The problem there is that because
internally the value of "Latest Browser" is wrong, it gets encoded
wrongly. If I change it using the bot, it gets sent correctly.

Hopes this gets fixed soon!

Cheers,
Alex



[View Quote] >Hello Devteam,
>
>I have noticed a serious problem for universe caretakers using the bot
>SDK to set universe options. Not only in the latest beta build 37,
>but earlier 3.4 and maybe 3.3 ones too. If uni caretakers use the AW
>Browser, this problem does not occur.
>
>The bot SDK reads and writes Latest Browser using the values of Latest
>2.2 browser:
>
>aw_int(AW_UNIVERSE_BROWSER_RELEASE) does not give me the value of the
>Latest Browser, it gives me the value of the Latest 2.2 Browser.
>
>Further, if I do aw_universe_attributes_change() without changing any
>of the values of the Browser parameters, the universe server changes
>the value of Latest Browser to match that of Latest 2.2 Browser. If
>both values were originally the same, you do not notice the problem,
>of course.
>
>I think this problem is serious, because bots are being used to change
>universe options, often only the world message... if they have
>different values for Latest Browser and Latest 2.2 Browser, they will
>be unknowingly changing the Latest Browser value.
>
>As I said, this problem does not occur when you read or set options
>using the browser.
>
>Alex

Apr 25, 2004, 5:46pm

This is a graphic of what is happening:

http://www.xs4all.nl/~xelag/sdk_uni_error.gif


Alex

Apr 25, 2004, 5:51pm

ohhhhh I like the graphical support :D

- MR

[View Quote]

1  |   Order by index