Marten wrote:Do you also mean by "private" that only one player can enter the instance? That is not what I mean.
No. I mean one owner.
Marten wrote:You're right that a totally private Delin isn't of much use. But the approach I envision for instancing is to enable ad-hoc groups of players to form and visit instances together very easily. The Delin book can still reside in the Neighborhood library. I think it would work this way:
- Players approaching the book would have the option of linking to the original (public) instance or the journey (private) instance.
- The public instance is a place to visit, relax, and party. It is not possible to collect rewards there.
- If the player is solo (a group of one) and links to the private instance, he or she won't be able to solve the puzzle. (For various reasons, I do not want to prevent a player from linking into this age by himself or herself if that is what the player really wants to do.)
- If the player has formed a group with other players, anyone from that group that links through to the private instance will land in the same instance.
Forget the original instance of delin. Players can visit, relax and party in the private instance which is already public (shared)
Marten wrote:* If you wanted to hold a party in the back part of Ahnonay sphere 4, then players would need to use the journey cloth in the group leader's player's Relto - also exactly how it worked in MOUL.
No. Once the sphere is set as the active sphere, you can link there from the Ahnonay Cathedral. However if you want to link outside of the sphere, you need a cloth (or a new linking book).
Marten wrote:I hope this clarifies things... my intention is to develop a set of new rules that do not limit or take away what players could do in MOUL, but that introduces additional possibilities and makes the game easier to play and understand.
Seen from that point of view...
I've got an idea... it's a mix between what is currently implemented and the public ages idea.
In MOUL, you have three instancing models. Public, hood and private. Public is exclusively used by the cavern. Hood is for multiplayer ages and private is for ages where you can have persistent changes. We can't remove public and we can't remove private. Now what to do with hood ? It can't become private because of the multiplayer aspect of the ages. On the other hand, if it becomes public, then you get all the population issues.
While thinking about the behaviour of the Delin book, I noticed something interesting. Every Delin book is in the same cavern (IC) but they all link to differents instance. One book, one instance.
A book instance.
An age can have a book instance and a private instance. -> Singleplayer ages
Another age can have a book instance and no private instance. -> Multiplayer ages.
The whole idea use the following rules:
Links to cavern in nexus are for the public instance.
Links in Relto are for private instances (except hood and nexus)
Concerning the cavern.
Nobody can own the cavern.
The "private" instance of the cavern is shared with every member of the hood.
The global IC instance of the cavern can only be accessed through Nexus. (except hood)
Rooftops and others places like that:
Each "public" rooftop has its own instance.
Each "private" rooftop is in the "hood instance"
Links to public ages.
2 books in the same instance -> 2 instances or 1 if it's the same age. Can also be 2 instances even if it's the same age.
1 book in 2 instances -> 2 instances
Links to private ages:
Same as in MOUL.
Concerning ages.
You can only acquire and/or access your own instances through a place you own or one that nobody can own.
Links to public ages:
2 books in the same instance -> 2 instances or 1 if it's the same age. Can also be 2 instances even if it's the same age.
1 book in 2 instances -> they all go to the same instance.
Links to private age:
You link to the current age owner "private" instance.