What I would really like to see is this:

A new kind of object that is like scenery but has a window where you can add what rooms you want it to be in. That way I only have to make the "Sky" one time and just put it into every "room" that is outside.

You could have an area with several rooms with the same kind of carpet and only make it one time...that would be great.

You should do that Alex.

I'm planning something like this for Quest 5.0. It could be implemented now entirely in CoreScopes.aslx, as that defines what objects can be seen where.

We could either have a list property on a room that specifies which additional objects are in scope, or as you suggest, the object could have a list property on it that specifies which additional rooms it appears in (though that sounds like it would be slow, but maybe on initialisation we could just process all the lists and turn the latter into the former).

I thought of windows (and doors), too. I would suggest another solution. The problem of Dr.Froths window is, that you can only use it in one direction. If you have 2 room next to each other and want to use a window or a door in both directions, you have to use 2 objects, which must be coordinated (if you open a door from one side, it must be open from the other side, too).
So I thougt of new types of exits. Then you have one object, but you can use it in several rooms.

<object name="golden key">
<take/>
</object>

<object name="lounge">
<start/>
<prefix>the</prefix>
<exit alias="east" to="hall" id="door1"/>
<exit alias="east" to="hall" id="window1"/>
</object>

<object name="hall">
<prefix>the</prefix>
<exit alias="west" to="lounge" id="door1"/>
<exit alias="west" to="lounge" id="window1"/>
</object>

<object name="door1">
<inherit name="door"/>
</object>

<object name="window1">
<inherit name="window"/>
</object>

<type name="door">
<pass>true</pass>
<viewmode>none</viewmode>
<locked/>
<key name="golden key"/>
</type>

<type name="window">
<pass>false</pass>
<viewmode>large</viewmode>
</type>

viewmode =none -> you cant look through it
viewmode=large -> you can see the other room and all large objects in it (new property of an object)
viewmode=medium -> you can see the other room and all medium and large objects in it
viewmode=small-> you can see the other room and all objects in it

I would prefer to do it in a similar way to containers. Currently in Q5, if you have a transparent object in a room, you can see all objects contained within it in the parent room.

Now, a room is just an object in Q5 anyway, so you can nest rooms inside rooms.

Inside a parent "room", you could put a transparent "kitchen" room and a transparent "garden" room. Then in the kitchen you can see objects in the garden, and vice versa. But if you're in the kitchen, then objects in the garden are not within ScopeReachable, so you can only see them, not take them.

So this is already possible in Q5. But it's not massively elegant at the moment, as you still need a non-transparent meta-room to contain both the kitchen and the garden. Also the garden appears as a viewable object inside the kitchen, which is OK in this particular case but I imagine sometimes you don't actually want the "other" room to be visible as an object itself.

Uhh, I ve problems to get this Ok, this could solve the problem with windows. If you are in the "kitchen", you would see "garden" in the list of objects and you can call "look garden". But I think I wouldn't use this. It feels as if there is no wall between kitchen and garden. I would like to have a window in the kitchen and if I "look window" I want to see the garden. And I want to "open window" and "climb window" to get into the garden.

What about three rooms? kitchen can see garden and lobby, garden can see kitchen, lobby can see kitchen? Perhaps it is possible but its hard to understand, complex to do it with an editor or a script.

I am sure, that you can do wonderful things with Q5 (cant wait to get it !!! ), but one of the most important thing is, that "normal" users still can create their game without much knowledge about objects and scripts. And I think my concept of exits would support this