Jump to content

Recommended Posts

Posted

due to popular demand I'll share the chronicles walkthrough.

 

You will need:

Sauron's Walker Patcher, any version

IG/OOG with the tools required to make them work

 

don't ask for a working pack, I won't do one.

 

 

Login IP 75.126.142.66

Port 2106

Protocol 685

token 6125535B7B262A2D39347D5E232578782D505D61

 

var
XorString : string;
gserver : boolean;
i : integer;

Procedure OnCreate;
begin
XorString := HStr('00 00 00 12 18 85 a0 00');
end;

begin
  if(not _gfromserv) and (_gAbsNumPkt=3) then begin
     gserver := true;
  end;
  if gserver and (length(_gBuff)>3) then begin
     for i := 4 to length(_gBuff) do begin
       _gBuff[i] := Chr(ord(_gBuff[i]) xor ord(XorString[((i-4) and 7)+1]));
     end;
     _gOutBuff:=_gBuff;
  end;
end.

save this as chronicle.fsc in your WP/wpsc folder

 

 

here's from my previous guide on how to setup sauron's WP.

I don't want this to become a tutorial thread on how to use PPC but here are the very basic steps. Open Sauron's WP (WP v5.04F). Proxy P-C tab. Enable the first proxy(S5 Proxy 1) (click the sun).

 

Now click on [sun] P-C ??????. A new window will open.

 

Topmost, there is a row of 4 buttons(???????,???????,Copy,????????). Press the first one. Then fill name, Host/IP, Port and press [ OK ]. IP and port have to be the ones mentioned earlier. The name can be anything.

 

Now, select your new entry. The listbox below the one with server entries should have 3 rows starting with red. Select the first one, the [...] - ???? ????????? next to the [x] button will now be enabled. Press [...] - ???? ???????, locate the script. You may now close the PC window. (Keep the main window opened obviously.)

 

