#NEKOSUKE DEFENSE RPG SAVE EDITOR CODE#

In the Save your game events, set the variable called Game ID to 2. This means that the second game's ID is 2. In the Check data transfer event, select Not Equal to and 2 underneath our variable checked box. When coding another game, Game no.2 for instance, you need to edit the event called Check data transfer in our Save Map, and the events called Save your Game. Make sure you copy/paste this Save your game event in every map you want the player to be allowed to save the game. Set a different variable for Map's ID, X location and Y location.Р”Р„dd a Teleport to our previously-made Save Map.Р”Р„dd a Recall to Location and select the variables for Map's ID, X location and Y location we just made. In the Event Commands box, set the variable called Game ID to 1 (since this is the first game).Р”Р„dd a Memorize Location. In any map where the player is allowed to run this event (for instance a hallway hosting a save crystal before a boss fight), make an event called Save your game.

#NEKOSUKE DEFENSE RPG SAVE EDITOR CODE#

We now have to code the event that allows the player to save the game. When you're done initializing, add a Teleport to the current game's party starting position. You might want to initialize other things, such as current party members, etc. In the example below I set Variable 0001 to zero to initialize whatever story-related scene it is assigned to (in the sample game provided below, I set it to the number of times you speak to the kids). In the Event Commands box to the right, you want to initialize all of the story-related switches and variables of the game. Select the Parallel Process trigger condition. This means that our first game's ID is 1. Since we are coding the first game, select Not Equal to and 1 right underneath. In this event's Preconditions box, check Variable. This event will check if the save file the player loads had been transferred from another game to this one, and initialize all of the current game's story-related switches and variables so it can be started anew while keeping past progression. In this map, make an event called Check data transfer. This might sound more complicated than it actually is. That way it will be much easier to initialize them all when needed. You should also use the same switches and variables for the story-related events of all games. For instance, all Items should be the same for all games. Database settings should remain the same for all games in order for the system to work properly. I would recommend that you fully complete a first game with this system included, copy/paste its folder in your RPG Maker Projects folder and edit the copy to make it your second game. It will not work when saving through the Menu. This system only works if saving the game is initiated through an event, such as a save crystal the player steps on. A map where the player can save the game. To code the save file transfer system you will need: Note that the Save.lsd files also feature numbers, such as Save01.lsd. Transferring save files is done by opening the game's folder and copy/pasting a Save.lsd file to another game's folder. This system allows you to create different games where the players can keep their experience levels, items, equipment, money and other forms of progress achieved in previous games when starting another one. This simple tutorial allows a save file transfer between RPG Maker 2k or 2k3 games that are linked together, such as sequels or chapters released separately.

Nekosuke defense rpg save editor