akiko

Etoimo me odigies tha to breis edw: http://rapidshare.de/files/11804062/eL2Walker10.4.9_-_E-Global.zip.html

Seems it was teh walker version that caused all the trouble! 10.6.0 wouldnt work instead 10.4.9 works fine!

I tried ur token with walker 10.4.9 and it works!

U can find it here--->http://sourceforge.net/project/showfiles.php?group_id=156903 its called la2.gr-patch.10.rar

So whats new with e-global? What does the new l2launcher.exe do? Walker wont work! :( Does anyone have a clue about it? :cry:

i have the same problem with e global.although i have found the correct token ( i think i did) i cant connect.I its something aobut the set.ini pls someone ???? I used the token protocol and found the new token for e-global too, but the walker still wont work!I dont know why! I dont think its the set.ini, because protocol and ip are the same!I am not sure about the port!Also I am curious about the token options.ini if OffSet=$005362F8 GMFix=1 Rename=1 these 3 up here have something to do with the login! Also although I found a new token for e-global windows tell me that the engine.dll hasnt been modified since 3 november 2005! There must be something that has to do with the new l2launcher!

So any solution?Any rumors?

Try also this http://rapidshare.de/files/10890919/TokenProtocol_engine_v2.rar.html U just find the engine.dll and it gives u the token and protocol! Can anyone plz help me with the e-global server and post all data that I can make the bot work there?

I used this programe http://rapidshare.de/files/10890919/TokenProtocol_engine_v2.rar.html to find the protocol and token of my server!It decrypts the engine.dll and i found out that the token changed but my walker still doesnt work! What my server actually changed was the L2launcher into version 1.5 Since then I can not log with my walker! The program i give u is virus free ofcourse 100% So can anyone explain what the hell changed or maybe should we w8 for a new token.exe Oh yeah the program has an exe once u run it, it asks u to find the engine.dll Once u find it it gives u the token and the protocol!

No u are wrong!I have read that its is because the protocol or the token has changed!I am facing teh same problem because my server changed the laucnher and now my bot cant login and gives me the same message!

It worked all fine until my server changed the l2launcher.exe yesterday! The new launcher is 1.5 version!Does anyone know what to do about it?