Closed Arnuh closed 10 months ago
It's always hard to catch issues like this, given the enormous amount of versions and variations of files to be tested against. I wish it could be done automatically someway, somehow.
Perhaps limiting the scope of sorting to only map layer canvas and subproperty?
Like I said previously, sorting shouldn't happen unless its opt in.
I'd assume proper setup is the following, hopefully I'm not missing anything.
LMK if there's any other issues.
I'll close it. From my basic usage it seems to work as intended, any issues with the sort buttons would be a new issue imo.
Your problem also occurred when I saved GMSv83 as another IV. How did you solve it? Can you guide me to solve it? Is there a bug in the operation or can you post the code that fixes the problem.
Your problem also occurred when I saved GMSv83 as another IV. How did you solve it? Can you guide me to solve it? Is there a bug in the operation or can you post the code that fixes the problem.
Latest release doesn't have the issue fixed, you have to build it yourself for now if you want it fixed.
I already stated this in the initial issue #173 that ended up introducing such change. This change directly breaks wz files.
Running something as simple as what's shown below "corrupts" Base.wz due to the code introduced in https://github.com/lastbattle/Harepacker-resurrected/commit/a5760d43eb187354c466665a404ee5ca9f3e2001
I suggest reverting the commit and looking to introduce the feature in another manner if still deemed as needed.
Order matters, MapleLib should never touch it without the user opting in. Attempting to add workarounds where ever it breaks things is not the correct way.