Jump to content

Recommended Posts

Posted

Hello, sorry my English!

Normal, the blessed enchant failed, the enchant value of the item became 0

With some fix, when the blessed enchant failed, the enchant value of the item became decreases by 1.

Ex: You have a weapons +13 and you enchant it with blessed enchant, if failed, your weapons is +12!!!

 

com.l2jserver.gameserver.network.clientpackets/RequestEnchantItem.java

 

- activeChar.sendPacket(SystemMessage.getSystemMessage(SystemMessageId.BLESSED_ENCHANT_FAILED));

+ activeChar.sendMessage("THE BLESSED ENCHANT FAILED!");

+ activeChar.sendMessage("The enchant value of the item became decreases by 1.");

- item.setEnchantLevel(0);

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

item.updateDatabase();

activeChar.sendPacket(new EnchantResult(3, 0, 0));

Credits : by me

Posted

Hello, sorry my English!

Normal, the blessed enchant failed, the enchant value of the item became 0

With some fix, when the blessed enchant failed, the enchant value of the item became decreases by 1.

Ex: You have a weapons +13 and you enchant it with blessed enchant, if failed, your weapons is +12!!!

 

com.l2jserver.gameserver.network.clientpackets/RequestEnchantItem.javaCredits : by me

 

maybe needs a correction then

 

+    if (item.getEnchantLevel() != 0);

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

+    else

+            activeChar.sendMessage("hi failure you enchanted a +0 weap wth blessed)

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

      item.updateDatabase();

 

     

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

      item.updateDatabase();

      activeChar.sendPacket(new EnchantResult(3, 0, 0));

 

Posted

maybe needs a correction then

 

+    if (item.getEnchantLevel() != 0);

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

+    else

+            activeChar.sendMessage("hi failure you enchanted a +0 weap wth blessed)

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

      item.updateDatabase();

 

     

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

      item.updateDatabase();

      activeChar.sendPacket(new EnchantResult(3, 0, 0));

 

I tested and work 100% with my code in Hi5 server.

Thanks you!

Posted

Thats useless code...Noone will uce that scrolls..You made with a lot of farm and stress the weapon for example +14 and you fail on enchant and it gets +13 thne you fail again +12 and goes on!!Until you get +3 again that you started and you leave and server and then you are happy :P

Posted

Thats useless code...Noone will uce that scrolls..You made with a lot of farm and stress the weapon for example +14 and you fail on enchant and it gets +13 thne you fail again +12 and goes on!!Until you get +3 again that you started and you leave and server and then you are happy :P

lol better than back +0 always ;D

anyway any1 know

can i make it only from expecific enchants? i mean from 0 to 16 it back -1 after 16 back to +10...

Posted

I code it for hard server :)

You can used a different patch:

				if (scrollTemplate.isBlessed())
				{
					// blessed enchant - clear enchant value
-      activeChar.sendPacket(SystemMessage.getSystemMessage(SystemMessageId.BLESSED_ENCHANT_FAILED));
-            item.setEnchantLevel(0);
+						activeChar.sendMessage("THE BLESSED ENCHANT FAILED!");
+						if (item.getEnchantLevel() >= 10)
+						{
+						activeChar.sendMessage("The enchant value of the item became decreases by 1.");						
+						item.setEnchantLevel(item.getEnchantLevel() - 1);
+						item.updateDatabase();
+						activeChar.sendPacket(new EnchantResult(3, 0, 0));
+						}
+						if (item.getEnchantLevel() < 10)
+						{
+						activeChar.sendMessage("The enchant value of the item became 0.");						
+						item.setEnchantLevel(0);
+						item.updateDatabase();
+						activeChar.sendPacket(new EnchantResult(3, 0, 0));
+						}						
					if (Config.LOG_ITEM_ENCHANTS)
					{
						LogRecord record = new LogRecord(Level.INFO, "Blessed Fail");
						record.setParameters(new Object[]{activeChar, item, scroll, support, chance});
						record.setLoggerName("item");
						_logEnchant.log(record);
					}
				}

 

When you used Blessed enchant:

If your enchant item <10: The enchant value of the item became 0

If your enchant item >10: The enchant value of the item became decreases by 1

  • 2 weeks later...

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
Reply to this topic...

×   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

    • sell adena l2rebon signature x1 - 1kk = 1 dollars l2reborn x10 - 500kk = 4 dollars E-Global x Lu4 - 1kk = 2 dollars BOHPTS - x20-x500 TOP PRICE DISCORD - GODDARDSHOP TELEGRAM - MMOPROMO Also on sale are Epic jewelry, Clothes at a very good price
    • Hello Sorry, my Discord is: ave7309
    • “Hello, I’d like to present a short description of the server. Everyone starts equally at max level 80. The server includes a custom buffer, custom class master, custom weapons and armors, custom zones, custom teleporter, custom raid bosses, and much more. I’ll leave a link in the description for those who want to see how everything looks inside. The server is only open on weekends, and you can find more news via the Facebook link.”   https://www.facebook.com/profile.php?id=61578869175323
    • 1. You where subscriber 3 years ago. 2. There is no current L2jMobius 2.8 Seven Signs version. Subcriber or not. 3. You have your answer from multiple forums that more items is more delay.  
    • 1. Optimize Packet Serialization Look in ItemList.java or wherever the inventory packet is constructed. Instead of building the packet with inefficient string concatenation or repeated allocations, use a preallocated buffer and avoid creating new objects for each item. Mobius sources are Java-based, so profiling with something like VisualVM or YourKit can help see where most time is spent. 2. Avoid Sending the Full List Each Time Modify the server to send only changed items (diff packets) when the inventory window opens. Some newer forks implement this as “lazy loading” or paged inventory so the client only loads e.g. 100 items at a time. 3. Limit the Inventory Size Per Page Instead of showing all 500 slots at once, split the inventory into pages/tabs (100 slots each). When the user switches a tab, send only that page’s items. This requires some client-side editing, but it’s the most user-friendly long-term fix. 4. Database & Cache Optimizations Ensure your items table is indexed by owner_id to make the query for player items fast. Cache item templates and static data so they are not reloaded every time the inventory is shown. ⚠️ Things to Keep in Mind Increasing slots from 80 → 500 does not just change a number — it multiplies the workload for packet building and UI rendering. You can’t fully avoid some extra cost with 500 items, but you can keep it under a few milliseconds if you optimize how and when the data is sent.    
  • 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