MV - Save/Load/Defeat - extra features (Auto Save, etc)

Well, I can't find any possible connection between the two plugins. Not a single function in common.

I uploaded the newest version though, so give that a try and see if it takes care of the problem for you. Also, if you don't already have the plugins in this order, try this - Top to bottom:

• ZephAM_Core
• YEP_Core
• YEP_MessageCore
• ZephAM_SaveLoadDefeat

Sorry for more bad news, but the update doesn't appear to work at all for me, no matter the load order. Not only that, but it went from blocking certain plugin commands (specifically, message core's) to virtually all plugin commands.

In fairness, it's a game in progress with a lot of plugins, most of them Yanfly's. If I try dropping the SaveLoadDefeat plugin down to the bottom of the list, it throws up a "TypeError: Cannot read property 'toLowerCase' of undefined" and points to Yanfly's Core Engine's line 1098: console.error(e.stack);

I appreciate your effort, in any case, and I hope others have more success with it.

Don't give up yet ^_^.

I'll look into this and see what I can find. If you could screenshot the console error list - and maybe your plugin list - that may help.

Edit:
Also - console.error(e.stack)? That's line 1094 in my Yanfly Core. Double check that you have the updated version of that plugin? Though it hasn't been updated in a while. Should be version 1.31

Tried putting those 4 plugins into an older project of mine - pre MV 1.41 - but still works without crashing... Hmm.

@Drunken Paladin - The plugin worked for you a few versions ago, right? Do you happen to remember the last version it worked with? Or a feature in the update list that wasn't there when it worked?

I was trying to get this to work for a while now. I'm out of ideas.


It does create an autosave slot, but doesn't autosave on map transition. No message pops up or anything.


(No common events are set)

Your plugins are at the bottom of the list. I got all yanfly plugins in the correct order.
There are no errors in the console either.

(On a side note, it would've been nice if there was some information on where exactly the plugin puts the save folder. Looking for it was a pain)

Hopefully someone can help.


Edit: Using the autosave plugin command does nothing either.

Found this just as I'm headed out to work, but I'll get you an answer tomorrow (I'm on EST, so it's 12:30 now).

I don't see anything wrong at a glance, but throwing it into an empty project, you're right, the auto save doesn't seem to be registering.

Thanks for letting me know! (And I'll make a note of the save location too.)

~ Zephyr

I find it quite amazing how most plugin authors are still so active on here, even when the last post is years old most of the time :D

Since I’m not working on any large issues on Entitled, putting a bit more work in here.

Along with fixing it, I’m planning to rework this plug-in a bit (wasn’t happy with it’s usage when I tried to use it awhile back).

• Remove Core plug-in requirement - never expanded into a wide library, not worth it really
• Alter/Add Defeat option that occurs before Scene_Gameover - avoid the gameover screen/menu entirely
• Link plug-in text to my Translation plug-in, if it exists - will not be required

Let me know of any other features that could improve here!

~ Zephyr

Those are solid improvements! What I'd like to see is the option to autosave based on time. Like every 15 minutes or so. I feel that's how most modern games autosave anyway.

Please do ping me whenever the update hits. I don't want to miss that!

Updated with basic fix for Auto Save not functioning. Works now ^_^

Also removed the 'set save filepath' option, as there's really too many things that can go wrong with that. After more thorough searching/testing, I may be able to reimplement. For now, just added code to make sure the /save file exists in the game folder. Can still set the naming scheme for save files though.

Wanted to get a 'working' version up quickly

~ Zephyr

Edit:
Oh, and you’ll need to copy all the saves in your current save folder over into the base game save folder for now. Sorry!
Changed ^_^
Folder save path setting works again. Core reliance removed (if you keep Core though, update it too). Couple more things. Notes in the update spoiler.

Added a new version with better(?) auto/quick save connections, depending on the needs of the devs.
As usual, there's bound to be bugs hiding amongst the code, so let me know of any problems!

(Sadly not working with YEP_SaveCore for now XD)
Works with YEP_SaveCore again! I am working a few functionality quirks out between the two, but everything runs without trouble so far!

Great plugin, definitely would like to use it in my games!

There is just one issue though, and I don't know if it's intended. When entering the load screen from the main menu, you can select and save to an empty slot. It doesn't work of course, but if you enter the game first (i.e. actually enter a playable map) and exit to the main menu again, you can save into empty slots from the main menu, and it'll save the game as though you were in the game at the map you were in before you exited to the main menu.

Another issue I found is that disabling save access (using the vanilla Change Save Access command) doesn't work when this plugin is active. I can still save from the save menu even after disabling save access. And while I'm on the subject, is there a plugin command or something to disable quicksaving?

I do have a ton of other plugins (though Yanfly Save Core is the only thing affecting saves), so it could be a compatibility thing, but turning off this plugin (V1) disables saving in the main menu again and disables save access when it's supposed to.

Let me know if you need additional information, and thanks in advance!

Same. If you want to load/continue your savegame (main menu, not ingame menu), it first selects a blank savefile, instead of a used savegame. Also you have to additionally press "enter" one time.
Anyway, great plugin :).

Sounds like it's selecting an empty slot instead of defaulting to the most recently played save?

Also, for the "enter" thing, are you using Version 2 of the plugin? In that one, each save slot has its own dedicated auto/quick saves, so the first "enter" is to select the base save slot, so you can then move up and load an auto/quick save if you wanted.

Assuming I'm understanding right ^_^

Yeah, looks like it´s selecting an empty slot instead of defaulting to the most recently played save - just as you said.

Yes, I am using version 2. Maybe it would be great if you could disable this option then? Or maybe I´ll take a look at version 1 then.

If you don't want the slots to have dedicated auto/quick save slots, then yeah, pick up V1 instead. That's the primary difference between them.

If you just don't like how it works, with the "enter" to select and "enter" again to choose, a custom UI may fix the issue - if you're intending to make/have one made.

I will look into the 'starting Load on an empty slot' thing though. Thanks for the heads up!