aluigi wrote:
Are you using the script 0.4.25?
Currently no idea about that error, the UE4 script should be quite stable even with the overhit workaround.
I use latest download from your web.
spiritovod wrote:
aluigi, the game is using two identical magics. With the previous script version it's omitting stuff through backward compatibility to the second magic, where workaround is applied. With the new approach it's trying to find magic upward and find first one, which will not work. Setting initial magic offset to 0x2C and then searching upward should resolve this issue, but it also may break other workarounds for similar reasons.
@CriticalError: Use "latest" script from
here, it should work.
which one, attachment have a lot scripts and try with all and same error.
tested
latest_UE4_bms-script.bms with same result as screenshot posted.
unreal_tournament_4_0.4.26_paks_only.bms tested and got this error
offset filesize filename
--------------------------------------
The archive is encrypted, select the number of the key to use or type yours:
0: press RETURN for no encryption (Lineage 2 Revolution)
- please insert the content for the variable KEY:
0x4531413146324534414130363643353442443530393046343633454444463538
KEY: E1A1F2E4AA066C54BD5090F463EDDF58
Error: [myfseek] offset 0xe9bbed77286ed4e2 in file 0 can't be reached
Last script line before the error or that produced the error:
50 log MEMORY_FILE5 OFFSET SIZE
others are for others games.