06-08-2024, 07:11 PM
Alas, in two days...
First, I was given a request to alter the Scene_Config option.
Originally, you needed to pass a 'true' value into the configuration menu's command to inform the system that it was to return to the main menu. However, I was told that some custom main-menu systems would not work with the command: Xail's, Mobius's, and others.
So, one needs to either include the 'true' value to the Scene_Config command when using it from the field map, or the quick command I had already added. So if anyone was just using the quick command in their project, you're good.
There was an issue with the menus built into the Battlemusic, Windowskins and Fonts menus. That is, if the unlocked music/skins/fonts skipped around, the index position was not accurately returned. A couple lines each was needed, and repaired these.
And the Windowskins plug-in had one more issue. The use of the "Restore Defaults" option worked, but it invalidated the "FIXED WINDOWSKIN" option. A fixed windowskin is when the skin for the options menu is not supposed to change regardless of windowskin you change for all other features. However, the Command Window for the menu did. This required some subtle changes to the plug-in so the Fixed Windowskins remained in place when engaged.
BUMP
TO VERSION 2.1
TO VERSION 2.1
First, I was given a request to alter the Scene_Config option.
Originally, you needed to pass a 'true' value into the configuration menu's command to inform the system that it was to return to the main menu. However, I was told that some custom main-menu systems would not work with the command: Xail's, Mobius's, and others.
So, one needs to either include the 'true' value to the Scene_Config command when using it from the field map, or the quick command I had already added. So if anyone was just using the quick command in their project, you're good.
There was an issue with the menus built into the Battlemusic, Windowskins and Fonts menus. That is, if the unlocked music/skins/fonts skipped around, the index position was not accurately returned. A couple lines each was needed, and repaired these.
And the Windowskins plug-in had one more issue. The use of the "Restore Defaults" option worked, but it invalidated the "FIXED WINDOWSKIN" option. A fixed windowskin is when the skin for the options menu is not supposed to change regardless of windowskin you change for all other features. However, the Command Window for the menu did. This required some subtle changes to the plug-in so the Fixed Windowskins remained in place when engaged.