Jump to content

Recommended Posts

Posted

This is what you do....

 

1st) Buy any cheap Dgrade Armor or Jewelry (not a weapon).

2nd) Buy 6 Enchant Armor D's

3rd) Get one Enchant Weapon B(grade that you are wanting to enchant, for this we will say Dual SLS).

4th) Go ahead and plus up your D armor or Jewelry to +3 and your Dual SLS to +3 as well.

5th) Put your 3 left over EADs and your 1 EWB on your hotbar

IE: F1/EAD F2/EAD F3/EAD F4/EWB

6th) This is were you have to be quick about it. Enchant your Darmor or Jewelry +1. See if it breaks. AS SOON AS IT BREAKS ENCHANT YOUR WEAPON.

IE: you hit F1 and you blow that +3 Darmor going to +4 then you will press F4 and enchant those Dual SLS to +4.

 

How does this work and why is only 80% successful. Well this is lineage 2 the odds are against you and nothing with enchanting is 100%. All your doing is taking that chance of breaking your weapon right off the bat out of the question when doing this which leave you open for success. Side note: Only try this once a day. You do it multiple times a day you greatly reduce your success rate.

 

I have personally used this. I have made many +8-10 Weapons. I sell most of them after +8. Today alone I made a +5 Dual SLS and +4 Dual Raids (different accounts).

Posted

sometimes thinks like that helps at enchanting (dunno why) i personaly made with a little different trick 1 weapon from +8 to +25 rate 80 % in 5 minutes and at the beginging i  thought that this tricks works 100% but the 2nd weapon i tried it broke to +12

anyway its a good trick and stop flame the person that post it here

Posted

Lucky 8 times? :D

 

Yes. It's luck. Neither NCSoft nor l2j forks use random number tables, so the chance is fully random. Even if you just failed 2800 enchants in a row, you have the same chance to enchant the 2801st time.

Posted

Altho, I kinda like the l2 client side enchant packet system..

 

I don't know if someone noticed, but if you start enchanting a HD and a DHA you will see that 70% of the brokes HD will brake first and DHA will go upper and brake too..

 

Same for AM and Imperial staff..

 

its just so cool and funny, cuz its not even coded this way in java ^^

Guest
This topic is now closed to further replies.



  • Posts

    • try this one instead. The one he shared affects every single NPC/player character in the game, the one I posted only affects player characters  https://drive.google.com/file/d/1UtccbD9e50x3WEnQBab2PTZnBHwpcGYM/view?usp=sharing or perhaps i misunderstood; if you could please post a full explanation of the problem you're having with the files, unfortunately i think whatever you're using to translate to english is a bit bad
    • <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
  • 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..