Jump to content
MaxCheaters Official Group on Discord
Top.MaxCheaters.com is now OPEN – Lineage 2 Top Listing

How to get to Dion using a SOE

MASTROPOS

By MASTROPOS
in Hacks & Cheats [English]

 Share

Recommended Posts

MASTROPOS Newbie

MASTROPOS

Posted
Posted

How to get to Dion using a SOE

I will attempt to explain how to bypass teleporting to towns and wasting adena just to get to dion. It will only cost you a Scroll of Escape to get to dion. Note that this was attempted and repeated many times on a private server that is using official server files and not the L2J emulator.

 

Step 1: First thing you need to do is buy 1 Scroll of Escape which will cost you 400-500 adena in a shop.

 

Step 2: *Note* You need to talk to any of the Gatekeepers that offer to teleport you to Monster Derby Track for free *Note* Teleport to the monster derby track for free from the Gatekeeper.

 

Step 3: You will arrive at the monster derby track, when you arrive you should end up at the North End of the track by the fence. In front of you, you will see the Race Manager and Lottery Ticket Seller. Then if you look outside of the fence you will see the Race Track Gatekeeper standing to the east of a rock with moss on it.

 

Step 4: At this point you should be standing right in front of the Lottery ticket seller. Now walk east towards the broadcasting tower which is now in front of you,but dont go up to it, or else you walked too far..... Make the first left (go north) at the pavillion/wood shelter thingy. You are now looking at another fence.

 

Step 5: Put your character as close to the corner of the fence as possible. I am talking about the corner of the fence that is MOST NORTH and MOST WEST. Or in other words...the left corner.

 

Step 6: You need to use the action (Attack) for this to work. So either pull it up by pressing "C" or equip it on your hotkeys, because you are going to need to spam it.

 

Step 7: Now that you are in the corner, you need to set your character up to do this. On the"WEST SIDE" of this fence you will see the corner post, and to the south of this corner post, you will see another support post. Between these 2 posts is a small ground post. You should align your character up between this ground post and the corner pavillion/wood shelter post so that your character is standing directly in between the ground post and the pavillion post.

 

Step 8: Now move your camera so that you can see the Race Track GateKeeper. Click her once just so that you target her.

 

Step 9: Now that she is targeted and your charcter is set up. Hold down the attack action on your hotbar, or just spam click it if you are doing it from the action menu. You character will start to run to her but get blocked by the fence. NO WORRIES, just keep it held down, or just keep spamming it. This is called bugging. Your charcter should start to run sideways along the fence or just kind of have a seizure looking thing. After 5-15 seconds of him doing this, the dialog screen should pop up for the Race Track Gatekeeper.

 

Step 10: Now choose, "Go to the Monster Derby Track! (Free of charge). You will be teleported back in to the track.

 

Step 11: Simply talk to the Race Manager, and select, Exit the monster race track.

 

Step 12: You are now outside the derby track standing next to the gatekeeper in Dion Territory. In the server I am in, when I use a SOE from this position I get directly sent to Dion and not Floran. But if you get sent to Floran no worries, it takes 1 minute to run to dion all for the cost of 1 SOE.

 

 

I hope this little bug helps everybody save lots of adena from stupid traveling costs. I have saved well over 100k already since I like to move from town to town a lot without running.

 

lostos Newbie

lostos

Posted
Posted

This is an old trick, i dunno where u got all these old tricks mastro (maybe I know), nevertheless, it works, but it is stupid cuz you spend all that time just to save some bucks. It takes too much damn time! (Monster race track is in giran territory, if u use soe, u get to giran)

MASTROPOS Newbie

MASTROPOS

Posted
  • Author
Posted

lostos when you play official you have no so much adena ...for f*(@#+! soes...

go play official and than say It takes too much damn time!

 

 

PS:my english sux

lostos Newbie

lostos

Posted
Posted

hohoho, yes man I play in off. What did you think, I 'm just a random guy? I have a lot of money, and you know what? I always had enough money to teleport. You don't have to go to dion from lvl 1 or something, do you?

  • 3 weeks later...
  • 5 weeks later...
Guest
This topic is now closed to further replies.
 Share
Go to topic listing


  • Posts

    • FunBasec
      PlayCMS is a website management system for Lineage 2 gaming

      By FunBasec · Posted

      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.
    • eMommy
      Needing DEV.

      By eMommy · Posted

    • RMTgold
      Buying & Selling POE & POE2 Divine-Mirrors

      By RMTgold · Posted

      PAYPAL& BINANCE
    • RMTgold
      Buying & Selling Wynncraft Stx

      By RMTgold · Posted

      PAYPAL& BINANCE
    • RMTgold
      Buying & Selling Torn City Cash

      By RMTgold · Posted

      PAYPAL& BINANCE

  • 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..