Good evening.
I'm creating a game in "Text Adventure" mode, not "Gamebook" and every time I advance and play it, I have to start from the beginning. Is there any way for my character to start in the place I want or just in the place where he/she has stayed?
Thanks in advance for the answer.

You should be able to just 'SAVE GAME' and then 'LOAD GAME' to resume at the place you left off. Check the docs for the exact syntax as I may have mis-remembered.

If you're talking about saving while testing the game during development, the save system won't help you – as it saves an entire copy of the game. In this case, the most common way to deal with it is to create a hidden command which restores the player's location/inventory/stats to specific values.

If you're creating a game on the desktop editor, I believe you can also use a feature called "walkthroughs" to record your progress through the game up to a certain point, and then replay it later.

Thanks to both of you for the response.
Yes. I really mean saving while testing the game during development.
I am using the Quest application but without programming. I see that using the “Code View” option lets me insert commands.
Could someone please pass me the code or sequence of commands to insert? I have never done it but I will try as a newbie to see if I can do it.

Thank you very much in advance.

It's not something you can really give a predetermined series of commands for.

For example, one game I've been debugging has a scenery object in the first room called "cheat ball". Because it's scenery, you can't see it unless you know it's there; the player has to type in "get cheat ball" to pick it up. Then it has verbs called things like "skip chapter 5", which do something like:

SetObjectFlagOn (gemma, "caughtfish")
AddToInventory (smokebomb)
AddToInventory (fish)
AddToInventory (broken pipe)
MoveObject (player, courtyard)

It's basically just giving the player all the objects they need and teleporting them to the right place so that the creator can test a later chapter without having to play through the game up to that point every time.

If you use an object like that, I would suggest putting it inside a non-openable object before you publish the game; meaning that players can't get to it but moving it out again for future testing is just a click away in the editor.