Jump to content

Recommended Posts

Posted

"G" Share (:

But i have a problem T_T ... look up to the pic

 

 

erroreagle.png

 

well the problem is texture are not encrypted with l2encdec, just do it, copy MOrcV4.utx in folder you have l2encdec, you don't have just download, ok now open CMD or DOS console same and copy path of l2encdec and now write l2encdec -e 121 MOrcV4.utx and you get a file named enc-MOrcV4.utx just copy in your systextures and rename to MOrcV4.utx and you done ;) ok enjoy and sorry for english hope understand.

 

rly thx for ur share,CriticalError....

but just one question: why u update the stuff on FreakShare???i remembered u like update stuff on Rapidshare,in recent days i found u update on FreakShare.

this netdisk rly slow.....^%&#$%#$&

OK I move to freaksahre because they pay for downloads, and ofc I uploading files from years in RS but they fuck me with new system put, I lose 222000 points and don't get nothing just a free account with premium privilegies? fail RS, now I move to fileserve becasue this host for I read is good and well this is all.
Posted

well the problem is texture are not encrypted with l2encdec, just do it, copy MOrcV4.utx in folder you have l2encdec, you don't have just download, ok now open CMD or DOS console same and copy path of l2encdec and now write l2encdec -e 121 MOrcV4.utx and you get a file named enc-MOrcV4.utx just copy in your systextures and rename to MOrcV4.utx and you done ;) ok enjoy and sorry for english hope understand.

 

he thanks buddy .. don't worry about english i get you xD! ... [te he encontrado en otros foros .. yo con otro nombre xD] ..

i will try that right now (:

 

EDIT: DONE! ... EVERYTHING WORKS ON (:

Thanks CriticalError [recuerda tu gente de habla hispana xD!]

 

NOTE: might not be better MEDIAFIRE, maybe 4SHARED or MEGAUPLOAD ? .. well, that's what i think.

Posted

I have one problem with this armors when insert SQLs into Navicat and data to gameserver folder all is OK,when i make and server side DAT files and systextures is OK too,but when i log into game and when i equip armors they no have textures (when i equip full set just hero's head are seen xD ) i read in this topic for encripting the textures and i made it with l2encdec_2.10.1 ( if i'm remember well in cmd i need to write "game dir"\l2encdec\l2encdec -e 121 "filemname" amd to get a encripted file "enc-filename" to rename it and to replace with older one in systextures folder) i made it with MHuman.utx i enc the file and replace it and when i log in game and equip the armor the game kick me with critical error :

Error:

Insufficient Memory.

Please check the Virtual Memory Option and avilable hard drive space.

You can check them by going to : Control Panel->System->Advanced->Performance->Settings->Advanced->Virtual memory.

 

On Firs time i say "lol thats can't be" of my 4GB Ram and 1TB hard and this error lolz". I stop some of process and try again and i get this error again.Then i try with another armor Tallum i get set tallum and equipe it and all was normal i check my memory and all working fine then i get again armor Desert and equip it and BOOM crit error. I replace the ENC files with normal one and again all works fine.

If someone can help me to fix this problem to get armors with tetures whith out problems with critical errors etc. to say or if someone are made it correctly and all for him working fine to share ready encripted fils to share it please.

Thanks!

Posted

It's an armor I made long time ago :)

Posible to download that armor or what was the name of armor ? :D

 

anyway i was looking for weaponts and wings thanks :P

Posted

The only armor set that mFxc got from Ave and to bad that I shared it :] Nice to see CriticalError that You share my stuff when I'am BAN'ed :]

NETTE stop -beep-ing pm'ing me about my stuffs. You will get a shit ;)

 

Take care mFxc

Posted

The only armor set that mFxc got from Ave and to bad that I shared it :] Nice to see CriticalError that You share my stuff when I'am BAN'ed :]

NETTE stop -beep-ing pm'ing me about my stuffs. You will get a shit ;)

 

Take care mFxc

Weaponts & Wings is good only for me :P I dident like that mod of vesper armor is just white and in some places RED ;D

And dont act like idk like your stuff are the best in l2 client mods ;D I have seen  great works from Makers and they share for free and i love them  :P

Guest
This topic is now closed to further replies.



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