Jump to content

Recommended Posts

Posted

Hello guys i have a dificult time figuring out how to make this  :'(

 

I know how to add stats on individual armor but ....

Ex: if i put 2000 HP on helmet and i want the stats to activate when the whole armor is on me it dosent work ....

It gives 2000 HP only when i ware the helmet...

How can i make it as if ONLY when the whole armor is on me the 2000 HP activate ???

 

 

Please help  :'(

Posted

i understood you^^ well i am not sure 100% because i am not so good developer,i started 1 month ago and day by day i fight vs problems:P anyway for what i know..u should create a new skill that add ur desired stats and add it correctly on ur set on navicat(i think armorsets table,skill_id)..i heard that from taks7,a man that i "love"^^ but i am not sure about what i said..so try or wait for a l2dev

Posted

yeap.. u need to make a skill (passive) that will be activated when all parts are equiped.. not add stats in every single part of the armor :/.. helmet, gloves etc.. and then its all about adding the armor parts in `armorsets` at db...

Posted

yeap.. u need to make a skill (passive) that will be activated when all parts are equiped.. not add stats in every single part of the armor :/.. helmet, gloves etc.. and then its all about adding the armor parts in `armorsets` at db...

 

I have no idea how i shold make that >.<

Can you make a guide with this ??

That wold be very helpfull :D

 

Thank you ;)

Posted

Sure, and sorry if I explain this very basic; it's not that I am assuming you are an idiot or something, it's just so that new people that read this can immediately know what to do.

 


 

'armorsets' table is inside you Navicat where your l2j database is.

 

Direct link: http://i89.servimg.com/u/f89/11/39/87/02/explan10.jpg

explan10.jpg

 


 

There is a column called 'skills' which triggers when the list of armor from that particular row is fully equipped.

 

Let's take a look at the first row skills: You can find them in your gameserver folder /data/stats/skills (open the .xml with notepad(++))

<skill id="3006" levels="1" name="Equip Set Items">

  <set name="target" val="TARGET_SELF"/>

  <set name="skillType" val="BUFF"/>

  <set name="operateType" val="OP_PASSIVE"/>

</skill>

 

Just the default skill at all of them; I guess they will display the item icon in the characters passive skills.

 

<skill id="3500" levels="1" name="Wooden Set">

  <set name="target" val="TARGET_SELF"/>

  <set name="skillType" val="BUFF"/>

  <set name="operateType" val="OP_PASSIVE"/>

  <for>

    <mul order="0x30" stat="pDef" val="1.02"/> <!-- P. Def. +2% -->

    <add order="0x40" stat="maxHp" val="41"/> <!-- HP +41 -->

  </for>

</skill>

This is getting more interesting: so this skill only applies when the 'Wooden Set' is fully equipped.

 

If you just want to edit an existing set, search the armor id('s) and look for it in the armorsets list, check the skills, open the xml's and edit them there.

 

For your custom armor, you can:

- Copy an original line

- Paste it in notepad

- Edit the ID's of the armor parts and perhaps some other variables

- Go back to navicat armorsets table to the bottom row, press one down (down arrow key), this will create a new line, have the first column selected and paste your edited content from the notepad

 

 

Good luck

 

 

 

Posted

Sure, and sorry if I explain this very basic; it's not that I am assuming you are an idiot or something, it's just so that new people that read this can immediately know what to do.

 


 

'armorsets' table is inside you Navicat where your l2j database is.

 

Direct link: http://i89.servimg.com/u/f89/11/39/87/02/explan10.jpg

explan10.jpg

 


 

There is a column called 'skills' which triggers when the list of armor from that particular row is fully equipped.

 

Let's take a look at the first row skills: You can find them in your gameserver folder /data/stats/skills (open the .xml with notepad(++))

Just the default skill at all of them; I guess they will display the item icon in the characters passive skills.

This is getting more interesting: so this skill only applies when the 'Wooden Set' is fully equipped.

 

If you just want to edit an existing set, search the armor id('s) and look for it in the armorsets list, check the skills, open the xml's and edit them there.

 

For your custom armor, you can:

- Copy an original line

- Paste it in notepad

- Edit the ID's of the armor parts and perhaps some other variables

- Go back to navicat armorsets table to the bottom row, press one down (down arrow key), this will create a new line, have the first column selected and paste your edited content from the notepad

 

 

Good luck

 

 

 

 

I am not an idiot but i am a newbi i am still learning ^_^

as you where once when you didant know anything about the game :)

I am still learning :D

 

Thank you very much for your help !!!

Posted

I am not an idiot but i am a newbi i am still learning ^_^

as you where once when you didant know anything about the game :)

I am still learning :D

 

Thank you very much for your help !!!

Locked.If you want to ask something about this topic pm me to unlock it.

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