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

Sold

katsu jo
 Share

Recommended Posts

Asmodeus Newbie

Asmodeus

Posted
Posted

Do a fundraising campaign online and set a goal of 300$, when it's done share it for everyone. Either way they're only useful for l2j developers.

Zeeyo Newbie

Zeeyo

Posted
Posted (edited)

What about DB dump or SQL scripts (yeah, you can't classify those as binaries :D)? At least SP declarations!

 

Do a fundraising campaign online and set a goal of 300$, when it's done share it for everyone. Either way they're only useful for l2j developers.

That's a good idea.

Edited by Zeeyo
  • 2 weeks later...
Ghost Newbie

Ghost

Posted
Posted

Do a fundraising campaign online and set a goal of 300$, when it's done share it for everyone. Either way they're only useful for l2j developers.

Yuyup.

*real*savormix Newbie

*real*savormix

Posted
Posted

Do a fundraising campaign online and set a goal of 300$, when it's done share it for everyone. Either way they're only useful for l2j developers.

Don't forget than in fundraising you could even set a larger goal (if you really want to). Still, GD is 3 years old, and seeing what changed in Lindvior, Epeisodion, as well as Ertheia and IO, it looks like that in current L2 there's hardly anything left from GD – not even GD's 4th classes and their skills are in use anymore (according to IDs observed in IO).

And unlike HF, which was last of its kind before major & completely unnecessary changes, GD is in the middle of major and unnecessary changes that were later reverted or reworked.

 

The price could be justified if it was an Epeisodion script pack with those Ertheia/IO html/geo bonuses. But GD… it's like C5. Nobody needs C5/GD, since C4/HF and IL/Ertheia are unquestionably going to be extraordinarily more popular.

 

But this is just my opinion.

 

TL;DR: GD isn't worth 300 USD to me, so I prefer the fundraising scenario, like others.

AlmostGood Enthusiast

AlmostGood

Posted
Posted

glory days was nice cuz of 8 classes only, so olympiad had huge competition even on low online servers.

Classes were changed in Lindvior, but only with name and few skills, 90% of skills is just the same to these on IO update.

 

In general it's not as bad as you say, GD has just less endgame content than IO and miss new race/few changes in skills.

*real*savormix Newbie

*real*savormix

Posted
Posted (edited)

Well, I didn't check if Iss Hiero/DC/Domi is reusing Iss Ench skills, but I'd bet it isn't (despite the fact that the skills do the same). Iss SD got their awakened dances, Iss SM got their awakened songs, Wynn AL got their cats, Wynn SM got their dark servitors, Wynn EM got their unicorns, …

You get the picture. While pretty much all 'divine' skills (before awakening) remain the same as in HF (and these still comprise the majority of player's skills), GDL introduced a lot (relatively) of new 'giant' skills.

 

Oh, and did I mention the not-so-small skill enchant related changes in IO? "Skill" is no longer an ID+level; now it's ID + level + sublevel.

 

I understand, IO does look pretty much like GoD. But then again, I could say IO looks pretty same as GF, because Ruin Imp Elders (isolated example, the correct term would be "all monster ai superclasses") act precisely THE SAME WAY as they did in GF. The free teleport bug is still there in IO as it was in GF. And so on…

 

 

My main point was that the script pack is 3 years old currently. It will only get more obsolete with time, so with the current price it may become more of a decoration than a useful (even if only for l2j) data pack before it finds a buyer. Therefore, crowdfunding.

 

 

P.S. Please consider the fact that I am an interested party and thus the point of view used in my messages may not objectively reflect the way general market perceives the value of the files for sale.

Edited by _dev_
  • 2 weeks later...
  • 2 weeks later...
  • 1 month later...
Erlandys Newbie

Erlandys

Posted
Posted

Do a fundraising campaign online and set a goal of 300$, when it's done share it for everyone. Either way they're only useful for l2j developers.

You should do so, in that case you can bring up more money, and make l2j GoD chronicles to be much better (y)

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


  • Posts

    • Out of Time
      Needing DEV.

      By Out of Time · Posted

      And whats the reason posting this here? GoldMembership in 2026 in MAXC.
    • 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

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