Jump to content

Recommended Posts

Posted

Long time to share something, so lets start

 

This is a unique event for your server, it will run on any pack with no need of addaptions and shits, just add it and it will work

public class NullEvent {
    static
    {    startEvent();
    }
    
    public static void startEvent()
    {    throw new NullPointerException("Null Event started, participation in Giran");
    }
}

What it does? If called properly it will freeze your GS to a point where players will cry for lag and shits, but here is the point, they are wrong! Cause its null event time.

Posted

LOL it working <3 perfect it register and after it ends it give X rewards.. Amazing +1 karma to Xdem and Stacy (they are perfect couple)

 

 

what da  :happyforever:

Posted (edited)

small codes not allowed...

 

I can write in 2 lines a code that would take you 120 lines, crawl back to school

 

 

It's true honey, Xdem is the best boyfriend for you. imagine this:

You wake up in morning next to him in bed, you fondle his arms and you kiss him gently then you wrap the blanket arround your naked body

and you sit on computer where you do some Java with DBO connections sql then he stand up and he come with his coffee on top of you and behind your back

he bend and kiss your head then he softly take the mouse and tell you "honey this line is wrong" ... can u imagine this :3 ?

PERFECT COUPLE....

 
I strongly recommend you to go visit a psychiatrist, he will let you know if you have some treatable problem or if you was born with mental issues
Edited by drake2wow
Posted (edited)

 

I can write in 2 lines a code that would take you 120 lines, crawl back to school

 

 

the problem when you write 2 lines is this:

 

 

Ignorance of the rules is not an excuse for breaking them.

 

General Rules

  • Here you can post any L2J related share, except projects
  • Do not ask for help here. Use proper section for that, here or here
  • Make sure to include the proper prefixes for your topic
  • Always put a simple explanation of what you are sharing
  • Use pastebin or the code tag for your codes (for ex. [ code ] your code [ /code ] without the spaces)
  • If you are not the owner of the share, please add the proper credits, else you will be smitted
  • Do not post simple java strings or stupid configuration codes. Such topics will be immediately locked
  • Badly coded shares will be locked for the sake of java
  • Your code must be tested before you share. We do not want to become a junkyard of non-working stuff
  • Remember that this section is international, so you can not use your own native language. English is required
  • Do not make one single word post like "thanks". Your post should provide feedback whether the code is working or not, else you want to suggest something (code improvements, new features, etc)

 

A share must contain

  • A valid download link
  • As much info as you can (about the share)
  • Pictures if possible
  • Your file must be clean, no viruses and/or backdoors. Use this site to check your file VirusTotal and post the result of the scan
  • Credits

 

A guide must contain

  • Neccessary program(s) used in your guide and general information about the product
  • Always be as more specific as possible in your guide (do not go offtopic)
  • Pictures, if possible, for a better understanding
  • Credits

A tool must contain

  • Detailed information about the program
  • Valid download link
  • Pictures if possible
  • Credits

Updating a share

  • Add UPDATE prefix to your topic' title
  • Make a post with a detailed info about the update to notify the members who use it about the changes (including first post)

 

 

  • Do not post simple java strings or stupid configuration codes. Such topics will be immediately locked
  • Badly coded shares will be locked for the sake of java
  • Your code must be tested before you share. We do not want to become a junkyard of non-working stuff

 

Final conclusion you are ignorant on the rules.

PS: I know you are professional java developer and you have rejected nasa, microsoft proposals for work and yet you choose to be where you are now doing what you do best as I can see from the topic but relax you are not the only one.

Edited by Nightw0lf
Posted (edited)

Oh xDem reached the "throw" lesson. Impressive. 

 

another fanboi, when I reached the throw lesson you was back in high school studying the greek version of pascal for the first time.

 

You know that I'm up to any programming challenge and we both now you're too pussy and amateur to take me on.

 

 

PS: Im pretty sure that you don't even have the proper try catch throw understanding, don't make me embarrass you even more

 

 

the problem when you write 2 lines is this:

 

 

  • Do not post simple java strings or stupid configuration codes. Such topics will be immediately locked
  • Badly coded shares will be locked for the sake of java
  • Your code must be tested before you share. We do not want to become a junkyard of non-working stuff

 

Final conclusion you are ignorant on the rules.

PS: I know you are professional java developer and you have rejected nasa, microsoft proposals for work and yet you choose to be where you are now doing what you do best as I can see from the topic but relax you are not the only one.

 

 

The guy who made the rules has no sense of programming or even l2j thus I'll ignore his rules on this section

Edited by drake2wow
Posted

 

another fanboi, when I reached the throw lesson you was back in high school studying the greek version of pascal for the first time.

 

You know that I'm up to any programming challenge and we both now you're too pussy and amateur to take me on.

 

 

PS: Im pretty sure that you don't even have the proper try catch throw understanding, don't make me embarrass you even more

 

 

 

 

The guy who made the rules has no sense of programming or even l2j thus I'll ignore his rules on this section

 

That's true, they junk nice codes or fixes because of low amount of lines. WTF.

Posted

so hardcore

 

I used a static block to call a public static method and all you have to say is some random shits lol. Make up your life mate, there are always jobs as dish washer jobs in London, tho if you want something close to java you can work as a "Garbage Collector" (iliterally) it really suits you as you have no future in IT

Posted

 

The guy who made the rules has no sense of programming or even l2j thus I'll ignore his rules on this section

 

i guess you mistaken irony for sarcasm

ignoring the rules is why you got banned in first place

plus the conversation level you got is same as toilet paper (used)

its a fable cycle you will keep creating accounts

and keep getting banned...

the matter that you are still at large makes me wonder 288 posts :not bad:

 

 

so hardcore

what the hek why you are black (ban) :y u no?:

 

 

devlin gather all those fixes and make a universal patch with all those and share it... not sell it

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