1  ...  12  13  14  15  16  17  ...  36  |   Order by default

Mar 5, 2004, 9:34pm

Well, note that the scripting language does not allow to suppress
whispered commands from its owners, it does have statement to suppress
verbal commands from all using chat. This is simply to ensure that
the owner in some way retains control over the bot. In x1, you can
suppress or allow others to send certain commands to the bot (suppress
by checking 'bot | listening restricted"). But in the last resort,
the owners whispered verbal commands can not be suppressed.

Alex

On 5 Mar 2004 16:28:13 -0500, "mastergrey" <webmaster at greylight.com>
[View Quote] >
>That's what it was... I hadn't thought to block the verbal processor. The
>command to trigger the walk is "Follow Path" so when whispered the bot would
>dutifully attempt to follow person Path, who never seemed to be around. ;-)
>Meanwhile the script itself is executing flawlessly.
>
>Okay, that solves it. No more late night scripting!
>
>The rest has been sent via email as requested. If only it is so easily
>solved.......
>
[View Quote]

Mar 10, 2004, 6:52am

av99bot and the service bot allow any number of bots... but: they are
all in one and the same thread, so you can't put too many in the same
application, as they will fight with the aw.dll for breath and choke.
Set up a few folders with av99bot applications, with fewer bots per
application. I would limit it to 10 or 15 bots per application,
depending on how busy they are.

Alex

[View Quote] >is there a way to increase the bot limit for xelag? after 50 bots it makes
>the bots leave and reenter which in effect makes my greater bot say hi and
>bye way to many times.
>
>kloot
>

Mar 10, 2004, 7:04am

Or are you talking of a world full of bots and people? And one
greeter bot?

If you use xelagot as greeter, it should not repeat itself like that,
it keeps track of session numbers and only greets the same session
once... unles the session leaves and comes back after half an hour.

The problem is that bots and browsers have a perception limit of 50
nearest avatars (sessions), up to about 200m in 4 directions - except
for caretaker bots in global mode. That can not be changed... but as
I said, you can use the xelagot to restrict the number of times it
greets.

Alex

[View Quote] >is there a way to increase the bot limit for xelag? after 50 bots it makes
>the bots leave and reenter which in effect makes my greater bot say hi and
>bye way to many times.
>
>kloot
>

Mar 12, 2004, 1:05am

Is your greeter a xelagot? It should not be doing this. Please
contact me at xelag at 3dee.nl if you are using a xelagot as greeter bot.

[View Quote] >hey Alex, yes, i am talking about over 50+ ppl/bots..... it makes the
>application pretty much usless when this occurs and it sucks cause i enjoy
>using it.
>

Apr 5, 2004, 2:17pm

This version of Xelagot (x1, Av99bot and srvcXlgBot) is the first one
using the just released 3.5 SDK build 37 beta.

I have waited a long time to release it due to the fact that, for the
first time in AW's history, we were not provided with a beta SDK
until last friday, despite the fact that 3.5 has been in open beta
since december or january.

Besides adding a few of the new SDK features, I added lots of
enhancements to the Survey Manager and other user utilities. Please
read What's New for more details:

http://www.imatowns.com/xelagot/xlgwhatsnew.html

I hope you enjoy this version :)

Alex

Apr 5, 2004, 6:38pm

Your little toys are little jewels, what added up together make a
whole garden of jewels; my Xelagot is one jewel, multi-populating a
garden too :)

[View Quote] [View Quote]

Apr 5, 2004, 6:46pm

Keep wishing, you might get it at channuka :)

Alex

[View Quote] >Xelagant work Alex
>
>Hopefully the next mod can have the one lil thing I Emailed ya about too
>*grins*
>
>Karten
>
[View Quote]

Apr 5, 2004, 11:25pm

