Jump to content

Question

Posted

How i can make Delevel Manager With request item for delevel + reward for delevel?

Was something with L2ItemInstance, but i don;t know how.  

I want to take from players 1 kk adena and give 1 apiga. Thank you !

Recommended Posts

  • 0
Posted (edited)

Yea, no work for me, thx all for attentions. everything i do, no work. I have lv 80 and item for destroy, Delevel Manager has telling me i no have lv 801.....

Edited by 0flee
  • 0
Posted (edited)

Try this 

player.removeExpAndSp(ExperienceData.getInstance().getExpForLevel(55), 0);
player.broadcastUserInfo();

Do you want it reduced to 55 or 30 levels?

Edited by TGSLineage2
  • 0
Posted (edited)
13 minutes ago, 0flee said:

I want after level 80 ( till level 85) player downlevel to 55.

assuming the method you are using is void type, you should ask at the beginning.
           

if (player.getLevel() <= 80) {
            player.sendMessage("You don't have the level necessary to perform this action")
            return;
            }

 

Edited by TGSLineage2
  • 0
Posted

I try this before, unsuccessfully. Btw, i find a voice command to do that except npc. But it is in Greek and it is for interlude, and i try to adapt L2j-Sunrise , but idk if i can.

Spoiler

 

 

  • 0
Posted

try this one

if (player.getLevel >= 80 && player.getLevel <= 85) // Only 80 .. 85 levels 
	if (player.destroyItemByItemId("delevel", 57, 1000, null, true)) // Check the destroy item
		{
			player.removeExpAndSp(player.getExp() - ExperienceData.getInstance().getExpForLevel(55), 0); //remove the xp
			player.addItem("delevel-reward", 7575, 1, null, true); // reward
		}

 

Note: If this will not work, then you should look before this code if something doesn't allow the conditions

  • 0
Posted (edited)

Yea, i did it on voice command. Now i must find that way to do delevel after lv 80. I try 

if (player.getLevel >= 80 && player.getLevel <= 85) // Only 80 .. 85 levels

and chat still sau i no have requirements to do delevel.

Edited by 0flee
  • 0
Posted
21 minutes ago, 0flee said:

Yea, i did it on voice command. Now i must find that way to do delevel after lv 80. I try 


if (player.getLevel >= 80 && player.getLevel <= 85) // Only 80 .. 85 levels

and chat still sau i no have requirements to do delevel.

maybe you should post exactly what message you are receiving. also, post the whole code here in code tags

  • 0
Posted (edited)

Ok, i have level 80 and i can;t do delevel. just on level 85. I will post here code.

 

http://dfrhtcF.png

 

Spoiler

public class DelevelCmd implements IVoicedCommandHandler
{
    private static final String[] VOICED_COMMANDS =
    {
        "delevel"
    };
    
    public static final int ZONE_PEACE = 2;
    
    /*
     * (non-Javadoc)
     * @see l2r.gameserver.handler.IVoicedCommandHandler#useVoicedCommand(String, l2r.gameserver.model.L2PcInstance), String)
     */
    @Override
    public boolean useVoicedCommand(String command, L2PcInstance activeChar, String target)
    {
        if (command.startsWith("delevel"))
        {
            requestDelevel(activeChar);
        }
        return true;
    }
    
