That is definitely too many symbols/bookmarks. I'm in favor of keeping it to a minimum... public, group, solo. (group and solo are both forms of 'private').
My hope is to find some time, soon, to "mock up" a demonstration of the ideas here, and to spec out how it would apply to every single book and link in the game (long list), to make certain that I haven't left any uncovered holes in my thoughts.
Cleaning Up Instancing
Moderator: OpenUru.org Moderators
Re: Cleaning Up Instancing
The music is reversible, but time is not.
Re: Cleaning Up Instancing
I think I still prefer just having Public and Private instances, with all D'ni/Cleft being Public and Ages linked from those being Public until they're added to relto/nexus where when accessed from those locations they'd be private.
Re: Cleaning Up Instancing
Public and private: yes.
Private from Relto and Nexus only: no.
Private from Relto and Nexus only: no.
A demonstration of the symbols or of your whole instancing idea ?Marten wrote:My hope is to find some time, soon, to "mock up" a demonstration of the ideas here, and to spec out how it would apply to every single book and link in the game (long list), to make certain that I haven't left any uncovered holes in my thoughts.
Re: Cleaning Up Instancing
The whole idea.realXCV wrote:A demonstration of the symbols or of your whole instancing idea ?
The music is reversible, but time is not.
Re: Cleaning Up Instancing
And still I havn't read a better model to do this than the one I proposed, with the amendment for handling the Yeesha bookmarks.
By golly, it takes 2 seconds to click on the share page first before clicking on the linking panel to carry on with a private instance - handled through the Big KI
Or in the case of a new book, clicking on the share page would add the book to the Nexus
Its not that complicated
if player == PublicAge
....if player clicks link page
........link player to a public instance
....if player clicks on share page
........add Age to Nexus
....if player clicks bahro link
........link player to public instance
....if player clicks bahro share
........add stone link to players' book in Relto
if player == PrivateAge //Controlled through the Big KI and Nexus (hood and party controls), unless the Age was accessed through Relto, then override
....if player clicks link page
........if player did not previously click on share page
............link player to public instance of Age
.........if player did previously click on share page
............link player to private instance
....if player clicks share page
........if book is new
............add book to Nexus (and Relto if applicable (kemo))
........prepare to set a private instance, or join instance (Big KI controlled) of next Age
....if player clicks bahro link
........link player to public instance
....if player clicks bahro share
........add stone link to players' book in Relto
Yeesha bookmark Relto
....if clicked return player to instance last clicked
Use the Big KI to tell the game if the bahro stones that are in a private instance, to link the player to a hood/private (or party) instance, when the link plane is clicked after the share stone
I admit there is some learning to this method, but it is indeed clean, with no extra symbols that what there is already (Ahnonay cathedral will need to be reworked for this)
All public instances of Ages will have several key objects that are purposely disabled or hidden, like cloths, a switch, a door
Eg a player can be in a public instance of Tolesa, the telescopes work, but even if they are aligned, the door would not rotate, such is life when equipment has been left idle for hundreds if not thousands of years, it will not work, the stone will be there, the Yeesha cloths be hidden and disabled. These things can be controlled quite well through SDL variables
By golly, it takes 2 seconds to click on the share page first before clicking on the linking panel to carry on with a private instance - handled through the Big KI
Or in the case of a new book, clicking on the share page would add the book to the Nexus
Its not that complicated
if player == PublicAge
....if player clicks link page
........link player to a public instance
....if player clicks on share page
........add Age to Nexus
....if player clicks bahro link
........link player to public instance
....if player clicks bahro share
........add stone link to players' book in Relto
if player == PrivateAge //Controlled through the Big KI and Nexus (hood and party controls), unless the Age was accessed through Relto, then override
....if player clicks link page
........if player did not previously click on share page
............link player to public instance of Age
.........if player did previously click on share page
............link player to private instance
....if player clicks share page
........if book is new
............add book to Nexus (and Relto if applicable (kemo))
........prepare to set a private instance, or join instance (Big KI controlled) of next Age
....if player clicks bahro link
........link player to public instance
....if player clicks bahro share
........add stone link to players' book in Relto
Yeesha bookmark Relto
....if clicked return player to instance last clicked
Use the Big KI to tell the game if the bahro stones that are in a private instance, to link the player to a hood/private (or party) instance, when the link plane is clicked after the share stone
I admit there is some learning to this method, but it is indeed clean, with no extra symbols that what there is already (Ahnonay cathedral will need to be reworked for this)
All public instances of Ages will have several key objects that are purposely disabled or hidden, like cloths, a switch, a door
Eg a player can be in a public instance of Tolesa, the telescopes work, but even if they are aligned, the door would not rotate, such is life when equipment has been left idle for hundreds if not thousands of years, it will not work, the stone will be there, the Yeesha cloths be hidden and disabled. These things can be controlled quite well through SDL variables
Re: Cleaning Up Instancing
If the player click twice on the share page, does the book reverts back to public or does it stay in private?
Re: Cleaning Up Instancing
Having to click something on a book to make it private, then clicking it again to make it public, says to me that it is being over complicated. Not to mention to annoyance a mechanism would cause when it borks and you're trying to get a group running through one of the Ages.
Re: Cleaning Up Instancing
A click is not that complicated. What is complicated is to find an instancing method with no holes.
Re: Cleaning Up Instancing
That is the truth!realXCV wrote:A click is not that complicated. What is complicated is to find an instancing method with no holes.
The music is reversible, but time is not.
Re: Cleaning Up Instancing
No just a click, if you click 5 times, it will still be considered that you are requesting a privatized/hood instance.Tweek wrote:Having to click something on a book to make it private, then clicking it again to make it public, says to me that it is being over complicated. Not to mention to annoyance a mechanism would cause when it borks and you're trying to get a group running through one of the Ages.
I believe this method has the least amount of holes in it. It definitely has less holes than what Cyan had put in it.realXCV wrote:A click is not that complicated. What is complicated is to find an instancing method with no holes.
Best of all it fits within the confines of the greater story and book mechanism
You can also say that with using the Big KI you could if you wanted to have all the books in Relto take you to the last instance you visited, but I reckon that is where I draw the line, above that, Relto book links always take you to a private/hood instance, consider them to be "hot links", with the regular method being used through the Nexus