Hello.

Play this: http://textadventures.co.uk/games/view/ygx7zfaobkcdnalth3wknq/relay-game

Use the thingy.

That will transport you to a second game.

If you start the second game on its own, you will not have the thingy in your inventory.

If you use the thingy in the first game, that will move you to the second game, and you will have the thingy.

Here's the link to the second game, so you can see what happens when starting the game without having been transferred there from the first game.

http://textadventures.co.uk/games/view/7yk1_ymuykkjnenlsxbdug/a-quest-6-serial-adventure-act-i-game-1

Fascinating, what ideas you come up with :-) Whether one could also take over the inventory with into the 2nd game?
Surely it's also possible to trigger a save before switching games. If you then use the Thingy in the 2nd game to get back into the first game, you would have to be able to reload the old save from the 1st game and continue playing from the last place - with the items from the 2nd game.

Hello, Pertex!

I hope you've been well!

Fascinating, what ideas you come up with

To give credit where it's due, Pixie came up with the idea.

https://github.com/ThePix/QuestJS/wiki/Chaining-Several-Games-Together

I do agree that it's fascinating, though!

trigger a save before switching games

I thought about trying to do that, but I decided to see how it all worked when both games were uploaded to this site. I'm sure it's as easy as parser.parse("save"), but I'm just guessing.

If you then use the Thingy in the 2nd game to get back into the first game, you would have to be able to reload the old save from the 1st game and continue playing from the last place - with the items from the 2nd game.

Whether one could also take over the inventory with into the 2nd game?

Well, I was thinking . . .

It's easy to pass the data. You basically just send what you would code in JS. Like, in this one, I passed this when using the thingy: w.me.usedThingy = true.

In the first game, the thingy is in the first room (of course).

In the second game, the thingy is Nowhere. On load, a script checks for data, and this one checks for w.me.usedThingy once the data (if any) is loaded. So, the second game sees that the player used the thingy from the first game, and it moves the thingy in the second game to the player. All attributes on the first thingy could be transferred to the second thingy between games. This game was just a very basic test.

Anyway, I have a room called "Nowhere". In Nowhere, I can place one of each type of object, each with a name reflecting its type (e.g., "blank_switchable"). Then, I can pass data between games that will lead to cloning whichever object and setting whatever alias and whatnot. Should be relatively easy.

I think the hard part would be actually loading a saved game when jumping between games. It works like the Glulx games work on this site. You can have multiple saves in your local storage. That would make it difficult to code things correctly, I bet.

...unless Pixie knows of some way to check which saved game is loaded from within the game. If that could be done, we could easily concoct a data string to pass the information back and forth, I suppose.

Gosh, Pertex! It sure is nice to hear from you! I reiterate my hope that all is well!

I think the hard part would be actually loading a saved game when jumping between games. It works like the Glulx games work on this site. You can have multiple saves in your local storage. That would make it difficult to code things correctly, I bet.

You just give it a name, so you do parser.parse('SAVE GAME'), and later parser.parse('LOAD GAME') (I think anyway, not tried it).

Gosh, Pertex! It sure is nice to hear from you! I reiterate my hope that all is well!

Yes, I am doing very well, thank you for asking. I'm on vacation now, Christmas is just around the corner and I'm happy that Quest is continuing. It's very impressive what The Pixie has done there. And that you play around with it so enthusiastically :-)