Magsbot Class, Session 3
Saturday March 11, 2006 6pm VRT
Guri Lady: Hello :)
PeLican: Hello
Magine: hi all
Guri Lady: Hello, Magine :)
Guri Lady: Hello, Pel
PeLican: hiMagine
PeLican: hey GL
Guri Lady: Hey hehe
Guri Lady: twins lol
PeLican: erm
Guri Lady: grrr my firewall is mad
Guri Lady: I dcan't log in the bot right now
PeLican: isnt that it in front ofyou?
Magine: what's it saying?
Guri Lady: oh it's blocking an intrusion so it's not
letting anything log in LOL
Guri Lady: I have errors for aw too.. not dling
Guri Lady: kk Ive got the bot on now
Guri Lady: gonna grab coffee brb don't wait for me :)
Magine: hm, looks like only 3 students here today?
Magine: unless everyone just sent bots, heheh
PeLican: hehe
Magine: i wonder if people lost interest after last
time...maybe i should pass out teacher evaluation forms :D
Guri Lady: back
PeLican: our a whip
PeLican: or
PeLican: not our
Guri Lady: nah their loss hehe
PeLican: it seemed like they were all gun-ho
Guri Lady: I grammed Brina
Guri Lady: she told me she was coming last time lol
Magine: maybe they just forgot...the weather is
getting nicer..(wow i just noticed, 60 degrees here)
PeLican: same here
PeLican: oh thats right,i live next door to you
Guri Lady: nicer?
[Jarvis]: I am here
Guri Lady: it snowed in San Jose ca lol
Magine: well nicer some places then
Guri Lady: we been having hail about 3 x's a day LOL
Guri Lady: it's weird hehe
Keshi: hello all
Magine: wow
Magine: hi keshi
PeLican: hi keshi
Guri Lady: hello, Keshi
Keshi: Smiles is hot here
PeLican: hehe
Magine: well, any questions from last time?
Keshi: not that i can think of
Guri Lady: ditto
PeLican: nope
Guri Lady: yay I found one person for the class lol
Magine: so you all understand about surveying and all
those lists :D
Guri Lady: mostly
Jesse K: hello
Magine: hello jesse
PeLican: did i miss a class last week?
Guri Lady: Hiyas, Jesse :)
Jesse K: hi Magine and Guri Lady
Jesse K: How's it going?
Magine: (to PeLican) if you weren't here last
saturday at this time, then yes :D
Guri Lady: Good :)
PeLican: thanks , that helps
PeLican: :)
Magine: originally the last session was supposed to
cover using the predefined buttons,and surveying and lists...quite a
bit, and we didn't get to all of it
Magine: so i split up that session into two
parts...so we can continue with those topics this week
Magine: let's go backwards a bit, to talk about the
buttons some more, since i skipped past some of that last time
Guri Lady: Okay :)
Magine: something simple...the buttons on the
movement tab
Magine: i guess they are mostly self-evident
however....
PeLican: ok
Magine: you can set bookmarks or markers for the bot
to return to later
Magine: the different is, bookmarks include the world
name and markers don't
Magine: to set a bookmark at the bot's location, just
click "Set Bookmark from Bot"
Magine: or to set the bookmark at someone else's
location,click "Set Bookmark from Target" and then choose the person
from the list of nearby people that appears
Magine: if you're in a world where you have CT privs,
you can also forceably teleport or warp other people around
Magine: the interesing thing you can do is to define
a path for the bot to move in
Magine: let's make a simple path or "position list"
for our bots to follow
PeLican: k
Guri Lady: :)
Magine: first move your own av to the place that you
want the bot to start from
Magine: the, assuming you've already given yourself
controller status with your bot,
Magine: you can say /newpos
Magine: oops
Magine: say /newpos and the name you want to give the
list, actually
Magine: like /newpos path1
Magine: /newpos path1
[Mags]: List path1 created.
[Mags]: Set position 1 of path1 to
16647,-773642,0,-469
PeLican: /newpos path2
Magine: your bot should whisper the coords to you
PeLican: /newpos path2
Keshi: /newpos p1
Magine: then move to the second spot, and just say
/newpos (you don't need to say the list name except when starting)
Magine: /newpos
[Mags]: Set position 2 of path1 to
17377,-774355,0,-431
Guri Lady: /newpos path1
Magine: /newpos
[Mags]: Set position 3 of path1 to
17266,-775111,0,-578
PeLican: /newpos
PeLican: /newpos
Magine: /newpos
[Gardener]: List path1 created.
[Gardener]: Set position 1 of path1 to
16647,-773642,0,-469
[Gardener]: Set position 2 of path1 to
16647,-773642,0,-469
[Mags]: Set position 4 of path1 to 18775,-776496,0,749
Guri Lady: /newpos
[Gardener]: Set position 3 of path1 to
17377,-774355,0,-431
[Gardener]: Set position 4 of path1 to
17377,-774355,0,-431
Keshi: /newpos
[Gardener]: Set position 5 of path1 to
17266,-775111,0,-578
Magine: /newpos
PeLican: /newpos
[Gardener]: Set position 6 of path1 to
17266,-775111,0,-578
[Mags]: Set position 5 of path1 to
19223,-775238,0,1466
PeLican: /newpos
Magine: /newpos
Keshi: /newpos
Guri Lady: /newpos
[Mags]: Set position 6 of path1 to
17726,-774520,0,1553
PeLican: /newpos
Magine: your path should end up near where it began
Guri Lady: /newpos
Magine: /newpos
[Gardener]: Set position 7 of path1 to
17480,-774311,0,1396
[Mags]: Set position 7 of path1 to
16672,-773626,0,2995
[Gardener]: Set position 8 of path1 to
17480,-774311,0,1396
[Gardener]: Set position 9 of path1 to
16672,-773626,0,2995
[Gardener]: Set position 10 of path1 to
16672,-773626,0,2995
Guri Lady: /newpos
[Gardener]: Set position 11 of path1 to
16672,-773626,0,2995
[Gardener]: Set position 12 of path1 to
16672,-773626,0,2995
[Gardener]: Set position 13 of path1 to
16672,-773626,0,2995
[Gardener]: Set position 14 of path1 to
16672,-773626,0,2995
PeLican: /newpos
Guri Lady: /newpos
Keshi: /newpos
PeLican: /newpos
PeLican: /newpos
Keshi: /newpos
PeLican: /newpos
Guri Lady: /newpos
Guri Lady: /newpos
Keshi: /newpos
PeLican: /newpos
Magine: besides the chat command, you could use the
"Set Postion..." buttons for the same purpose
Guri Lady: /newpos
Keshi: /new pos
Keshi: /newpos
Keshi: /newpos
Magine: once you've finished, click ctrl-F3 to see
the list in memory
Keshi: /newpos
Magine: all position lists are actually named RM_n
where "n" is a number
Magine: but you can refer to them by name because the
list names are stored in the $RM list, which can also see there
Magine: that is, $RM:1 will contain the name of your
list, and $RM_1... will contain the actual coords
PeLican: k
Magine: you can also click "show position lists" to
see the lists you have defined
Magine: and you can clcik "SavePosList" to save the
list to a file
Magine: and reload it from the file using
"LoadPosList" later
Magine: now, to have the bot move along the path you
defined, click "Patrol" and choose the name of the list you made when
asked.
Magine: for the time, just use the default...
Magine: the time is the time in seconds that the bot
will pause at each spot in the list
Guri Lady: hehe kewl
Guri Lady: Hajus like flowers lol
Keshi: hmm
PeLican: ok, Opie is freaking
Keshi: Jarvis is doing no thign
PeLican: ahh.cause he is still following me
Magine: if you in a world that has terrain, the bot
will also follow the terrain, if you first load the terrain data in,
using the "load terrain buffers" button on the Terrain tab
Guri Lady: Hajus is picking flowers for me :D
Guri Lady: Oo that's what I want to learn.. terrain
features w/ the bot.. IE shaving them etc etc
Guri Lady: There he goes again LOL
Guri Lady: Too funny
Magine: i kind of need to work on saving terrain to a
standard elevdump file actually...
Guri Lady: This is awesome, Magine
Magine: right now magsbot uses its own format for
terrain...
[Jarvis]: I am back
Guri Lady: Welcome back
PeLican: wb
Guri Lady: you rock :)
Magine: as you can see, with Patrol movement the bot
moves from one spot to the next
Magine: but you can instead have it move randomly
between any of the positions in the list, using the Random Movement
button (but click Patrol-Stop first)
Guri Lady: kewl
Keshi: /newpos p1
Keshi: /newpos
Keshi: /newpos
Keshi: /newpos
Keshi: /newpos
Keshi: /newpos
Guri Lady: /newpos path2
Keshi: /newpos
Guri Lady: /newpos
Guri Lady: /newpos
Guri Lady: /newpos
Magine: if you want to edit the position list, you
can also specify which other positions are valid for the bot to move
to, from each particular position
Guri Lady: /listens
Magine: and you can specify a different time to pause
for each position
Keshi: hmm he wont patrol oh
well i will practice
PeLican: nice
Guri Lady: very
[Maggy]: ahem
Magine: if you want to change the time that the bot
waits at each position, you would edit the position list and add the
pause time to the coords,separating them with a semicolon
Magine: for example the first position in my list is
16647,-773642,0,-469
Magine: if i wanted my bot to pause there for 15
seconds, i could change that to 16647,-773642,0,-469;15
Guri Lady: kewl
Magine: another thing you can specify is which
positions the bot can move to from each position
PeLican: cool
Magine: for example, suppose you had defined 4
positions forming a square
Magine: and you want the bot to randomly move from
point to point,
[Jarvis]: .
Magine: but NOT across the center of the square
Magine: in that case you could for each point,
add the numbers of the other positions that it was ok for the bot to
move to
Magine: so from position 1, for example, for the
square, you could say that the bot can move only to points 2 or 4, but
not 3 because that would take it across the center of the square
Magine: so you could change the position data to
16647,-773642,0,-469;15;1,4
Magine: the 1,4 on the end of that are the points
Guri Lady: kewl
Magine: if you want to take the time and effort, you
could define a whole network of positions that the bot would move
between, carefully avoiding passing thru objects because of the points
you defined as being okay to move to
Magine: if that makes sense :D
PeLican: yes, it does
Guri Lady: Yea.. that sounds awesome! hehe
PeLican: maze solving
Guri Lady: Ooh yea that be fun
Magine: another handy thing the bot can do, is if you
have done a survey to a list in memory, the bot can warp you to
an object you pick (if the bot has CT privs)
Magine: or if you're in a public world, you could at
leave have the bot run to the spot where the object is
Magine: *at least
PeLican: brb
Guri Lady: kewl
Guri Lady: I hate when I lose an object hehe
Magine: btw when getting the bot to come to you, if
you say /come it will stand in front of you, but if you say /here it
will stand at the same spot you are
Magine: /come
[Maggy]: Be right there.
[Gardener]: Be right there.
Magine: /here
Guri Lady: /come
Guri Lady: /here
Magine: oops, lol, my gardener bot that i keep here,
heard me too
Guri Lady: LOL!
Magine: when you use the slash commands, any bot that
you are controlling will respond
Magine: if you want just one bot to respond, use its
name instead
Magine: i'll move gardener back to the tower that way
Magine: hm, looks like she beat me to it
Guri Lady: lol
Magine: i forgot, i put a check in that script so
that she returns to her spot if she finds herself wandering
Guri Lady: oh kewl
PeLican: hehe
Magine: mags come
Magine: mags here
Magine: maggy here
Keshi: Jarvis come here
Guri Lady: Hajus like my perfume.... LOL
PeLican: 1Opie come
PeLican: Opie come
PeLican: works better withut the gibberish
Guri Lady: lol
PeLican: Opie here
Magine: hm, you know, i've found just the other day,
that avs don't really go down to ground level when you are standing on
the ground
Guri Lady: really?
Magine: at least their altitude as given by the SDK
doesn't reflect the correct height exactly
PeLican: just the short ones
PeLican: hehe
PeLican: yep
Guri Lady: hey not short av jokes
Guri Lady: *Is only 5' 2"*
Guri Lady: lol
PeLican: awwww (pats her head)
Sylsea: :-)
Magine: or maybe yeah, it's just the old avs are not
designed quite right
Guri Lady: *laughs*
Keshi: yes and sometimes causes
drop problems when done in relatative to the av
Guri Lady: That could be it, Magine
Guri Lady: Hello, Sylsea *hugs*
PeLican: hi sylsea
Magine: glad it's not something i did wrong anyway :P
Guri Lady: hehe
Magine: but when you are defining a position list on
terrain, you have to be aware of that fact
Guri Lady: you nah.. too smart :D
Guri Lady: kk thank you will check
Magine: it was causing me some trouble yesterday
Keshi: ground reference troubles have plagued aw
browser
Sylsea: Hi all :-)
Keshi: hiya
Magine: you see, the terrain-walking routine in the
standard magsbot script tried to determine when it's appropriate to
walk on the terrain, and when it isn't
Guri Lady: Glad ya here, Sylsea :) *hugs*
PeLican: i see
Magine: for example, if you want the bot to walk
across a bridge or up some stairs, or if it is underground, then you
would not want it to keep to the terrain height
Keshi: but if terrain does not load don't you
have a problem
Magine: if there is no terrain data loaded, then
magsbot will walk in a straight line between positions in the list
Keshi: ok
Magine: if one position is higher or lower, the bot
will walk on an invisible incline
Magine: but if terrain data is loaded, then it has to
figure when to follow the terrain and when not to
Magine: so what i finally arrived at, is to have the
bot "snap to" the terrain
Magine: that is, if both points that it is walking
between are near the terrain height at those points, then the bot will
follow the terrain height as it moves between the points,
Magine: even if there are hills or valleys
Guri Lady: kewl
Magine: but if the point at either end of the line it
is walking, is *not* near terrain height, then it will use the
invisible incline method
Magine: so if you wanted the bot to walk across a
bridge above the terrain,.
Magine: you would be sure that you defined points in
the position list that were on the bridge itself
PeLican: i see
Magine: anyway...the problem i was having, that i was
telling you about...
Magine: is that since the avs don't touch the ground
sometimes,
Magine: when i was creating the position list, even
though i thought my av was standing on the terrain,
Magine: it was actually above it a bit,
PeLican: ahhh
Magine: so when the bot later walked the path, it
didn't realize the point was supposed to be on the terrain,
Magine: so it used the wrong method, it used the
invisible incline instead of following the terrain
Magine: which made the bot seem to walk thru the
ground or in the air
Magine: anyway, i just discovered that problem last
night...
Magine: so if you've creating a position list in a
world with terrain, make sure your av is really touching the ground
Magine: when you want to create a point on the terrain
Sylsea: cool....ok
Guri Lady: Just in time to help us for class :D
Magine: (to [Maggy]) /cell
[Maggy]: You are in cell 16,-6 on page 0,-6
PeLican: ok
Magine: (to [Maggy]) /ht
Magine: you can ask your bot what terrain page and
cell you are at, btw
Magine: just say /cell
Magine: /cell
[Maggy]: You are in cell 16,-6 on page 0,-6
PeLican: /cell
Sylsea: nice
Magine: actually i thought it also had a /ht command,
which the rpgbot in awrpg does, but i guess i didn't copy that to the
standard bot yet
Guri Lady: /cell
Magine: however, we could add that right now if you
want
Magine: as an exercise :)
PeLican: ok
Guri Lady: okay
Keshi: /cell
Magine: oops, wait a sec, it needs a button too
Sylsea: can we make a button on our test tabs in
action from last week?
Magine: sure
Magine: hmm, not sure if the ht thing will work
though...there's no terrain here anyway
Guri Lady: /cell
PeLican: ok, skip it
Magine: so let me see...what would a simple thing be
to make a button for?
PeLican: say "Guri Lady is Goofy"
Guri Lady: ROTFL
Guri Lady: That's a given LOL
Magine: too simple:P
Sylsea: lo;
Guri Lady: see?
Guri Lady: LOL
Sylsea: lol
Magine: anyway, programming starts in the next
session, heheh
Guri Lady: awe.. hehehe
Sylsea: hehe ok
PeLican: k
Magine: did i tell you last time how to rebuild
something?
Guri Lady: Okay I better learn the basics before I
waste time trying to wonder why my programming is a mess LOL
Guri Lady: nope
Magine: let's do that
Sylsea: no, we got to survey and stopped
PeLican: you didnt tell me
Magine: did you understand about the different survey
formats?
Guri Lady: kewl
Guri Lady: ehh think so :)
Sylsea: at the time haha
Magine: you can survey to a list in memory (two
different kinds, actually) or to a file
Sylsea: right ok
Magine: in comma-delimited format, or the propdump
format that aw uses
PeLican: ok
Sylsea: ye
Magine: the nice thing about comma-delimited format
is that you can save the file, edit it in a text editor, load it back
in, and rebuild with the changes
Magine: you can't edit a regular propdump without
messing it up
PeLican: ok
Magine: does anyone know where there is some free
space here in aw?
Sylsea: as in not claimed by a cit?
Magine: right
PeLican: i should..lemme get my list
Sylsea: I have a field that we can use
Sylsea: I can clear the tiles
Sylsea: it's totally empty
Magine: if you don't mind, sylsea
Sylsea: sure hold on
Magine: clear the tiles?
Sylsea: grass floor objects
Sylsea: that I laid down to claim the area
Magine: oh if you have it covered, don't bother, i
have some land i can use
Sylsea: ok
Magine: i'll just use the place i have reserved ;)
Sylsea: wouldn't take long at all if you want, tho
Sylsea: ok
Magine: ok, first let's survey something to build
there
Magine: how about the fountain in back here?
Magine: everyone join me back here behind the tower
PeLican: opie come
Magine: this can also be a demonstation of how to use
magsbot zones
Guri Lady: kewl
Magine: maggy come
[Maggy]: Be right there.
Magine: now since i only want to survey the fountain
and not everything here,i'll define a zone around it, and then survey
only in the zone
PeLican: k
Magine: zones are rectagular and have to be aligned
on theworld grid...they can't be rotated diagonally relative to the
grid that is
Magine: so first i click F10 in the AWB to see
the grid
Magine: it looks like i'll have to take about 9 grid
squares here to get the whole fountain
PeLican: yep
Magine: so to define a zone, i wll go to each edge of
the rectangle i want to define, and use the SetZone buttons on the
Magsbot . tab
Magine: SetZoneE for here at the east edge...
Magine: i'll name the zone "fountain"
Magine: heheh you know, what am i thinking? the zone
has to be aligned, but it doesn't have to include whole grid squares
Magine: so actually i can make it a bit tighter
Magine: here for the north edge
Magine: here west
Magine: and finally south
Guri Lady: ehh what action tab we using?
Keshi: . tab
PeLican: i dont see it either
Keshi: i think
Guri Lady: oh yea.. thanks, Keshi
Magine: the SetZone buttons are on the "root" tab,
the one just named ","
PeLican: ahh
Magine: "."
PeLican: ty
Magine: after defining the edges, i need to activate
the zone
Magine: with SetZoneActive
Magine: hopefully you all have up-to-date
userdefs.udf files, because there's a macro in there that makes this a
bit easier,the @objinzone macro
Magine: now we do a local (3x3) survey, and for the
conditional expression, we put @objinzone[fountain]
Magine: we set Send to List for "Global List" and
Send to Behavior Table "off" since that isn't necessary for this
Magine: ok here goes (hope this works right, heheh)
Guri Lady thinks she messed up..
Guri Lady: lol
Magine: ok, let me check the object list that was
created, to see if it looks right
Magine: to check the result you click "object log" on
the Lists tab
Magine: or you could just press ctrl-F3 and look at
the whole global var list, but the Object Log button will jsut show you
what you want to see
Magine: and it does look ok...
Magine: so, now let me find that patch of open
ground...
Magine: brb
Magine: ok, join me there in a moment....
Immigration Officer: You are being joined by PeLican.
Magine: oops, i did a dumb thing already....
Magine: well, first things first...
Magine: to get your bots here, click AW coords on the
Location panel and enter these coords, then click Set on the
Location panel
Immigration Officer: You are being joined by Sylsea.
Magine: but i made a mistake that i have to correct
first.....can anyone guess what i did wrong, for extra credit? :D
Guri Lady: I didn't get any objects.. hope I didn't
mess up lol
Sylsea: start survey?
Guri Lady: LOL Sylsea
Keshi: set zone and didnot survey it
Sylsea: ;-)
Magine: no, i did the survey...but i forgot an
important setting
PeLican: translation?
Guri Lady: k then i messed up
Magine: yes that's it pelican
PeLican: woohoo..teacher's pet
Magine: i didn't use "relative to origin"
Guri Lady: heh Pel
Magine: so if i rebuild the fountain using that
survey, it will just duplicate the fountain in the same place
Sylsea: *claps*
Sylsea: ahhhhh
Sylsea: can we edit the survey?
Magine: i send maggy back to survey again, this time
with "relative to origin" set
Magine: ok, sylea, we can try that too for an added
touch :D
Sylsea: oh dear hehe
Guri Lady: I need to do it over.. I have no objects
LOL
Magine: uh oh, me either
Magine: lol
Magine: ah yes, a new bug to find each day
Sylsea: goodness knows what I have...
Magine: ok, i know what the problem is....
Magine: since the survey is now relative, the objects
don't appear to be in the zone
Magine: hm, problem for the teacher here...should
have testing this before class :D
Magine: well that's ok, there's a work-around
Magine: eh, but it involved arithmatic :P
Magine: *involves
Magine: let me see, let me see *thinking
Sylsea: yum...scrambles for scientific calculator..
PeLican: me good math
PeLican: 85^2 = 7225
Magine: we just have to figure the offset, to get the
fountain here
Magine: so we would subtract the original coords
first, to make the bot's location 0,
Magine: then add these coords back in when building
Magine: whew i hate this :P
Guri Lady: I dunno what I missed ...
RedWolf: sorry im late
Guri Lady: hello, RedWolf :)
Magine: guri...let me see if i can explain this better
Sylsea: hi RedWolf
Keshi: Hiya Red
Guri Lady: Okay thanks
Guri Lady: *hugs*
Magine: when we do the survey, the coords of the
objects are saved as part of the survey
PeLican: hi redwolf
RedWolf: MadDog come here
Magine: so rebuilding it will just create the
fountain at the same location
Magine: so, i then did a relative survey, that
adjusts the coords so that the bot appears to be a GZ
Magine: then we could rebuild the fountain here by
adding these coords in
Magine: but, sigh, since the coords are
adjusted in the relative survey, the @objinzone test won't work
Magine: because the zone is defined for the real
location of the fountain
Magine: so, okay, i went back a did a regular survey
again
Magine: but now when i rebuild i have to subtract the
orginal coords and add these new coords in
Magine: ok, so the bot did the survey at 23n 778e
Magine: so when i build, i will first subtract
-23000 from the NS coords and -778000 from the WE coords
Magine: but also add these coords -5619000 NS and
3889000 WE
Magine: i hope that makes some kind of sense...i
don't like it either, should be simpler :P
Magine: i need to make a relative zone-checking macro
to make this easier
Keshi: Magine you are saying that If you survey
relative to the bot you can then build relative to the bot
anywhere without much difficulty right?
Guri Lady: sure does.. after a few hits amd misses
I'm sure it will sink in LOL
Magine: but for now, let me try the manual arithmatic
Magine: keshi, yes that's right, the only problem
here was that fact that the bot couldn't detect the zone properly
when using a relative survey
Keshi: ok
Magine: if i had wanted to survey the whole area
instead of just the fountain, there would have been no problem
Magine: heheh maybe i should do that for a simpler
example :D
Magine: well let me try the math first, i want to see
it build the fountain here :P
Sylsea: this is good to know thogh
Magine: so, we use the Built tab
Guri Lady: ahh okay
Magine: and first click "Set relative mode"
Magine: then click "build from obj list"
Magine: use objlog for the list name (the survey
dialog always puts the results in a list with that name)
Magine: and definitely i want to put the build
results into a templog so i can delete it when i mess up----er, i mean,
when i want to tidy up :P
Magine: and use original builder id
Sylsea: hehe
Magine: but now here comes the darned math part
Magine: since i chose to build in relative mode, it
already chose the bots current coords for the offset
Magine: but i have to subtract the coords of the
original location
Magine: ah, oops, no that's wrong too :D i forgot to
move the bot here first :D
Magine: so start over
Magine: FIRSt move the bot here, lol
Magine: ok now do the build stuff
Guri Lady: :)
Magine: -5619000-23000=-5619000
PeLican: it does?
Magine: (current NS coord-original NS coord=NS offset)
Magine: pelican, it had better :D
Guri Lady: hehe
PeLican: -5642000
Magine: oh yeah, huh, bum calculator
Magine: or bum fingers
Guri Lady: Nah.. I took you battery for mine.
Guri Lady: Sorry
Guri Lady: *Gives it back to Magine*
RedWolf: lol
Guri Lady: lol
Keshi: mags can calculate ... right?
PeLican: she's just lookin tosee if we're payig
attention hehehe
Guri Lady: I bet she is hehe
Magine: then for 3889000-778000 i get 3111000 is that
right? :D
Keshi: built in calculator
PeLican: yes
Magine: that is the current WE coord - original WE
coord
Magine: ok, here goes, hope this works so i
don't look too silly
PeLican: but is the original coords positive or
negative?
PeLican: nvm
Magine: lol
PeLican: go for it
Magine: a ton of errors and "not allowed"
RedWolf: *watches*
Magine: did aw finally prohibit bot building?
PeLican: i wonder..thre was talk recently
Magine: i know it has been considered improper, but i
didn't know they made it impossible yet
RedWolf: why cant we build with the bot?
Magine: no, it let me add a red tree just now
Magine: no reason i think the teach just messed up
PeLican: ok..so u r building on someone's property
Magine: ok i know the problem
Magine: when buidling i should not have chose "use
original builder ID"
Guri Lady: Tis okay.. I'll proabbly be messing up and
I can learn now how to fix it hehe
Magine: because that made the bot use the OBJECTLOAD
function instead of OBJECTCREATE
Magine: and OBJECTLOAD will only work where you have
CT rights
Guri Lady: ahhh
Magine: so,,,,this time for sure,,,i'll try again
Magine: now what were those numbers? :D
Magine scrolls back
PeLican: bahaha
Guri Lady: hehe
PeLican: hehe
PeLican: the 2nd one was 3111000
PeLican: -5642000
PeLican: was the first
Magine: ohhh please work :P
PeLican: BOOM
Guri Lady: lol
Magine: hmmmm
Magine: i don't see a fountain
PeLican: nope
PeLican: MIA
Magine: ok, the heck with the arithmatic stuff, i'm
just going to build the whole darned gardens here
Magine: just to show you it can be done :D
Keshi: heehee
Guri Lady: hehee
PeLican: uhoh...we made her mad
PeLican: hehe
Magine: ok so i send the bot back, survey relative,
without the zone stuff
PeLican: k
Magine: i check the objlog, which i can see has
nice small numbers, showing that it was correctly surveyed relatively
Magine: now i bring the bot here
Guri Lady: that's the action / survey tab / then
survey relative mode button?
Keshi: darn Jarvis is really a mess
today wont come here
Magine: correct keshi
Keshi: no i mean he wont follow me
Magine: now build relative (crossing fingers)
Keshi: he locked up and would not patrol
Magine: ah ha
Guri Lady: using that button.. how does the bot know
how far to survey.. is that the set zone did eariler?
Magine: whew
Guri Lady: oh kewl
Magine: would have felt pretty dumb if it hadn't
worked that time
Magine: now it is pretty slow, because i put in a
delay factor, because i found that if you build too fast aw will choke
PeLican: woohooo
Guri Lady: Yay!!
RedWolf: whoa
Sylsea: *applauds* :-)
Guri Lady: *Claps*
Guri Lady: *pats Maggy bot's head*
Guri Lady: hehe
Keshi: giggles
PeLican: oh great...now we're gonna have to clean the
fountain
Magine: however you could if you feel lucky, edit the
[BuildObjLst] button and change the MBWAIT 100 at the bottom to some
smaller number
Guri Lady: LOL
RedWolf: lol
Magine: right now it waits 100 ms between building
each object
PeLican: i see
PeLican: oops sorry
Guri Lady: Nah I trust you.. LOL
Guri Lady: ?
Magine: you can tell when it's done, btw, by looking
at the button...it will stay down until the action is completed
PeLican: ok
Guri Lady: Did the bot use the zones we set eariler
to build using relative build button?
Magine: nope, guri, the zone thing had problems
Guri Lady: Okay
Magine: let me try to explain that better...
Magine: when you do a relative survey, magsbot
subtracts the bot's coords from the coords of every object surveyed
Guri Lady: so how does the botty know how far to
survey an area when you use the action / survey tab / then survey
relative mode button?
Magine: so the resulting survey will show objects
near the bot as if they were near GZ instead of at their real coords
Guri Lady: Okay
Magine: but the zone thing was set for the real
coords
Magine: so therefore, the entire survey was excluded
from the survey file, it all fell outside the zone,
Magine: so, i need to create some simple mechanism to
allow users to use zones for surveying relative mode
Keshi: yes please
Magine: probably i'll made a
@objinzone_relative macro
Guri Lady: thank you
Magine: that will adjust the zone coords
Magine: maybe we can test that next week, heheh
Guri Lady: :)
Magine: anyway the build finished
Sylsea: that would be cool
Keshi: :d
PeLican: cool
Keshi: :D
Magine: the flagstones are under the grass here
though, heheh
Guri Lady: hehe
Magine: but since i don't want to mess up my nice
pristine forest here, i will now delete this all using the templog
Magine: that was created when it was built
PeLican: k
Magine: so on the Build tab i use Delete obj list and
give templog for the list name
Magine: lol but once again there's a little problem
Magine: minor though
Magine: i have to turn off the relative building first
Magine: because the templog saves true coords
PeLican: so it wouldve deleted youroriginal?
Magine: no, it tried to delete things that arent there
PeLican: oh, right
Magine: it won't delete the original because the
original has different objectnumbers
PeLican: i see
Magine: but this points out something else you should
know...
Magine: to interrupt a loop or a button, you can
press F12
PeLican: oh ok..good to know
Magine: there it goes, poof
PeLican: good
Guri Lady: kewl
Magine: after pressing F12 to break from loops, you
should press Shift-F12 to reset though
PeLican: k
Magine: or else no loops will run
Sylsea: ok
Magine: lol i'm still going to be getting a lot
of error messages about those objects i tried to delete that weren't
there though
PeLican: hehe
Guri Lady: lol
PeLican: Im going afk for dinner...i'l leave my av
and bot here
Magine: well this was an interesting
session....though i might have discouraged you from using magsbot to
build :P
Guri Lady: hehe
PeLican: naaa....there's always littlebugs to workout
PeLican: and there's always a work arund
Guri Lady: Nah I may just go practice now lol
Magine: hopefully i will see you all again next
saturday, back at the gardens
PeLican: thanks Magine
Guri Lady: Yep I'll be there :)
Magine: and we can talk about some intro programming
concepts...
Guri Lady: Thank you, Magine *hugs*
PeLican: cool
PeLican: ok, Im out for dinner
Magine: have a nice rest-of-the-weekend everyone :)
Magine: bye