actually, x1 does that on your chat screen (and gives you the uni
build as a bonus) just before it gives you the world welcome message.
Also, as pointed out by Karten, at the world attributes screen (tab
varia). The server's version is not mentioned, as that is not
completely safe to determine. Between AW main versions there are
transision periods (betas and fixes) and so my bot does set internally
some equivalence (for 3.4 I have like 3 'stages') just for practical
purposes, like disabling or enabling options, but those are just more
or less blindly enlightened guesses :)

If you need that info using a xelagot script:
UniverseBuild %u
gives the build number of the universe server
WorldBuild %w
gives the build number of the world server
http://www.imatowns.com/xelagot/xlgasworldattributes.html

Alex

[View Quote] >Does anyone know of a bot or program that can determine a world server's
>version and build number *without* having to be a caretaker? Using the
>remote admin tool doesn't count as a solution. :)
>
>Builderz
>http://www.3dhost.net

Apr 11, 2004, 12:26pm

Happy Easter sunday!

The latest version of xelagots x1, av99bot and srvcxlgbot are now
available. Read the details at
http://www.imatowns.com/xelagot/xlgwhatsnew.html

Alex

Apr 12, 2004, 3:09am

There is a problem with the cell data limit:

1) the SDK pages do NOT mention a change there

2) testing now, I find that world build 57, which accepts a cell limit
of 5000 (go to av02 and check), the 531 browser does not show this,
although the new SDK does report it properly. World 64 is accepted ok
by the browser with a Mega cell limit (see Xelagon)

3) in older worlds, the SDK allows to set 5000, even if its not
allowed, and things go wrong at world and SDK reporting level

So I forgot nothing, it simply has not been properly implemented and
documented, even if the 531 browser has 5000 Mega. I will investigate
this further, thanks Ep0ch. Seems typical of what is happening lately
for the past 3 or 4 months with the beta: no proper info or updates.

Alex



On 11 Apr 2004 18:17:36 -0500, "ep0ch" <deltawolf at deltawolf.com>
[View Quote] >You forgot the Mega cell limit again, new in build 64 of the world server.
>Mega is 5000 bytes.
>
>-Ep0ch
>
[View Quote]

Apr 14, 2004, 10:37am

That is how the 3.4 AW browser behaves because it does not know Mega.
Use the 3.5 latest browser 531 in a world server 64 (world server 57
is included in the bot as having Mega by mistake, will be corrected in
a future version).

Alex

On 14 Apr 2004 00:14:22 -0500, "sweets" <stylecanin at hotmail.com>
[View Quote] >when I change the limit to Mega using the xelagot, I noticed when I checked
>by aw browser (still have 3.4) that it had switched from Huge to Normal and
>the building inspector still was screaming.. I changed it back to Huge and
>tried again through the bot and it again changed to Normal.. Is this Normal?
>LOL .....do I trust the Xela at Mega or AW at Normal?...
>sweets
>

Apr 14, 2004, 10:53pm

Sorry Sweets, if you don't know about numbers, just leave it at what
it was. The maximum setting you can use if you are blonde and things
don't work is Huge, Mega is not for blondes. Set it back to Huge in
either the browser or bot, and pay for the best :)

Alex

On 14 Apr 2004 17:02:03 -0500, "sweets" <stylecanin at hotmail.com>
[View Quote] >ok zeofax must tell you I read it and read it and still is chinese to
>me.....3.5 latest browser 531 in a world server 64 (world server 57
>LOL sorry folks but although I have run bots and world for many years I do
>not even recognize any of these numbers or have any idea what anyone is
>talking about (ok flame me for being dumb is ok LOL)
>Do I leave it on the AW browser as Huge? or do I change it to Mega using the
>bot then leave the aw browser at Normal when it is switched.....sorry but
>that is all I need to know without a batch of numbers.....
>sweets
>

Apr 14, 2004, 10:55pm

not:
and pay for the best
but:
and pray for the best
:)

