So I poked around in a few games, and I don't see that code in any of them but LSL3 (which is what Brian based the template game on I think?).
In LSL3, it looks like it's used in 2 places. I haven't played the game, but one is in room 355, in "Ken"'s office. In this case, a copy of the ego is drawn to the background (with AddViewToPic), and the ego "becomes" the chair that Ken was sitting on. It looks like they did this to save having to have an extra Act/Prop instance around maybe? That would be weird though, because I think the code to manage it would end up being larger than the extra data required for another Prop.
(case 17
proc65535_0(355 6)
proc000_15(gEgo) // This is the AddViewToPic call
(send gEgo:
view(355)
loop(3) // This is a picture of chair. The ego becomes the chair?
posn((aKen:x) (aKen:y))
setPri(5)
stopUpd()
)
proc000_2(aKen 3 352) // Ken switches to a walking view resource
(aKen:
illegalBits(0)
viewer(0)
posn(30 140)
setPri(3)
setMotion(MoveTo 30 132 self)
)
)
(case 18
(aKen:setMotion(MoveTo 40 128 self)) // and then walks over towards the ego
)
(case 19
proc65535_0(355 7 67 -1 144)
(aKen:setMotion(MoveTo 109 128 self))
)
(case 20
proc65535_0(355 8)
(send gRoom:newRoom(350))
)
The other usage of this function is in the opening scene where you see the beach get developed with real estate. It's used to make lots of copies of the little house on the volcano.
(instance aHouse of Prop
(properties
y 999
x 999
view 130
loop 9
)
)
and then:
var local2
var local3[42] = (158 73 172 73 185 73 197 73 205 65 192 65 178 65 166 65 151 66 140 59 150 59 160 59 171 59 184 59 196 59 189 51 180 51 171 51 162 51 153 51 999 999 )
(localproc_2226)
(aHouse:
setPri(1)
posn(local3[++local2] local3[++local2])
)
proc000_15(aHouse) // This is AddViewToPic
(if (== 999 local3[local2])
= local2 (- local2 2)
)
)
So it looks like as the room script continues on, it just adds another house at the next coordinate in the array.
