LTN Core, Day and Night, Time engine Type error

[GigglePickle]

For my game Im using the LTN core, time engine and day and night plugins.
In testing, whenever I enter a battle I get this error:



I read a similar thread with this sort of error about changing one of the parameters on LTN core.js for the rescale backgrounds paramater for "battle" to false, however that was already set to false.
Heres a screenshot of my parameters:



Day and night plugin parameters:


Time engine plugin parameters:


Here's the dev tool error code:

rpg_managers.js:1949 TypeError: Cannot read property 'battle' of undefined
at Spriteset_Battle.$.rescaleImageBackground (releases_LTN_Core.js:1586)
at Spriteset_Battle.$.locateBattleback (releases_LTN_Core.js:1581)
at Spriteset_Battle.updateBattleback (rpg_sprites.js:2487)
at Spriteset_Battle.update (rpg_sprites.js:2454)
at rpg_scenes.js:262
at Array.forEach (<anonymous>)
at Scene_Battle.Scene_Base.updateChildren (rpg_scenes.js:260)
at Scene_Battle.Scene_Base.update (rpg_scenes.js:113)
at Scene_Battle.Scene_Base.update (releases_LTN_TimeEngine.js:588)
at Scene_Battle.update (rpg_scenes.js:2259)

 

[GigglePickle]

It also had this:

Uncaught TypeError: Cannot read property 'Game_Time' of undefined
at releases_LTN_DayNight.js:170
at releases_LTN_DayNight.js:410

 

[GigglePickle]

Here is the link to the reddit thread for more info:

 

[Aloe Guvner]

Can you provide a link to the plugins so people can double-check the instructions?

And are you sure it should be named "releases_LTN_DayNight.js" and not "LTN_DayNight.js"? If you rename it instead of keeping the name the author gave it, it might not load plugin parameters which would cause issues.

 

[GigglePickle]

Sorry about the link, i forgot to post it. Heres the link to the plugin page:
https://rpgmakermv.co/resources/day-and-night.1047/

 

[GigglePickle]

I changed the names of the plugin file and that fixed the problem. How did I not think of that! Anyway, thank you for pointing that out Aloe Guvner.

 

[Aloe Guvner]

That's OK, it's a common mistake because it's not always obvious.

The reason is from a coding perspective, the easiest way for the plugin to read what settings you have done is with the name of the plugin. The MV editor saves those settings next to the plugin name, so that's how the plugin author will program it to read the settings.

There's another way to do it without needing to use a specific name, but most plugin authors don't do it that way (myself included).