[View Quote] >Sorry Sweets, if you don't know about numbers, just leave it at what
>it was. The maximum setting you can use if you are blonde and things
>don't work is Huge, Mega is not for blondes. Set it back to Huge in
>either the browser or bot, and pay for the best :)
>
>Alex
>
>On 14 Apr 2004 17:02:03 -0500, "sweets" <stylecanin at hotmail.com>
[View Quote]

Apr 12, 2004, 3:40am

Due to the lack of proper documentation on the ActiveWorlds SDK web
pages, and to the inconsequent functioning of the SDK build 37 and of
the browser build 531 regarding this matter on world builds earlier
than 63 or 64, the previous 2 versions of Xelagot lack the ability to
set the Cell Data Limit to Mega. This version attempts to fix this.

While writing this, I have not yet been able to update the xelagot web
pages: it is 6:30am and I've been investigating this problem all
night. But the links to download this version (x1, av99 and srvcxlg)
have been updated.

Alex
http://www.imatowns.com/xelagot/

Apr 15, 2004, 8:42pm

Sweets,

get rid of world server build 57. This was an early 3.5 beta world
server. Install the latest one (64 I think) which you can get at
http://www.activeworlds.com/products/download.asp
(make sure you get the 3.5 beta one). You can also get the latest 3.5
beta browser there. Never use a 3.4 browser in a 3.5 world if you are
caretaker, always get the latest one. In fact, match you browser and
world servers :)

Alex


On 15 Apr 2004 16:05:46 -0500, "sweets" <stylecanin at hotmail.com>
[View Quote] >now that I understood...thanks Alex....was confused because world server
>says at top build 57 and yet when look in the 'about' there it says build 13
>(and that was loaded 3 months ago)....I have 3.4 browser and my partner 3.5
>but see aw as build 498 (not sure what hers is) but by the bot says sdk
>build 37 and on bot browser says on entry is Activeworlds. build 51,
>Universe build 51.....none of these numbers seemed to match anything anyone
>was saying.....LOL can kind of see why I got confused. Thanks much for the
>help and the explanation. Makes a bit more sense now *groans
>sweets
>PS: did I ever tell you I hate computers?? LMAO.....PEACE : )
>

Apr 16, 2004, 10:27am

[View Quote] >
>KKhhmmm - sever build 57 is NOT a beta server! It fixed a serious world size problem and did not include any new features.
>
>Sorry,


it does include terrain_offset and water_under_terrain, which are the
two first 3.5 additions to the world attributes, so that qualifies for
me as beta. Maybe it's a combined 3.4 fix on an incipient 3.5 beta?

Alex

Apr 16, 2004, 10:53am

Andras, we are probably both half-right. It is offered by AW as a
non-beta world server on their page, but it has the first two 3.5
world attributes (even the 531 browser recognises that), and appeared
during the beta period in november 2003. At that time, I had not been
included in the alpha/beta group (was denied admittance), and when I
finally was admitted in december, had to update my knowledge of the
beta ng very fast - it took me a couple of weeks to do so. So there
is my confusion about the status, which is confusing anyway because it
is half way between 3.4 and 3.5 :)

Alex

>
>KKhhmmm - sever build 57 is NOT a beta server! It fixed a serious world size problem and did not include any new features.
>
>Sorry,

Apr 16, 2004, 6:27pm

[View Quote] [View Quote] I was talking about the use of beta attributes. World server 57 has
two beta attributes (in that sense I consider it beta). If one wishes
to use beta attributes, ditch 57 and move on to the latest beta. If
not, stick to 4.3 attributes. I may have phrased it wrong, but this
is what I mean.

You said 57 does not have new beta things: it does, and that makes it
confusing, it is a regular 4.3 world, and it is an early beta 3.5 :)

Alex

Apr 17, 2004, 12:56am

I have just sent an email to Andras explaining my position about this.
In short, but in other words:

