Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I believe MS Office apps use a hidden "recovery" file that auto-saves every so often. When the program closes normally, this file is deleted. When launched, the app checks for the existence of any such file and if so launches the recovery process. Not sure if that's possible in RMMV without a major rework of how it accesses files, but could be worth requesting regardless. =)
Don't you test everything you do? If you work for 2 hours, and run into a strange error in the game, how will you ever find out what went wrong? Is it something you changed 2 hours ago, or did you make the mistake just now?
My advice is to test your progress with every little change you made. This way you save often enough, and you are always sure everything works.
What Caeth says is right too. MS office uses temporary saves on a timer, which only saves the changes, not the whole file. This is impossible (or at least very hard) for MV, because your project is not 1 file, but a collective of many files.
Thank you amigo.
The two hours was spent mainly writing dialogue and building maps- nothing that really needed testing. I think I grew complacent with RPG Maker VX Ace. I have a little over 700 hours in it and it never crashed, so I suppose I didn't think RPG Maker MV would either. I suppose I there's not much to do except start saving/closing the game more often.
You don't have to close the game all the time. It won't crash all the time either. But if you don't test, just teach yourself to hit ctrl+s everytime you changed something important.
And even without all that, you need to test dialogue to see if all tekst fit the screen. And to see if you didn't make any weird typo's. And if the dialogue gets triggered right.
But if you make a tiny mistake somewhere, and you miss it cause you don't test, that could mess up the whole flow of your game. And if you work for 2 hours after that mistake, and you finally test, it is hard to pick out those tiny mistakes.