Keeping tokens when saving/loading

Make Forums Requests Keeping tokens when saving/loading

This topic contains 10 replies, has 4 voices, and was last updated by  Aura 4 months, 2 weeks ago. This post has been viewed 623 times

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
  • #3352



    We have a function of “reset game” to make tokens go back to zero. But they go back to zero when ever you save/load the game as well.

    For example, if I play a game and receive 1 token, that token will disappear if I save my progress and load the saved file again.

    Will there be a function to save your progress of playing the game (not saving the progress of MAKING the game), where the player could keep received tokens and continueing where the player left off another day?




    As you already noticed, save games isn’t implemented yet. This is also one of those features that I will postpone until it’s obvious you definitely need it ;).

    For now, all games I’ve seen can be played in maximum 15-30 minutes, so I think it’s still OK to skip the save functionality. You’re also the first one to bring up this topic (my features are highly influenced by what people are requesting), so I’m definitely taking note. But for now, I think I can still get away with not having it. We all still make short games.

    There is also an extra thing I need to consider when I implement save games: what happens with game updates. Assume some player plays your game version 1.0, and stores some checkpoint and leaves the game. You make changes to your game, add some enemies, remove some, add a level, etc. Now the player comes back to your version 2.0 game, and wants to load the old saved game. What do I do?

    1. Bring the player back to version 1.0 if he wants to continue. But this means I need to keep track of all previous versions.
    2. Try to upgrade the 1.0 save file to 2.0, but it’s impossible to get this 100% correct all the time

    I’ve already analysed a solution for save games, and the implementation, which is basically game state saving, can be applied to 3 different things:

    1. Save your progress in the game
    2. Rewind/Replay functionality (in the maker tool, not in the game itself)
    3. Multiplayer

    Multiplayer seems a bit weird here, but it’s actually sending (a part of) the game state to the game server and clients.

    And I’m definitely excited about the rewind/replay functionality that could become a part of it. Imagine you are testing some boss fight in your game. The boss is maybe too strong. So you open the editor, rewind a bit, set the boss damage a bit less, and test again. I think this could be really cool.

    And of course, as you mentioned, saving the game progress together with the game in a project file could be handy that you can just resume where you left off.

    So, long story short: not in the near future.

    But if I am correct, it seems you want it purely to not lose the tokens while editing your game. Would it help you if I added functionality where you could add/remove tokens? This way after loading your game, you could add the tokens manually and test the part of your game that you want.




    Hello, and first of all, thank you for the answer and the rpgmaker! It’s wonderful!

    The reason why I asked about the save progress function is because I’m doing a cross-over boardgame as a birthday present for someone turning 30. We are doing a sort of “Super Metroid/Hollow Knight” ANALOG boardgame (with dice and cardboard figure) and ONE of the sections on this analog boardgame is a DIGITAL world. In this digital world he needs to figure stuff out to get through to the next section in the boardgame. But, as in all metroidvania games, you always need to revisit every section at least twice when you get a new set of skills that could reach a passage you couldn’t before. That’s why the save-tokens function would’ve been nice. Not a save game, only save tokens so that he wouldn’t have to speak to the same people in the village again (solving the pussles again). Which also would mean that, when his birthday comes we would make no more changes to the game so the aspect of which version the game would be wouldn’t need to be updated?

    For exampel: let’s say that the DIGITAL world is “section 3” in the metroidvania board game. Somewhere in “section 4” (a analog section) he will get info about a hidden secret level in “section 3” (which is a medium room, with invisable doors on the ground which he has to get info about how to cross the room in “section 2”). So my guess he would have to revisit the digital world/section probably around four times! 🙂

    But hey, his birthday isn’t for a year or so. Maybe more people than me would’ve requested this function in a year!

    You are doing a fantastic job! 🙂



    Two games I’m making have a bunch of tokens and variables. I’ve already told people about having the ability to save within one of said games, and I REALLY don’t want to work on a password save system. I will if I have to, but that pulls me away from making content and overall discourages me from continuing on said project. Said game is being released in April, so perhaps an actual save system could be added before then? You said you were getting rid of the Play page to make room for something within the engine, so adding one spot in the menu for loading saved games shouldn’t be a huge issue. Hopefully. I know almost no code, and what I do know is either Python or how to start/end tags in HTML, so I don’t know how this would go.



    Presenting the load games will be easier indeed, but the saving itself still needs to be done, which will take some time.



    Do you have a ballpark estimate for when this functionality will be added?



    It’s pretty high up the wish list with 8 votes (see, so I hope to make it available this year.

    I will go with the solution of different releases of your game. So if you share your game, it will become a separate version. If a player loads a save game, the player will stay in that version, even when there is already a newer version of that game available.

    After that I can see how easy and robust I can make it so savegames can be upgraded to the latest version of the game. But the one who made the game might need to take certain things into account so upgrades work fine.

    So first I will implement that you share your games to certain releases, and after that I can make the save/load games. This year 🙂




    Hi! I have another question about saving: would it be likely that you would have to have an account in RPG Playground to use the save functionality, or could it be utilized by those without? This same game is mostly being made for people who don’t use the engine to make games-at least, not to my knowledge-and, as stated before, are expecting some kind of saving.



    Yes, you will need to have an account to save your game. But I guess all web games require that. RPG Playground will not require you to make games, so you can just play games if you want to.

    People can freely play without registering, but when saving, it asks for email and password. You can compare it to Kongregate or Steam or anything else, where you both have players and game developers. Players still need a login too.

    Below is the working version of the new welcome screen. As you can see, you can create, but a huge focus is now on playing. You will get this screen without registering, and you can play without registering.

    A direct link to your game will still start it right away, without registering. So it should be fine.

    Remark that I want to bring RPG Playground to this year. So that means a lot of players will be able to play your games, without the need for a RPG Playground specific login (because they use the one from Kongregate). Saving etc. will also be possible there.



    Okay! Thanks!



    This looks already amazing! It makes you eager to create your own game as well as playing others… And it will surely attract some more users/players! Can’t wait for this update! 🙂

Viewing 11 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic.