Jump to content

Recommended Posts

Posted

WSS 2.7 http://rapidshare.com/files/110214004/WSS_2.7.rar.html

WP PPC http://saur.x33.ru/wp.html

set.ini

[l2-gof.pl]
LoginServerIP=91.121.100.48
LoginServerPort=2106
ProtocolVersion=828
ServerList=[01];[02];[03];
UseProxy=1
ProxyServerIP=127.0.0.1
ProxyServerPort=1777
doEncDec=1
doOutEnc=1
doRSAEnc=1
isC4=0

Unpack wss into walker directory.

Create file (or change) set.ini (see in code)

Run PPC and bind scipt fix02.fsc for 91.121.100.48:7777

Run walker and set socks5 127.0.0.1:1777 for game server. (DO NOT login server!)

Run WSS and double click on l2walker.exe (left window) - Caption walker changed to [Patched]

Run walker and enjoy

 

Posted

Well I did it just like dmitry501 said but changed the IP to the one I need but it always fails to get to the login server.

 

walker01ll1.th.jpg walker02ux4.th.jpg walker03kc3.th.jpg

 

set.ini

[Private]

LoginServerIP=88.198.51.242

LoginServerPort=2106

ProtocolVersion=828

ServerList=[1]Bartz;[2]Sieghardt;

UseProxy=1

ProxyServerIP=127.0.0.1

ProxyServerPort=1777

doEncDec=1

doOutEnc=1

doRSAEnc=1

isC4=0

 

Any idea wheres my mistake?

Posted

:))))))))))))    work now!!!!!!

 

I dont use fix02.fsc, i put in ppc all ON, double ckick walker, then wss -> path --> run walker

 

[Private]

LoginServerIP=L2authd.lineage2.com    <-- i changed ip adress for this and work now ^^

LoginServerPort=2106

ProtocolVersion=828

ServerList=[1]Bartz;[2]Lionna

UseProxy=1

ProxyServerIP=127.0.0.1

ProxyServerPort=1777

doEncDec=1

doOutEnc=1

doRSAEnc=1

isC4=0

 

------------------------

 

Thk everybody

Posted

Do not use xzCrk.

This is change protocol to 831 (hello chinese :D )

Use WSS 2.7 - correct verify bots 10.8.6 (IL) - 10.9.0 (Kamael), and packet correcter

http://www.maxcheaters.com/forum/index.php?topic=22661.msg154482#msg154482

http://www.maxcheaters.com/forum/index.php?topic=22661.msg154056#msg154056

Here's what I did:

1. Run WSS.exe

2. Run Walker and log in

I get:

L2Walker was patched for USA (port: 2106, protocol: 828)

WSS v2.7 by Sh00rGo

10:41:08 Link LoginServer Succeed.

10:41:08 服务器[01]当前在线率:27.33%,能否登陆:能

10:41:11 Link GameServer Succeed.

10:41:16 ->Enter Char[1].

10:41:19 Packet Error ...

 

Now, I've created text file, renamed it to Fix02.sc

put this inside and saved

BEGIN

  If (_gBuff=#$02+#0) then gBlockPacket;

END

 

I have turned on S5 Proxy 1 in WP and embedded Fix02.sc into that via PPC Panel

But still getting the same Packet Error...

 

What else can I do?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



  • Posts

    • <dailyReward days="28" autoOpen="true" minimumOnlineTimeSeconds="30" oneRewardPerIP="true" resetIfMissDay="true">   For now, I have these settings in the XML—this is the V1 version I created, though I plan to make further improvements over time. Of course, I’ll also add more protections—MAC, HWID, and perhaps others like account-based restrictions—to make it more secure. We can also implement non-tradable items to further enhance the system's security. I’ll keep posting updates and refining both the system and the interface. I might make a video tomorrow; if you look at the top, you'll see the "auto-open" feature can be toggled on or off, allowing users to rely solely on the `.daily` command. Cheers! Note: If I sell it in this state, I’ll provide support and roll out updates to users. I’m not forcing anyone to buy anything; I’d even provide the patch files so that anyone with the necessary skills can add features, modify it, or improve it further.
    • If the problem is that the target is lost, the action of aiming at another character, upon losing collision, does not allow aiming.   This one works as it should, allowing you to target characters
    • MICROTEXT AND WATERMARKS BREAK MOST RENDERINGS Microtext and watermarks aren’t just small decorative details. They are one of the most common reasons a document fails verification, even when it looks decent at first glance. The issue is that these elements are almost impossible to reproduce “by eye.” Microtext requires precise geometry and legibility at a very small size, while a watermark needs the correct density, transparency, and accurate placement relative to other security features. Any deviation becomes obvious during detailed inspection. ▪ What’s most often done wrong: - microtext is drawn too thick or blurry - the watermark is made either too visible or almost invisible - the positioning between microtext and watermark is ignored - the original printing technology isn’t taken into account when choosing density and shape - The stronger the document’s security features, the less room there is for approximation. What matters here isn’t visual similarity, but accurate reproduction of the original technical characteristics. If your document contains microtext and watermarks, this is always an area that requires extra attention. Write to us in DMs. We’ll review your case and point out exactly which details need the highest precision during rendering. › TG: @mustang_service_ms ( https:// t.me/ mustang_service_ms ) › Channel: Mustang Service ( https:// t.me/ +JPpJCETg-xM1NjNl ) #drawing #microtext #photoshop #editing #watermarks
    • GoldRush launches tomorrow! July 18 16:00 GMT+3 Europe / International Register your account in the website, connect wallet and be ready to dominate!
  • Topics

×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..