    public boolean requestDelevel(L2PcInstance activeChar)
    {
        Siege siege = SiegeManager.getInstance().getSiege(activeChar);
        
        // Check the activeChar's level.
        if (activeChar.getLevel() <= 80)
        {
            activeChar.sendMessage("You do not meet the level requirement for Delevel!");
            return false;
        }
        // Check activeChar if have SubClass
        else if (activeChar.isSubClassActive())
        {
            activeChar.sendMessage("Please switch to your Main Class before attempting Delevel.");
            return false;
        }
        // Check activeChar if in Peace Zone
        else if (!activeChar.isInsideZone(ZoneIdType.PEACE))
        {
            activeChar.sendMessage("You can only Delevel in peace zone.");
            return false;
        }
        // Check activeChar is death/fake death and movement disable
        else if (activeChar.isMovementDisabled() || activeChar.isAlikeDead())
        {
            activeChar.sendMessage("You can't Delevel on death mode");
            return false;
        }
        // Check if activeChar is in Siege
        else if ((siege != null) && siege.isInProgress())
        {
            activeChar.sendMessage("You are in siege, you can't Delevel.");
            return false;
        }
        // Check if activeChar is a Cursed Weapon owner
        else if (activeChar.isCursedWeaponEquipped())
        {
            activeChar.sendMessage("You can't Delevel! You are currently holding a cursed weapon.");
            return false;
        }
        // Check if activeChar is in Duel
        else if (activeChar.isInDuel())
        {
            activeChar.sendMessage("You can't Delevel You are in a duel!");
            return false;
        }
        // Check is in DimensionsRift
        else if (activeChar.isInParty() && activeChar.getParty().isInDimensionalRift())
        {
            activeChar.sendMessage("You can't Delevel! You are in the dimensional rift.");
            return false;
        }
        // Check to see if the activeChar is in an event
        else if (activeChar.isOnEvent())
        {
            activeChar.sendMessage("You can't Delevel! You are in event now.");
            return false;
        }
        // Check activeChar is in Olympiade
        else if (activeChar.isInOlympiadMode() || (activeChar.getOlympiadGameId() != -1))
        {
            activeChar.sendMessage("You can't Delevel! Your are fighting in Olympiad!");
            return false;
        }
        // Check activeChar is in observer mode
        else if (activeChar.inObserverMode())
        {
            activeChar.sendMessage("You can't Delevel in Observer mode!");
            return false;
        }
        // Check activeChar have karma/pk/pvp status
        if ((activeChar.getKarma() > 0) || (activeChar.getPvpFlag() > 0))
        {
            activeChar.sendMessage("player in PVP or with Karma can't use the Delevel command!");
            return false;
        }
        // Check if activeChar have no one in target
        else if (activeChar.getTarget() == null)
        {
            activeChar.sendMessage("You can't have any one in your target when Delevel only your self.");
            return false;
        }
        // If activeChar have not any of theis can delevel
        delevelstart(activeChar);
        return true;
    }
    
    public boolean delevelstart(L2PcInstance activeChar)
    {
        try
        {
            if (activeChar.destroyItemByItemId("Delevel", 3470, 10, null, true))
            {
                activeChar.sendMessage("You don't have enough Gold Bar.");
            }
            {
                activeChar.addItem("delevel-reward", 7575, 1, null, true);
                activeChar.sendMessage("Congratulation)" + activeChar.getName() + (" you are on level 55."));
            }
            activeChar.getCurrentHp();
            activeChar.getCurrentCp();
            int max_level = ExperienceData.getInstance().getMaxLevel();
            // Protections
            Integer returnToLevel = 55;
            if (returnToLevel < 1)
            {
                returnToLevel = 1;
            }
            if (returnToLevel > max_level)
            {
                returnToLevel = max_level;
            }
            // Resets character to first class.
            activeChar.broadcastUserInfo();
            final byte lvl = Byte.parseByte(returnToLevel + "");
            final long pXp = activeChar.getStat().getExp();
            final long tXp = ExperienceData.getInstance().getExpForLevel(lvl);
            if (pXp > tXp)
            {
                activeChar.getStat().removeExpAndSp(pXp - tXp, 0);
            }
            else if (pXp < tXp)
            {
                activeChar.getStat().addExpAndSp(tXp - pXp, 0);
            }
            
            // restore Hp-Mp-Cp
            activeChar.setCurrentCp(activeChar.getMaxRecoverableCp());
            activeChar.setCurrentMp(activeChar.getMaxRecoverableMp());
            activeChar.setCurrentHp(activeChar.getMaxRecoverableMp());
            activeChar.broadcastStatusUpdate();
            // Updates the activeChar's information in the Character Database.
            activeChar.store();
            // Update skill list
            activeChar.sendSkillList();
        }
        catch (Exception e)
        {
            e.printStackTrace();
        }
        return true;
    }
    
    @Override
    public String[] getVoicedCommandList()
    {
        return VOICED_COMMANDS;
    }
    
}

 

Edited by 0flee
  • 0
Posted (edited)

OK guys, i solve it. the problem was "=" from <=80. Now i leave it < 80 and it's working. thx again. Now i want to know how i can count them. it is player.getCountDelevel()?

Edited by 0flee

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