BorPak for Windows

[DCurrent]

That's what I was confused about because I'm like how tf did that get packed anyway? But again, I'm hella ignorant within the coding field and don't know any better so I really appreciate your insight on this. I wanted to add in a thorough breakdown for folks who also have this same problem in the future and don't have much knowledge on this as well.

And I also saw your other comment about LNS being shady, which I had no idea about, and looked into it. Didn't know there was drama surrounding them and their practices.

It seems really counterintuitive I know, but on a technical level, packing is MUCH simpler than unpacking. Think of it like an old fashioned puzzle. The original maker takes a big picture and cuts it into a number of smaller pieces, which then fit neatly inside a box. Pretty simple. Just slice things up and smash it in there. If there's a bad cut or some tabs tear off, it still fits no problem because the packer doesn't have to understand anything about what it's packing.

Reassembling that puzzle is obviously a lot harder. That's the whole point, right? So imagine if some of the pieces go missing or a few tabs are torn. It could be nearly impossible, and for a simple machine, it IS impossible. That's what using non-ASCII does. Everything still goes in the box. The engine can even load portions and play it, but the algorithm that puts it all back into a data folder can't tolerate any errors. All it can do is exit, and there you sit.

Hope that makes more sense.

DC

 

[porksauceboi]

It seems really counterintuitive I know, but on a technical level, packing is MUCH simpler than unpacking. Think of it like an old fashioned puzzle. The original maker takes a big picture and cuts it into a number of smaller pieces, which then fit neatly inside a box. Pretty simple. Just slice things up and smash it in there. If there's a bad cut or some tabs tear off, it still fits no problem because the packer doesn't have to understand anything about what it's packing.

Reassembling that puzzle is obviously a lot harder. That's the whole point, right? So imagine if some of the pieces go missing or a few tabs are torn. It could be nearly impossible, and for a simple machine, it IS impossible. That's what using non-ASCII does. Everything still goes in the box. The engine can even load portions and play it, but the algorithm that puts it all back into a data folder can't tolerate any errors. All it can do is exit, and there you sit.

Hope that makes more sense.

DC

Makes a lot of sense! Thanks again for being super helpful! Cheers

 

[Borkjh]

 

[DCurrent]

View attachment 14735

@Borkjh,

Please do not post screenshots without context. What is your question?

DC

 

[Borkjh]

not work.

 

[Smart Kitty]

use paxplode

 

[SkierRay]

apparently it may result in the same failure via paxplode for invalid argument due to encrypted pak file. FYI

 

[DCurrent]

apparently it may result in the same failure via paxplode for invalid argument due to encrypted pak file. FYI

Unless I'm mistaken, that's not the case here. It looks like non-ASCII characters were used in some of the file names. That's asking for a problem. Sometimes it works, sometimes not. Always use ASCII characters, and only this subset. Otherwise there's no guarantee you can pack or explode properly:

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
a b c d e f g h i j k l m n o p q r s t u v w x y z
0 1 2 3 4 5 6 7 8 9
_ -

If it's someone else's project, then you're just out of luck, and will need to contact them about it.
DC

 

[SkierRay]

seemed to me, some modders of Korean project like the post would protect creation of characters and sprites via encryption or editing hex-values from unpacking and extracting. If the case is for nocheats modification, better off another way to try.