Jump to content
  • 0

WTF is going on


Question

Posted

i added dont loose your buffs on death code

 

// Same thing if the Character isn't a Noblesse Blessed L2PlayableInstance
        else if (this instanceof L2Playable && ((L2Playable)this).isNoblesseBlessed())
        { 
			((L2Playable)this).stopNoblesseBlessing(null); 

        	if (((L2Playable)this).getCharmOfLuck()) //remove Lucky Charm if player have Nobless blessing buff 
				((L2Playable)this).stopCharmOfLuck(null); 
		} 
		else

 

and i got this error

 


[javac] Compiling 1298 source files to C:\L2GateAway\L2JGateway\L2J_CORE\build\classes
    [javac] C:\L2GateAway\L2JGateway\L2J_CORE\java\com\it\br\gameserver\model\L2Character.java:1513: 'else' without 'if'
    [javac] 		else if (this instanceof L2PlayableInstance && ((L2PlayableInstance)this).isPhoenixBlessed()) 
    [javac] 		^
    [javac] 1 error

Recommended Posts

  • 0
Posted

interesting, but quote my code where i did

 

else if

else

 

or

 

else

if

 

or smth

 

where i said that you did anything like that?

i stated for a fact that in this topic those who tried to help the guy dont know java

  • 0
Posted

In addition to Intrepid's post.

The 'else if' thing is the simplified version of

 

if(something)
{
   doStuff();
}
else
{
   if(somethingElse)
   {
       doOtherStuff();
   }
   else
   {
       if...
   }
}

due to some nesting rules you can simply achieve the same result with:

if(something)
   doStuff();
else if(somethingElse)
   doOtherStuff();
else if...

  • 0
Posted

In addition to Intrepid's post.

The 'else if' thing is the simplified version of

 

if(something)
{
    doStuff();
}
else
{
    if(somethingElse)
    {
        doOtherStuff();
    }
    else
    {
        if...
    }
}

due to some nesting rules you can simply achieve the same result with:

if(something)
    doStuff();
else if(somethingElse)
    doOtherStuff();
else if...

 

wow surprise

  • 0
Posted

Pure logic.

Okay, you don't know anything, so use pure logic.

Can you create a statement, in the english language, by saying "else if", if you don't have an "if" before?

 

someone realy sucks at java here ^^

 

And it's not you, I suppose (?)

Guest
This topic is now closed to further replies.



  • Posts

    • <dailyReward days="28" autoOpen="true" minimumOnlineTimeSeconds="30" oneRewardPerIP="true" resetIfMissDay="true">   For now, I have these settings in the XML—this is the V1 version I created, though I plan to make further improvements over time. Of course, I’ll also add more protections—MAC, HWID, and perhaps others like account-based restrictions—to make it more secure. We can also implement non-tradable items to further enhance the system's security. I’ll keep posting updates and refining both the system and the interface. I might make a video tomorrow; if you look at the top, you'll see the "auto-open" feature can be toggled on or off, allowing users to rely solely on the `.daily` command. Cheers! Note: If I sell it in this state, I’ll provide support and roll out updates to users. I’m not forcing anyone to buy anything; I’d even provide the patch files so that anyone with the necessary skills can add features, modify it, or improve it further.
    • If the problem is that the target is lost, the action of aiming at another character, upon losing collision, does not allow aiming.   This one works as it should, allowing you to target characters
    • MICROTEXT AND WATERMARKS BREAK MOST RENDERINGS Microtext and watermarks aren’t just small decorative details. They are one of the most common reasons a document fails verification, even when it looks decent at first glance. The issue is that these elements are almost impossible to reproduce “by eye.” Microtext requires precise geometry and legibility at a very small size, while a watermark needs the correct density, transparency, and accurate placement relative to other security features. Any deviation becomes obvious during detailed inspection. ▪ What’s most often done wrong: - microtext is drawn too thick or blurry - the watermark is made either too visible or almost invisible - the positioning between microtext and watermark is ignored - the original printing technology isn’t taken into account when choosing density and shape - The stronger the document’s security features, the less room there is for approximation. What matters here isn’t visual similarity, but accurate reproduction of the original technical characteristics. If your document contains microtext and watermarks, this is always an area that requires extra attention. Write to us in DMs. We’ll review your case and point out exactly which details need the highest precision during rendering. › TG: @mustang_service_ms ( https:// t.me/ mustang_service_ms ) › Channel: Mustang Service ( https:// t.me/ +JPpJCETg-xM1NjNl ) #drawing #microtext #photoshop #editing #watermarks
    • GoldRush launches tomorrow! July 18 16:00 GMT+3 Europe / International Register your account in the website, connect wallet and be ready to dominate!
  • 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..