Engine.dll HF

[Napster321]

downloaded from m0nster.io -> 273 engine.dll [UNP] [by Deazer] & 273 protocol system, I patched the system and I'm trying to login but I get protocol error on server select.




the fact is that the problem comes from unpacked engine.dll since the protocol is 273


and it works fine with the packed engine.dll

any ideas?

[Alay]

unpack ur engine.dll with u can login by urself?

[n3k0nation]

This patch is clear (without killed GG or other modifications).

[Napster321]

Сообщение от n3k0nation

This patch is clear (without killed GG or other modifications).

i know this, what i tried to do and what i need is, patched system with unpacked engine.dll.

[Deazer]

1. One more time check protocol version on server side

2. Shutdown GameGuard from Core.dll
2.1 Download LordPe (setpu ) > Right Mouse Button > Load into PE editor
2.2 Select Directories > ExportTable > ....
2.3 Find ?GL2UseGameGuard@@3HA > edit > Copy RVA > Go to main window of Load into PE editor > Select FLC > insert RVA > Press DO > Than Hex Edit
2.4 Edit string looking like FF FF FF FF 00 01 00 00 to FF FF FF FF 00 00 00 00
2.5. Save and Enjoy

3. Change key in l2.exe to be able to read/change (and convert files with new key) the dat files and l2.ini (change addr, default addr=authd.lineage2.com)

[Napster321]

Сообщение от Deazer

1. One more time check protocol version on server side

2. Shutdown GameGuard from Core.dll
2.1 Download LordPe (setpu ) > Right Mouse Button > Load into PE editor
2.2 Select Directories > ExportTable > ....
2.3 Find ?GL2UseGameGuard@@3HA > edit > Copy RVA > Go to main window of Load into PE editor > Select FLC > insert RVA > Press DO > Than Hex Edit
2.4 Edit string looking like FF FF FF FF 00 01 00 00 to FF FF FF FF 00 00 00 00
2.5. Save and Enjoy

3. Change key in l2.exe to be able to read/change (and convert files with new key) the dat files and l2.ini (change addr, default addr=authd.lineage2.com)

I did disabled gg,patched system,checked server side.

[Deazer]

ahhh, I think some problems with realization on your core config Allowed Protocol revision. Try keep only one - 273. Or change priority like 273;271 etc.

[Napster321]

Сообщение от Deazer

ahhh, I think some problems with realization on your core config Allowed Protocol revision. Try keep only one - 273. Or change priority like 273;271 etc.

I did and it's the same error again, I think it's something related on engine.dll
the one you unpacked, have you tried and working fine with 273 protocol?

[Deazer]

Сообщение от Napster321

I did and it's the same error again, I think it's something related on engine.dll
the one you unpacked, have you tried and working fine with 273 protocol?

with engine.dll all ok, tested (anyway - if it did not match the client protocol (l2bin/nwindow/engine etc.), he would simply not started) . Have no more ideas

[Napster321]

Сообщение от Deazer

with engine.dll all ok, tested (anyway - if it did not match the client protocol (l2bin/nwindow/engine etc.), he would simply not started) . Have no more ideas

If it's not a waste of time for you testi it with 273 protocol HF because my tests show that the client is using 746 protocol...