+- LCKB (https://lckb.dev/forum)
+-- Forum: ** OLD LCKB DATABASE ** (https://lckb.dev/forum/forumdisplay.php?fid=109)
+--- Forum: Off-Topic (The Outer World) (https://lckb.dev/forum/forumdisplay.php?fid=198)
+---- Forum: General Discussion (https://lckb.dev/forum/forumdisplay.php?fid=147)
+---- Thread: [Release] Last Chaos Launcher EP1 & EP2! (/showthread.php?tid=618)
- someone - 01-30-2012
Suggestion for patching.
Use the function ReadProcessMemory, has same parameters as WriteProcessMemory.
If the client Unpacks correctly extract the byte from the Offset, and verify if it matches with the your data;
byte in;
ReadProcessMemory(PROC_HANDLE, offset, &in, sizeof(byte), null);
if(in == 0x75){
byte x=0xEB;
WriteProcessMemory(PROC_HANDLE, offset, &x, sizeof(byte), null);
Console.WriteLine("Done\n");
}
else{
Console.WriteLine("Wrong version or is Allready patched.\n");
}
- HateMe - 01-30-2012
Suggestion for patching.Use the function ReadProcessMemory, has same parameters as WriteProcessMemory.
If the client Unpacks correctly extract the byte from the Offset, and verify if it matches with the your data;
byte in;
ReadProcessMemory(PROC_HANDLE, offset, &in, sizeof(byte), null);
if(in == 0x75){
byte x=0xEB;
WriteProcessMemory(PROC_HANDLE, offset, &x, sizeof(byte), null);
Console.WriteLine("Done\n");
}
else{
Console.WriteLine("Wrong version or is Allready patched.\n");
}
thx, the byte in willl be always 0x75 ? i think for DES is another right?
and i will take the timing full out with just an pop up to patch yes/no
- someone - 01-30-2012
thx, the byte in willl be always 0x75 ? i think for DES is another right?and i will take the timing full out with just an pop up to patch yes/no
For DES will not change, (I think for XOR the same), but to be sure, put in the configuration another field called data, and compare the data from the memory.
The byte will change, over time, usually you can see that byte is when you look at the Offsets.
- HateMe - 01-30-2012
ty someone
Changes are done uploadet and working updated the tut also
how to read the 1546.cfg file:
try
{
BinaryReader bi = new BinaryReader(File.Open(Version + ".cfg", FileMode.Open));
IPAdress = bi.ReadUInt32();
XORDec = bi.ReadUInt32();
XOREnc = bi.ReadUInt32();
DESPatch = bi.ReadUInt32();
IPData = bi.ReadByte();
XORDecData = bi.ReadByte();
XOREncData = bi.ReadByte();
DESData = bi.ReadByte();
bi.Close();
}
catch (Exception e)
{
MessageBox.Show(e.Message);
}
if more ideas let me know
- HateMe - 02-07-2012
ok i made a little change i not use anymore the ChilkatDotNet4.dll to extract the .zip files!
usign now the Shell32
so the Launcher is not anymore so big bc he not kontains anymore the Chilkat.dll, i have tested it only on W7 x64 if some1 could give feedback if the new one is workign on 32 bit as well would be nice.- Wizatek - 02-10-2012
Sadly on 1548 it doesnt work anymore.
Probably the packer is more agressive now.
- HateMe - 02-10-2012
oO waht you done that this happened?
they have made no changes to the Engine.dll since version 1545 or 1546
- someone - 02-10-2012
Sadly on 1548 it doesnt work anymore. Probably the packer is more agressive now.
Still works, Just patched today.
- Wizatek - 02-11-2012
haha i just did like u said.
copied the launcher.exe into the usa client, then start it. it asks to patch and i click yes.
and then that message pops up when i start the client
- HateMe - 02-11-2012
haha i just did like u said. copied the launcher.exe into the usa client, then start it. it asks to patch and i click yes.
and then that message pops up when i start the client
hmmm i hope u did klick yes when u saw loginscreen not b4
[EDIT]
i just tryed it now if u hit to fast yes then this error pops up hit "yes" when u see the loginscreen and it will work fine
i will try to find out if its possible to read if the process done loading to let it patch automatical when Nksp.exe full loadet