World build 57, for 3.5 beta purposes, is an early 3.5 beta version,
because it includes the first two 3.5 beta world attributes
(contradicting Andras' assertion that no new elements were included).
Anyone wanting to use/experiment with 3.5 beta MUST DUMP THIS VERSION
AND USE THE LATEST ONE.

Funny enough, world build 57 is also the stable 3.4 world version.
Not my problem. I acknowledge Andras' role in encouriging AWI to fix a
bug in the world server, but it was up to AWI to decide which world
server would have the honour. It so happens it was a 3.5 early world
server :)

Alex

[View Quote] [View Quote]

Apr 18, 2004, 9:03am

On Saturday April 24th, Imatowns will have a downtime of several
hours. This will affect the Xelagot web pages. Please read:

http://www.imatowns.com/news.htm

Good luck, Ima, with the upgrade!

Alex

Apr 18, 2004, 6:08pm

See What's New:
http://www.imatowns.com/xelagot/xlgwhatsnew.html

Alex

Apr 24, 2004, 7:16pm

[View Quote] >Sorry if I can't make my statements clear - English is not my native language.

Magyar English or not, you're a good developer!

Boring Old Farts Unite!

Apr 24, 2004, 6:44pm

Since a few bot SDK builds, there is a problem for universe caretakers
if they set universe options using bots.

If the "Latest 2.2 Browser" value is different to the "Latest Browser"
value in the universe options, using a bot to change ANY universe
option (universe message, for example) will change the "Latest
Browser" and make it equal to the "Latest 2.2 Browser" value.

The worlkaround is to make both values the same in the universe
options, using a browser. Pull up "Latest 2.2 Browser" value to the
same value as "Latest Browser".

I have reported this to the AW developpers team. I'm CC-ing this
message to them too

Alex

Apr 27, 2004, 8:59am

Please see http://www.imatowns.com/xelagot/xlgwhatsnew.html for
details.

Alex

Apr 28, 2004, 12:25pm

This is the newest xelagot topic: Ghosts
http://www.imatowns.com/xelagot/xlgtopicghosts.html
It applies to all bots and browsers, so I make it generally available.

For particulars about xelagot, see What's New
http://www.imatowns.com/xelagot/xlgwhatsnew.html

Alex

Apr 28, 2004, 8:50pm

I'm glad Linux is getting some attention. But your reply does not
address the point I made :)

Alex

[View Quote] >Maybe I should spill the beans... But during some chat with Will (999),
>he mentioned a new linux world server that was a total rewrite of the
>first, including support for MySQL. I'm not sure about any of the
>details, or any estimated release date. He just said he had been working
>on rewriting the server and that it supported MySQL.
>
>-Jeremy
>
>
>
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>Jeremy Booker - Owner / Webmaster
>JTech Web Systems
>www.JTechWebSystems.com
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>"Therefore do not worry about tomorrow, for tomorrow will worry about
>itself. Each day has enough trouble of its own." -Mathew 5:34
>
>
>
>
[View Quote]

Apr 29, 2004, 8:21am

A rather rude reply, jerme.

It was the wrong thread, that's all. Linux is a separate problem,
there's a lot written here about it and it deserves its own thread :)

Alex

[View Quote] >dude... ease up a little... take a step down off the pedestal.
>
>I had relevant information about the server...
>
>It's being rewritten. Maybe they'll fix your ghost bug in the rewrite??
>
>-J
>
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>Jeremy Booker - Owner / Webmaster
>JTech Web Systems
>www.JTechWebSystems.com
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>"Therefore do not worry about tomorrow, for tomorrow will worry about
>itself. Each day has enough trouble of its own." -Mathew 5:34
>
>
>
>
[View Quote]

Apr 30, 2004, 1:58am

I did not chose to leave them out of my report, I mention bots
explicitely. Bots do not log in with a citizen number, they actually
log in with citizen privs. If you check world logs, you will see the
following when an entity logs in:

