Jump to content

Recommended Posts

Posted

What is the custom Enchant points?

Means:

All have different grade of equipment to strengthen points, points can customize ...

 

For example:

D grade equipment, scrolls to use an enhanced +1 (This is the official set), but we can change his values.

 

Becomes:

D grade equipment, scrolls to use an enhanced + X, (X is the value you set) ...

 

But the key is not here.

We can also set the X1, X2, X3, X4 ... to correspond to C grade, B grade, A grade, S grade ..

 

This work is very easy ..

So, here goes:

 

1) First open Config.java:

Found:

public static boolean ENCHANT_HERO_WEAPONS;

 

Added later:

	/** Custom Enchant Points? */
public static boolean CUSTOM_ENCHANT_POINTS;
public static int ENCHANT_D_GRADE_POINTS;
public static int ENCHANT_C_GRADE_POINTS;
public static int ENCHANT_B_GRADE_POINTS;
public static int ENCHANT_A_GRADE_POINTS;
public static int ENCHANT_S_GRADE_POINTS;

 

 

Find:

ENCHANT_HERO_WEAPONS = Boolean.parseBoolean(Enchant.getProperty("EnchantHeroWeapons", "False"));

 

Added later:

					/* custom enchant point  */
				CUSTOM_ENCHANT_POINTS = Boolean.parseBoolean(Enchant.getProperty("CustomEnchantPoints", "False"));
				ENCHANT_D_GRADE_POINTS = Integer.parseInt(Enchant.getProperty("EnchantDGradePoints", "1"));
				ENCHANT_C_GRADE_POINTS = Integer.parseInt(Enchant.getProperty("EnchantCGradePoints", "1"));
				ENCHANT_B_GRADE_POINTS = Integer.parseInt(Enchant.getProperty("EnchantBGradePoints", "1"));
				ENCHANT_A_GRADE_POINTS = Integer.parseInt(Enchant.getProperty("EnchantAGradePoints", "1"));
				ENCHANT_S_GRADE_POINTS = Integer.parseInt(Enchant.getProperty("EnchantSGradePoints", "1"));

 

 

 

2) Next open: enchant.properties

Found:

EnchantHeroWeapons = False

 

Added later:

# Allow custom Enchant points (default: False)
CustomEnchantPoints = False

# D grade equipment (weapons / armor / jewelry) effect:  Enhanced + 1 eq +X  (official: 1)
EnchantDGradePoints = 1

# C  grade equipment (weapons / armor / jewelry) effect:  Enhanced + 1 eq +X  (official: 1)
EnchantCGradePoints = 1

# B  grade equipment (weapons / armor / jewelry) effect:  Enhanced + 1 eq +X  (official: 1)
EnchantBGradePoints = 1

# A  grade equipment (weapons / armor / jewelry) effect:  Enhanced + 1 eq +X  (official: 1)
EnchantAGradePoints = 1

# S  grade equipment (weapons / armor / jewelry) effect:  Enhanced + 1 eq +X  (official: 1)
EnchantSGradePoints = 1

 

 

3) Finally, in the directory: java \ net \ sf \ l2j \ gameserver \ network \ clientpackets

Open:

RequestEnchantItem.java

 

Editing and adding:

Find:

boolean enchantItem = false;

boolean blessedScroll = false;

int crystalId = 0;

Added later:

		int enchpoint = 0;

 

 

Find:

case L2Item.CRYSTAL_A:

crystalId = 1461;

Added later:

			if (!Config.CUSTOM_ENCHANT_POINTS)
			enchpoint = 1;
		else 
			enchpoint = Config.ENCHANT_A_GRADE_POINTS;

 

Find:

case L2Item.CRYSTAL_B:

crystalId = 1460;

Added later:

			if (!Config.CUSTOM_ENCHANT_POINTS)
			enchpoint = 1;
		else 
			enchpoint = Config.ENCHANT_B_GRADE_POINTS;

 

Find:

case L2Item.CRYSTAL_C:

crystalId = 1459;

Added later:

			if (!Config.CUSTOM_ENCHANT_POINTS)
			enchpoint = 1;
		else 
			enchpoint = Config.ENCHANT_C_GRADE_POINTS;

 

Find:

case L2Item.CRYSTAL_D:

crystalId = 1458;

Added later:

			if (!Config.CUSTOM_ENCHANT_POINTS)
			enchpoint = 1;
		else 
			enchpoint = Config.ENCHANT_D_GRADE_POINTS;

 

Find:

case L2Item.CRYSTAL_S:

crystalId = 1462;

Added later:

			if (!Config.CUSTOM_ENCHANT_POINTS)
			enchpoint = 1;
		else 
			enchpoint = Config.ENCHANT_S_GRADE_POINTS;

 

Find:

item.setEnchantLevel(item.getEnchantLevel() + 1);

 

Modify:

				item.setEnchantLevel(item.getEnchantLevel() + enchpoint);

 

 

All work done!

Now, compile your source code, test, are you into the game .. 

 

The reason I do this, just to stand-alone.

You do not want to hold +100 D Top Weapon levelup to 80, Right?

  • 2 weeks later...
  • 2 months later...
Posted

I do not understand anything in your code

You 've gotta be so idiot lol, it's a different enchant value for scrolls. For example if your weapon is +0 and you add an enchant scroll it is going to become +2/+3 , regarding to the value that you set on the config.

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

    • 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 nevermind, i got what you mean, here's the fix   https://drive.google.com/file/d/1av7OHaGSdnVQtcBgb9MhtiIkxVXy3P2y/view?usp=sharing   CanIngnoreCollision=True CanBeIngnoredCollision=True  
    • <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..