One annoying thing about RPG Maker 2.

[ErikaFuzzbottom]

When you delete data, it no longer recognizes your test play.

What's up with that?

[Biggie]

Re: One annoying thing about RPG Maker 2.

Never had that problem.

Are you playing on an 80gig ps3 or something?

[Ryner]

Re: One annoying thing about RPG Maker 2.

I think there's more than one annoying thing about RPGM2.

[ErikaFuzzbottom]

Re: One annoying thing about RPG Maker 2.

Never had that problem.

Are you playing on an 80gig ps3 or something?

Nope, it's a regular fat PS2.

What I did was remove an event from the game system and then trashed the event. All of a sudden my quick save was gone, and attempting to load the last save only resulted in it not showing the file. It's happened before, too.

[BlueSenshi]

Re: One annoying thing about RPG Maker 2.

When you remove an Event from the Event Database, all of the other Events get moved "up" to fill in the unused sequence number. This changes everything in your test play save that refers to any Event "below" the deleted event. If it was the last one in the list, no harm done. If it was near the top, everything will have changed, and there's no way to resume the game using the old save.

You might consider it annoying, but it would be very difficult to properly convert the test play save to the new DB order, especially if you deleted multiple non-consecutive items. It's much simpler to just delete the test play save entirely.

[ErikaFuzzbottom]

Re: One annoying thing about RPG Maker 2.

Doesn't seem to affect when you re-start the game. Guess RPGM2 just saves funny.

[BlueSenshi]

Re: One annoying thing about RPG Maker 2.

I'm curious what you mean by "restart the game". As in hitting Reset and then reloading your game data in the editor? (I typically have the starting point set to whatever I'm trying to test, therefore I don't need to resume previous test plays, so I haven't encountered this problem.)

[ErikaFuzzbottom]

Re: One annoying thing about RPG Maker 2.

I mean when you start a new game. Which is what I have to do every time my test play fails.

[BlueSenshi]

Re: One annoying thing about RPG Maker 2.

When you start a new test play, you don't have pre-existing save data that refers to any of your Events. All of the new data will use the current Database.

For example, you have an Event, we'll say it's Event 500. During your test play, you register it as a vehicle and summon it to a new map. Event 500 is now on a new map and not on the old map. You save your test play, so Event 500 is now in a new location.

The next Event in the DB is number 501. It serves as the front door exiting a house. You decide to delete Event 500. This moves Event 501 to the 500 spot.

You want to load your test play. Your game save tells RPGM2 that Event 500 is wherever you parked your vehicle. This Event is still registered as a vehicle, but the script clearly moves you to the outside of the house. It doesn't have any of the Vehicle scripts you'd need to use it as a vehicle anymore. Obviously I don't know how it would handle the remaining Events in the Database, as a lot of Events have default locations that they will start in that are permanent in the Event Database. But Vehicles are allowed to move around, and the game tracks their location separately and would store that information in the test play save file.

Now, when you delete an Event from the Database, RPGM2 could go back and alter your test play save to account for the fact that the DB has been altered, but it won't have any idea what to do with the data for the original Event 500 (the vehicle that you trashed). The save still has its location and Vehicle registry, but how does it recover from the fact that the Event is completely different (or if it was in the last Database spot, no longer exists)?

My guess is that there is confusion about how RPGM2 constructs the game based on the actual Game file versus the test play save data. From a programming standpoint, it is not a good idea to allow the user to resume play from a save file if the Database has been altered in specific ways. Adding new or editing existing data is generally ok. Deleting data can generate unpredictable results because your Database Keys (the Event Numbers) have changed for 1 or more records in the Database (the Event that you deleted and everything that was "below" it in the Database).

[ErikaFuzzbottom]

Re: One annoying thing about RPG Maker 2.

Ah, that would make sense, especially since I am indeed calling a vehicle to a map.

[BlueSenshi]

Re: One annoying thing about RPG Maker 2.

I'd say "lucky guess", since I don't know anything about your game and don't resume test play save data frequently, but I did specifically choose that example because I knew the game would have to save the Event's location and vehicle registry in the test play save file.

[Jeremy]

Re: One annoying thing about RPG Maker 2.

When you delete data, it no longer recognizes your test play.

What's up with that?

I agree. Not only does deleting data screw your test play, but it wipes your previous saves as well. What i do is just copy new data over old data i want to get rid of.