for tourists, a cit 0 and privs 0
for cits, a cit x and a priv y
for bots, a cit 0 and privs x

notice also that bots log in with the priv password.

In the SDK events, because AW did not at first mention privs, avatar
adds events for bots use the cit field for its privs, and of course so
do the bot user interfaces. It is inconsequent, but presents no
problems, as one can distinguish a cit from a bot by its name (the
famous [...] thingies)

I tried to keep it readable in the pages... for technical and
especially non-technical people. If you have a suggestion on how I
can rephrase it, welcome: xelag at 3dee.nl

Alex

On 29 Apr 2004 22:28:29 -0400, "tony m"
[View Quote] >I'm not sure if you thought of it before, but bots are the only other entity which can be represented by your citizen number concurrently while you're logged in. So your second case does not consider any existing bots the citizen may be running in that world.
>
>Just a thought -- maybe you do know about it, but chose to leave it out of your report.
>
[View Quote]

Apr 30, 2004, 2:12am

On 29 Apr 2004 20:23:38 -0400, "ep0ch" <deltawolf at deltawolf.com>
[View Quote] >Thanks Alex, I will work on adding a "ghost checking" system to my bot.
>Shouldn't take more than 5 minutes with the information you've provided.
>
>Cheers,
>Ep0ch

Oh it will... the fact is, unless this is solved at world server
level, we will not get a watertight solution. If you start analising
the case, you will see a few problems:

case 1: how do you distinguish the live from the ghost? how do you
make sure that when you get an avatar delete, you delete the ghost and
not the live (if both are present)? In fact, you need to have a
counter, counting up and down the number of adds and deletes per
session number... In these cases, the SDK also gets confused, and chat
does not propagate.

case 2 and 3: which session number is valid? the last one received,
or the previous one? Bots are mobile, and entities can come in and
out of reach. Since for the world server, both the ghost and the live
are real, you can get avatar add and avatar delete for both session
numbers.

Bots in global mode should be able to solve these problems easier, but
it's not a 5 minutes work, I've been at it for months :)

Alex

Apr 30, 2004, 2:36am

What I forgot to mention is that, in the very begining of the SDK, we
did not even get the citizen number in the avatar add and delete event
(and no privs of course) so you could not even know who owned a bot.
And you could not even know what citnum XelaG or E N Z O had, except
by querying the universe server for the citnum of a name.

This was for me the reason to introduce the xelagot greet. At least
xelagots could identify themselves and their owners to other xelagots.

It took a while for AW to realise the cit was important. Botmakers
from the start pointed out to AW that cit, privs and IP (for bots with
eject rights) should be sent to bots directly with the events
concerning entities entering a world... after a while, first cit and
then much later privs were added, IP is still a matter of querying the
world server. Seems that what AW itself does not need for its own
projects is of no concern: no vision in this sense, and certainly they
do not consult other programmers who do have some sort of experience
about all this.

Alex

[View Quote] >I did not chose to leave them out of my report, I mention bots
>explicitely. Bots do not log in with a citizen number, they actually
>log in with citizen privs. If you check world logs, you will see the
>following when an entity logs in:
>
>for tourists, a cit 0 and privs 0
>for cits, a cit x and a priv y
>for bots, a cit 0 and privs x
>
>notice also that bots log in with the priv password.
>
>In the SDK events, because AW did not at first mention privs, avatar
>adds events for bots use the cit field for its privs, and of course so
>do the bot user interfaces. It is inconsequent, but presents no
>problems, as one can distinguish a cit from a bot by its name (the
>famous [...] thingies)
>
>I tried to keep it readable in the pages... for technical and
>especially non-technical people. If you have a suggestion on how I
>can rephrase it, welcome: xelag at 3dee.nl
>
>Alex
>
>On 29 Apr 2004 22:28:29 -0400, "tony m"
[View Quote]

1  ...  12  13  14  15  16  17  ...  36  |   Order by default