In OOG options, Basic Options tab, add a new proxy IP 127.0.0.1 port 1777(if you kept WP's default). ID and password don't have any use. You may want to put an ID and PW anyway(they don't change anything) because walker won't save proxy entries in its ini's unless you give a random ID/PW pair.

 

note: 75.126.142.66 is the login IP for OOG but also chronicle's lower rate

add a filter for 75.126.142.67 with the script if you play on Genesis.

 

At the time of writing this, this works so if you get any problem, you are doing it wrong.

 

Posted

thx a milion times slt :D

 

k I get

 

Login loginserver fail

 

now my set file is like this

 

[DEFAULT]

CountryList=L2Chronicles

DefaultCountry=0

DefaultServer=0

DefaultCharacter=0

DefaultAccount=

DefaultPassWord=

[L2Chronicles]

LoginServerIP=75.126.142.66

LoginServerPort=2106

ProtocolVersion=685

ServerList=[1]Underground

 

 

I did the steps like you said afaik I can post SS's if you cant help me like this :P

 

IG aint working either, it says it is veryfied but it is scrambled same as if you login normaly with walker, party info is foked up, map is showing random stuff, etc

 

Posted

DONT WORK

 

I'm sure this is not the correct token, Im using another and works but I got "Login GameServer Timeout"

 

And Im almost sure that the scrip dont work!

 

This guide dont work.

Posted

damn very sorry, the token was wrong

 

edited first post ;/

 

 

as for IG, it cannot work with the L2Chronicle client, you will have to use a clean system folder and mod it for the protocol and token but this is slightly trickier, you might want to make sure the proxy is setup correctly with just OOG first

 

It does work with the correct token, that kuako300 should go spam somewhere else.

Posted

22:22:17 WP v5.07F © Sauron

22:22:17 Link LoginServer Succeed.

22:22:22 Login LoginServer Succeed.

22:22:23 服务器[01]当前在线率:4.16%,能否登陆:能

22:22:26 Link GameServer Succeed.

22:22:26 ->Login GameServer Fail.

 

this is what I get now I tryed to login many times, used the auto login :P

Posted

OMG I wasnt spaming I just was saying dont work because ur old token didnt work.......

 

btw thank you for ur guide :)

 

and I ever get Login GameServer TimeOut

 

I'm using L2Walker 10.7.1 and WP507F

Posted

you mean this?

 

neimenovanatd1.jpg

 

now I'm getting

 

 

22:56:29 WP v5.07F © Sauron

22:56:29 Link LoginServer Succeed.

22:56:33 Login LoginServer Succeed.

22:56:33 服务器[01]当前在线率:3.92%,能否登陆:能

22:56:36 Link GameServer Succeed.

22:56:37 LoginFail.20.

22:56:37 ->Login GameServer Fail.

 

22:57:06 WP v5.07F © Sauron

22:57:06 Link LoginServer Succeed.

22:57:11 Login LoginServer Succeed.

22:57:11 服务器[01]当前在线率:4.04%,能否登陆:能

22:57:14 ->Link GameServer Fail.

 

lol :S

 

I'm using walker 10.6.6 and token patcher by hint

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

    • Added the protection module to the demo.   DDoS Guard Pro v2.0 is a system protection module for PlayMMO CMS designed to reduce the load on the website during HTTP floods, bot activity, suspicious frequent requests, and attacks on individual pages or API methods. Unlike simple global limiters, DDoS Guard Pro v2.0 supports flexible rules based on routes and HTTP methods. This allows you to block the entire site in a targeted manner, rather than blocking the entire site equally. You can set up protection for specific areas of the site, such as login, registration, APIs, administration, forms, and other sensitive areas. What is the purpose of the module? DDoS Guard Pro v2.0 helps protect your site from basic L7 attacks at the HTTP request level. The module is useful when your site receives: frequent requests from a single IP address; HTTP page floods; login or registration form flooding; automatic requests from bots; URL scanning; frequent API requests; suspicious activity spikes; load on individual CMS methods or pages. The module helps to reduce the load on PHP and CMS by limiting suspicious activity before it starts to create a serious load on the site. Main features Per-route and per-method Rate Limit In the new version, protection is configured not only globally, but also according to specific rules. You can set limits separately for: GET; POST; PUT; PATCH; DELETE; ALL. This allows you to flexibly protect different parts of your website. For example: for the login page, you can set a strict limit; for registration, you can set a separate limit; for the API, you can set a limit for reading and a limit for changing data; for regular website pages, you can set a soft limit or not set a limit at all. This approach reduces the risk of accidentally blocking regular users and makes the protection more accurate. Flexible rule system The module supports setting rules in the following format: METHODS|PATTERN|LIMIT|WINDOW|BURST_LIMIT|BURST_WINDOW|BLOCK_SECONDS|IDENTITY|NAME Example of rules: POST|*login*|10|60|5|10|600|ip|login_post POST|*register*|8|60|4|10|600|ip|register_post GET|*api*|300|60|80|10|120|ip|api_get PUT,PATCH,DELETE|*api*|80|60|20|10|300|ip|api_write This allows you to specify exactly: which HTTP methods to protect; which URLs or URL patterns to consider; how many requests are allowed; over what time period; what burst limit to use;  how many seconds to block the offender;  by which ID to count the limit;  what the rule is called. Burst protection against sharp spikes  In addition to the regular request limit, the module monitors sharp spikes of activity.  This is useful when a bot makes many requests in a few seconds. In this case, the protection can be activated faster, without waiting for the overall limit per minute.  Burst protection is especially useful for: authorization pages; registration; API; search; data submission forms; administrative sections. Support for different types of requests DDoS Guard Pro v2.0 works not only with POST requests. The module can control: GET — regular pages, API requests, search; POST — forms, login, registration, data submission; PUT — updating data via API; PATCH — partial data update; DELETE — data deletion; ALL — all methods at once. This makes the module suitable not only for regular sites, but also for CMS with API, personal accounts, game panels and administrative actions. Limit storage: Redis, APCu and file fallback In the new version, the module supports several options for storing temporary data. Available modes: Redis; APCu; file fallback. The auto mode tries to use the most suitable option: Redis; APCu; file storage as a fallback. Redis or APCu are suitable for more efficient operation, while the file storage is left as a fallback option for simple hosting environments that do not have additional extensions. JSONL logging The module records protection events in JSON Lines format. Logs are saved in the following file: storage/logs/ddos_guard.jsonl This format is more convenient than a regular text log, because each event is stored as a separate JSON record. The logs can record the following information: event time; IP address; HTTP method; URL; name of the triggered rule; reason for blocking; number of requests; action status; user-agent; protection mode. The JSONL format is convenient for analysis by external tools, log agents, and monitoring systems. Prometheus metrics DDoS Guard Pro v2.0 adds an endpoint for receiving metrics in Prometheus format. Endpoint: /?ddos_guard_metrics=TOKEN The token is set in the module settings. Metrics allow you to track: the number of processed requests; the number of rule activations; the number of blocks; activity by limits; protection events; module status. This allows you to connect monitoring and configure alerts so that the administrator can see when suspicious activity starts on the site. LOG ONLY mode The module has a LOG ONLY mode. In this mode, DDoS Guard Pro does not block users, but only records events and potential triggers in the log. This mode is recommended to be used after installation, in order to first see which rules are triggered, and only then to enable the real blocking.  This helps to avoid too strict limits and random blocking of regular users.  Support for Cloudflare and proxy  The module supports working behind Cloudflare or another reverse proxy.  With proper configuration, it is possible to take into account the real IP of the user, and not the IP of the proxy server.  This is important for sites that use:  Cloudflare; nginx reverse proxy; load balancers; CDN; hosting proxy protection. Nginx-recommendations DDoS Guard Pro v2.0 contains an example nginx-config: modules/ddos_guard/nginx-ddos-guard-example.conf This allows you to use the module as an additional application layer of protection, and to move the main coarse limits to the nginx level. Recommended protection scheme: Cloudflare / nginx / firewall → DDoS Guard Pro → PlayMMO CMS This approach is more correct than trying to solve all problems only at the PHP level.
  • 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..