Problem with extracting a script from Little Busters

[NatoYU]

Hi, you have a pretty good toolkit. I tested it on Loopers and it opened and packaged the script from it perfectly. I wanted to try it on Little Busters (I'm more interested in it). I don't understand what order to do it in? I moved SCRIPT.PAK, LuckSystem.exe and LB_EN (which contains OPCODE.txt) to one folder.

I decided to enter this command (with path replacement)

lucksystem pak extract -i data/LB_EN/FONT.PAK -o data/LB_EN/5 --index 5

Nothing worked.

I entered the following:

lucksystem pak replace -s data/LB_EN/FONT.PAK -o data/LB_EN/FONT.out.PAK -i data/LB_EN/temp

I got a huge number of SEEN files (whose format is not even .txt) and inside them text mixed in a pile with encrypted text.

I'm not even talking about how to turn all this back into .PAK.

"lucksystem pak replace"? Which command? Why so many commands? How to use it all?

With images, I expect even more problems. Even in Loopers I could not open the MANUAL.PAK containing images in cz format.

[G2-Games]

Hello. The SEEN files are how the script is stored, it is not plain text, and can be decoded using the command lucksystem script decompile. Also check out my similar project if you wish, which has some different utilities for extracting PAK files and reinserting data into them.

[ModzabazeR]

may I ask which .py file to use with LB_EN script decompilation?

[thedanill]

may I ask which .py file to use with LB_EN script decompilation?

LB was one of the first games, and support for it was added even before the switch to the Python plugin system. You can’t use it from the CLI, the only way is to call the right functions directly in code (example).

TBH, Little Busters is kinda weird — the engine was modified in some pretty unique ways just for this game, stuff you don’t see in others. I tried messing with it a while ago, and if I remember right, there are some issues with LB support in LuckSystem (like some files would fail to decompile).

I couldn’t really solve those issues, so I just ended up writing my own tool. It doesn’t look as good as LuckSystem and it only works with Little Busters, but at least it’s fully functional.

[ModzabazeR]

may I ask which .py file to use with LB_EN script decompilation?

LB was one of the first games, and support for it was added even before the switch to the Python plugin system. You can’t use it from the CLI, the only way is to call the right functions directly in code (example).

TBH, Little Busters is kinda weird — the engine was modified in some pretty unique ways just for this game, stuff you don’t see in others. I tried messing with it a while ago, and if I remember right, there are some issues with LB support in LuckSystem (like some files would fail to decompile).

I couldn’t really solve those issues, so I just ended up writing my own tool. It doesn’t look as good as LuckSystem and it only works with Little Busters, but at least it’s fully functional.

That is some useful information, thank you. I'm just chilling to see how LucaSystem engine works while waiting for Summer Pockets Reflection Blue to come out, while LB is the only one game in my steam library that uses this engine lol.

I willl take a look at your tools, thanks again.

[yoremi-trad-fr]

Hello, I had a similar problem very recently with LB Steam. I updated the sources (fork), and now LB Script Pak decompiles completely. (Fork V3.1 — Patch 1: Little Busters EN script decompile fix)