Jump to content
  • 0

Question

Posted

Someone must know a fix for this bug?

The play's time to go with the char buga clikas and fast restart in the same time and press the enter key again puts password and log normal buggy so that nobody can attack the play of the target to catch not only to attack the

Recommended Posts

  • 0
Posted

I will explain again

vo log your character on the screen to select the character you click enter and reloguin while i go back to the screen where you put your loguin ai and log normal so that you can attack more niguém will be able to attack your character and this bug

  • 0
Posted

// Check if player are changing class

                if (player.isLocked())

                {

                        _log.severe(" Player " + player.getName() + " tried to restart during class change.");

                        sendPacket(RestartResponse.valueOf(false));

                        return;

                }

 

 

by class if it makes it by class and if i understood well if they make it but fast clicking then

 

// Fix against exploit anti-target

                if (player.isCastingNow())

                {

                        player.abortCast();

                        player.sendPacket(new ActionFailed());

                }

 

at requestrestart.java

  • 0
Posted

yes Tryskell interlude

you have the correction?

 

Malzahax

I've applied this fix the problem continues for more how to make the bug, and as I explained

I believe that the correction would be something on the start button and log back on the screen of selection of char

  • 0
Posted

Akken, MAXIMO-XP speaks of logoff/relog in order to be in-targetable (mainly in sieges, no ? That was the bug on Frozen).

 

Frozen fixed it - in a weird way - some weeks/months, as I said. Just read timeline, I haven't time to read it for you :P.

  • 0
Posted

I do not understand your explanation you can send me a pm with your msn to help me

 

the go on l2pcinstance and find onEnter method

this is the place you can fix the problem

  • 0
Posted

That's a weird way frozen used to fix it.

 

Go to your L2PcInstance class , find the method onPlayerEnter and before the closing brackets ( }) , i mean at the end of the method add these lines

 

decayMe();
spawnMe();
broadcastUserInfo();

  • 0
Posted

That's a weird way frozen used to fix it.

 

Go to your L2PcInstance class , find the method onPlayerEnter and before the closing brackets ( }) , i mean at the end of the method add these lines

 

decayMe();
spawnMe();
broadcastUserInfo();

 

same :P

  • 0
Posted

public void onPlayerEnter() {

        startWarnUserTakeBreak();

        decayMe(); <<<<

        spawnMe ();<<<<

        broadcastUserInfo (); <<<<

 

        if (SevenSigns.getInstance().isSealValidationPeriod()

                || SevenSigns.getInstance().isCompResultsPeriod()) {

            if (!isGM() && isIn7sDungeon() && Config.ALT_STRICT_SEVENSIGNS

                    && SevenSigns.getInstance().getPlayerCabal(this) != SevenSigns.getInstance().getCabalHighestScore()) {

                teleToLocation(TeleportWhereType.Town);

                setIsIn7sDungeon(false);

                sendMessage("You have been teleported to the nearest town due to the beginning of the Seal Validation period.");

            }

        } else {

            if (!isGM() && isIn7sDungeon() && Config.ALT_STRICT_SEVENSIGNS

                    && SevenSigns.getInstance().getPlayerCabal(this) == SevenSigns.CABAL_NULL) {

                teleToLocation(TeleportWhereType.Town);

                setIsIn7sDungeon(false);

                sendMessage("You have been teleported to the nearest town because you have not signed for any cabal.");

            }

        }

 

 

this correct?

  • 0
Posted

public void onPlayerEnter() {

        startWarnUserTakeBreak();

        decayMe(); <<<<

        spawnMe ();<<<<

        broadcastUserInfo (); <<<<

 

        if (SevenSigns.getInstance().isSealValidationPeriod()

                || SevenSigns.getInstance().isCompResultsPeriod()) {

            if (!isGM() && isIn7sDungeon() && Config.ALT_STRICT_SEVENSIGNS

                    && SevenSigns.getInstance().getPlayerCabal(this) != SevenSigns.getInstance().getCabalHighestScore()) {

                teleToLocation(TeleportWhereType.Town);

                setIsIn7sDungeon(false);

                sendMessage("You have been teleported to the nearest town due to the beginning of the Seal Validation period.");

            }

        } else {

            if (!isGM() && isIn7sDungeon() && Config.ALT_STRICT_SEVENSIGNS

                    && SevenSigns.getInstance().getPlayerCabal(this) == SevenSigns.CABAL_NULL) {

                teleToLocation(TeleportWhereType.Town);

                setIsIn7sDungeon(false);

                sendMessage("You have been teleported to the nearest town because you have not signed for any cabal.");

            }

        }

 

 

this correct?

 

and that they have to apply to correct the problem?

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



  • Posts

    • We are taking new orders. Kindly DM us on Telegram!
    • Hello everyone!  I’d like to share an experience that might serve as a lesson for anyone planning to work with third-party protection services—specifically, Active Anticheat. I know this might sound like a strange job request, but  our player base mostly consists of veteran of Lineage 2 players who are used to using bots as part of their gameplay experience. As server administrators, we decided to adapt to our users. That’s why we approached Active Anticheat with a proposal: Allow bot usage under certain conditions. We explained everything in detail, and they agreed.   📌 February – A Promising Start On February 16th, we contacted Active Anticheat to request a custom antibot system. The idea was to kick players using bots during specific times (like sieges), but allow them to log back in without bots afterward. After a few discussions, both sides agreed on the following solution: Bots allowed during regular days. During siege events, anyone using a bot would be automatically kicked. Kicked players could log back in without using bots. The deal was priced at $5,000, which we already paid on March 31st, 2025. Active Anticheat promised delivery by the end of April, or at the latest, by May. Screenshot:  Deal 1 Deal 2   🕐 May – The Delays Begin We followed up multiple times in May, only to finally hear back on May 26th: “It won’t be ready this month. But we’re working on a big update coming in June.” That update? Still nowhere to be seen, even as I’m writing this post. Screenshot:  Delayed   🔁 Plan B – L2Walker Rejected, Adrenaline Offered With our server launch schedule getting tighter, we needed an alternative. At the end of June, we asked Active Anticheat: “Can you at least allow L2Walker access to the server?” Their response on June 28th: “L2Walker can’t be allowed. But we can allow Adrenaline (free & paid version) and L2Helper for $2,000 + $300 (for a new license).” We agreed, hoping it would be a temporary fix while waiting for the promised “big update” (which we had already paid $5,000 for, remember?). Screenshot:  New Offer 1 New Offer 2 New Offer 3   ❌ AA Failed Their setup took about a week. We ran 2–3 rounds of testing using clean clients. The result? Adrenaline (both free and paid) couldn’t connect to our server. It couldn’t detect the Lineage 2 client, because the custom Active Anticheat protection was blocking it. We reached out to Active Anticheat for support, and their response? “You should contact Adrenaline support to enable free Adrenaline for your server. Adrenaline blocks it by default when Active Anticheat is detected.” Then we tested Premium Adrenaline. And it still didn’t work. Active Anticheat stood firm: “It’s not our fault. Adrenaline blocked us—not the other way around.” Screenshot: Failed 1 Failed 2   💸 The Bitter Reality Today, we’re still waiting for answers. No reply. No fix. No update. No refund. We’ve spent a total of $7,300 and received nothing functional in return. And this, despite their full agreement with our initial plan.  
  • Topics

×
×
  • Create New...

AdBlock Extension Detected!

Our website is made possible by displaying online advertisements to our members.

Please disable AdBlock browser extension first, to be able to use our community.

I've Disabled AdBlock