GR Η Κίνα θα σταματήσει να χρησιμοποιεί Windows PC έως το 2022
-
Posts
-
-
-
By UTCHIHAmkt · Posted
DISCORD : utchiha_market telegram : https://t.me/utchiha_market SELLIX STORE : https://utchihamkt.mysellix.io/ Join our server for more products : https://discord.gg/hoodservices https://campsite.bio/utchihaamkt -
By EUSOUOMESTREDOSMAGOS · Posted
Do you know how I can remove that error? -
By Salty Mike · Posted
UPDATE 1: My bad! I didn't notice that this is published in the L2OFF section. The statement below is only relevant for L2J. (Yes, there is another, very simple, efficient, and quite elegant, way to do this. What you need is: - create one Config of type Boolean, lets call it MOB_DROP_ONLY_ADENA, which will act as the trigger point for this feature. - locate the method which is responsible for parsing the drops of the monsters from XML. - in this method, there should be a loop for each of the parsed items and there we add a simple check: if (Config.MOB_DROP_ONLY_ADENA && item.getItemId() != 57) { continue; } And we are done. Now, every time the server tries to parse a drop item, it will check if the ID of the item is 57 (adena) and skip it if it isnt. You should add a further check to make sure that the NPC you are parsing the drop for is of type Monster and not of type RaidBoss or GrandBoss (or any other custom type you might have). The easiest way is with with a lookup into the NPC/Monster Template, if there is one on your assembly of choice. What these templates do, usually, is to provide some lookup options for certain features of theirs, such as level, type, etc.)
-
-
-
-
Topics
-
Recommended Posts
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.