can't open data.win (out of chunk bounds) for Me and (My) Cat's Island Demo

[Imaynotbehere4long]

Describe the bug

Both version 0.6.1.0 and the fork linked in this thread trigger this error when trying to open the data.win for Me and (My) Cat's Island Demo:

I was unable to test this on the Oct. 8 bleeding edge version because that build (GUI-windows-latest-Debug-isBundled-true-isSingleFile-true) wouldn't run at all for me, even after clicking "Run Anyway" on the Windows Defender pop-up. I double-click its icon, it pretends to load for a second or two, then nothing.

EDIT: Got the bleeding edge build to run, but it still gives me the same error.

Reproducing steps

1. Download the free demo for Me and (My) Cat's Island
2. Try opening the data.win file

Setup Details

1. 0.6.1.0, Dec 2 bleeding edge build, and
   https://github.com/UnderminersTeam/UndertaleModTool/actions/runs/10398025646/artifacts/1814233921
2. Windows 10
3. https://store.steampowered.com/app/2703970/Me_and_My_Cats_Island/

[maxiterr1]

Try again with the latest bleeding edge release. The fact that it doesn't start at all isn't good. Maybe an outdated .NET framework? Idk

[Imaynotbehere4long]

Just tried the latest bleeding edge release, and still nothing (again, previous builds still run fine). If it were the .NET framework, surely there would at least be a pop-up telling me to install/update it like there was when I ran the fork, right? I went to the .NET website and saw both NET 8 and 9 had recently-released versions (same date for both), and .NET 8 was what the fork told me to install back when I first ran it, so I'm not sure which I should download to test this.

[Imaynotbehere4long]

Okay, so the Dec 2 bleeding edge build worked for me today; I think the issue is that the newer builds use C drive storage instead of RAM to do...something (even though I put all my builds of UndertaleModTool on my D drive instead), but since my Windows Update kept clogging up my C drive for a while, there wasn't enough storage space to do whatever the newest UndertaleModTool builds were trying to do.

And with that out of the way, I can confirm that the Dec 2 bleeding edge build STILL gives the exact same error, so my initial issue remains unresolved.

[luizzeroxis]

@Imaynotbehere4long, can you try my fork? I tried loading the game and it seems to have worked. No idea what exactly was added to make it work though.

Download: https://github.com/luizzeroxis/UndertaleModTool/actions/runs/12170130335/artifacts/2276480030

Also, in the single file version, it'll unpack itself in the temp folder, so that might be what you were having problems with, so I suggest using the non-single file one instead. (my version is single file only, sorry...)

[Imaynotbehere4long]

That did the trick, thanks! Now we wait for it to be rolled into the main build before the thread can be closed...

Also, in the single file version, it'll unpack itself in the temp folder, so that might be what you were having problems with, so I suggest using the non-single file one instead.

I actually did try one of the non-single-file versions a while ago (long before my current storage issues) and couldn't get any of its multiple exe files to run, and the fix was using the single-file version of that build instead, so I wrote it off as something you'd need a bit of coding experience to use. Was I just missing something simple this whole time?