![]() ![]() (Maybe it doesn’t need to be set to true-I’m just guessing-but I’m pretty sure you’ll have issues if you disable it just based on what I saw in Yanfly’s core. :) So, if you want to use the fix I made, you can only use it if Yanfly’s CoreEngine is installed and above Galv’s plugin and has its scale battle backs setting set to true. The right way to add this code would be to add a check to see if Yanfly’s CoreEngine plugin is loaded first and then only run these changes if it is. So, x can’t equal 0 but, rather, needs to equal -1/2 of the total width of the background image + the width of one frame. That makes sense if 0 is the leftmost corner of the image but it’s now the center of the frame that holds the battle backs. I also had to recalculate the x because Yanfly centers the battle backs for scaling purposes so only (less than) half the animation would run (replaced by empty black frames for the other half+ frames), otherwise Galv’s plugin would start from x=0. So, I changed it to reference the new class. It would be defined if Galv’s plug-in referenced the new class. ![]() This wonderful RPG emphasizes breathtaking graphics, exploration, well-crafted characters, and challenging turn-based battles. Galv’s animated battle backs plugin works around the use of TileSetter so it ignores anything Galv’s plugin does if it appears before the core in the plugin list and breaks the plugin if it appears after because the battle backs aren’t getting set by TileSetter. Created by Ronove, Star Stealing Prince is one of the most acclaimed games for RPG Maker VX. I was planning on just letting it go, but when I was about to close the file for Yanfly’s core I realized what needed to be done…and I can’t ignore stuff like that.īasically, Yanfly changed battle backs to display through the standard Sprite class instead of the TileSetter class because TileSetter is unreliable (apparently). :-P I mean, it still holds but I fixed the problem. You can just scale those in an image editor if you need to. But turning off battle back scaling is probably an easier alternative. Of course, that could break compatibility with any plugins that rely on changes in the latest version but if you can find an older version of the entire set you can just replace them all with the earlier version. I’m not sure and am just making a barely educated guess based on skimming the release notes, but that might be worth a try. ![]() It seems like this conflict was introduced in version 1.2.3 at the earliest. Alternatively, you can probably just download an earlier version of the core. First, you can turn off battle back scaling in Yanfly’s CoreEngine and that’ll resolve the error. I’m not really sure that it is, at this point, but I didn’t dig around in their long enough to figure out exactly what’s causing the conflict.Īnyway, you have a couple of options. Breaking compatibility with this plugin has to be a pretty low priority if this change was warranted. The core changes a lot about how battle backs work to solve other issues so I wouldn’t expect a fix from Yanfly. It’s related to the scaling of battle backs. The problem is caused by Yanfly’s CoreEngine. ![]()
0 Comments
Leave a Reply. |