hey guys thanks for help in advance. I run a grand chase private server for myself. Im trying to extract KOM files to edit the server. Before i stopped working on it BMS used to work and extract the files. 
I get the error now. " unknown algorithm 5e675234 at offset 0x0000000000005c6c (0 -> 207), contact me"
Not sure why ill post the script i got with the program that used to work... If you can find whats wrong i appreciate it... Its stressful
"# KOM archives (Elsword, GrandChase) 0.1.1
# script for QuickBMS http://quickbms.aluigi.org
quickbmsver 0.4.6a
idstring "KOG "
get SIGN string
set VER string SIGN
string VER &= "V."
string VER -= -5
string SIGN >>= " MASSFILE"
goto 0x34
get FILES long
if VER == "V.0.1"   # it's the same of 0.2
    set VER string "V.0.2"
endif
if SIGN == "THINCLIENT"
    if VER == "V.0.2"
        get DUMMY long
        get SIZE long
        get DUMMY long
        savepos OFFSET
        math OFFSET += SIZE
        for i = 0 < FILES
            get DUMMY long
        next i
    else
        print "Error: unsupported KOM version (%VER% / %SIGN%)"
        cleanexit
    endif
    for i = 0 < FILES
        get NAMESZ byte
        getdstring NAME NAMESZ
        get SIZE long
        get ZSIZE long
        get ZIP byte
        if ZIP == 0
            log NAME OFFSET SIZE
        else
            clog NAME OFFSET ZSIZE SIZE
        endif
        math OFFSET += ZSIZE
    next i
else
    if VER == "V.0.2"
        get DUMMY long
        savepos BASE_OFF
        math TMP = FILES
        math TMP *= 0x48
        math BASE_OFF += TMP
    elif VER == "V.0.3"
        get DUMMY long
        getdstring DUMMY 8
        get XMLSZ long
        savepos OFFSET
        log MEMORY_FILE OFFSET XMLSZ
        math OFFSET += XMLSZ
    elif VER == "V.0.4"
        get KEY long
        getdstring DUMMY 8
        get XMLSZ long
        savepos OFFSET
        if KEY == 0xb290207
            set KEY long 0x6e0acdeb # 64bit number (%lld)
        else
            print "Error: unkown relative key value (%KEY%)"
            cleanexit
        endif
        encryption sha1 ""
        string KEY E= KEY
        encryption bf_ecb QUICKBMS_HASH "" 0 20
        log MEMORY_FILE OFFSET XMLSZ
        encryption "" ""
        math OFFSET += XMLSZ
    else
        print "Error: unsupported KOM version (%VER% / %SIGN%)"
        cleanexit
    endif
    for i = 0 < FILES
        if VER == "V.0.2"
            getdstring NAME 0x3c
            get SIZE long
            get ZSIZE long
            get OFFSET long
            math OFFSET += BASE_OFF
            set ALGO long 0
        else
            findloc TMP string "Name=" MEMORY_FILE
            math TMP += 4
            goto TMP MEMORY_FILE
            for j = 0 < 6
                findloc TMP string "=" MEMORY_FILE
                math TMP += 2
                goto TMP MEMORY_FILE
                getct TMP string 0x22 MEMORY_FILE
                putarray 0 j TMP
            next j
            getarray NAME 0 0
            getarray SIZE 0 1
            getarray ZSIZE 0 2
            getarray ALGO 0 5
        endif
        if ALGO == 0
            clog NAME OFFSET ZSIZE SIZE
        else
            print "unknown algorithm %ALGO% at offset %OFFSET|x% (%ZSIZE% -> %SIZE%), contact me"
            cleanexit
        endif
        math OFFSET += ZSIZE
    next i
endif
"
			
			
									
						
										
						Help with QuickBMS, used to work, came back and its not working anymore...
- 
				prinnydewd6
- Posts: 1
- Joined: Sun Aug 30, 2020 3:21 pm
- 
				aluigi
- Site Admin
- Posts: 12984
- Joined: Wed Jul 30, 2014 9:32 pm
Re: Help with QuickBMS, used to work, came back and its not working anymore...
Do you mean that the script 0.1.1 you post works on your file and the current 0.1.3 doesn't?
Or do you mean that older versions of quickbms.exe worked and now no longer?
If you have a sample kom file that gives you that problem I can check it.
			
			
									
						
										
						Or do you mean that older versions of quickbms.exe worked and now no longer?
If you have a sample kom file that gives you that problem I can check it.