LST: Difference between revisions
No edit summary |
No edit summary |
||
| Line 33: | Line 33: | ||
LC-ScriptEngine ver1.0 | LC-ScriptEngine ver1.0 | ||
From watching file access to 'lcsebody.lst', it first reads from offset 0 with a length of 4. Then it reads the rest of the file in 76 byte chunks. This could suggest the first 4 bytes are file count and then the rest is file entries which would mean there is 598 files inside this games lcsebody. | From watching file access to 'lcsebody.lst', it first reads from offset 0 with a length of 4. Then it reads the rest of the file in 76 byte chunks. This could suggest the first 4 bytes are file count and then the rest is file entries which would mean there is 598 files inside this games lcsebody. Taking a random guess outta nowhere, it's almost like it adds 0x01 to every byte. o.o It... can't be that easy, can it? ^^; | ||
Revision as of 03:07, 16 July 2014
Used in the following game(s):
- Conquering the Queen
- Cosplay Alien
- Edelweiss
- Guilty ~The SiN~
- Harem Party
- Harukoi Otome
- Koihime Musou
- Magical Teacher
- Sandwiched by my Wife and her Sister
- Sex Slave is a Classmate, My
- Shera, My Witch
- Slave Witch April
- Suck my dick or die!
Common File names: lcsebody SoundPackSE
Most likely is index data for the extension-less file that accompanies this file with the same name. Index data, at the very least, looks obstructed....is that the right word? O.o I've been using that a lot but I feel like I have the wrong word.... Something like that word but with an F in it that means it hides, or masks the code? Obfuscation? :O
Research
Using the game 'Conquering the Queen' for research.
File names found.
lcsebody -> NECEMEM.SNI
Engine details.
LC-ScriptEngine ver1.0
From watching file access to 'lcsebody.lst', it first reads from offset 0 with a length of 4. Then it reads the rest of the file in 76 byte chunks. This could suggest the first 4 bytes are file count and then the rest is file entries which would mean there is 598 files inside this games lcsebody. Taking a random guess outta nowhere, it's almost like it adds 0x01 to every byte. o.o It... can't be that easy, can it? ^^;