- 0
-
Posts
-
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.) -
By EUSOUOMESTREDOSMAGOS · Posted
Hello, good morning everyone. I would like to know some way so that the mobs only drop adena, the only way I know is to go to each mob's line and delete the materials. Would there be any other way? -
We thrilled to announce our 1st Zealy Sprint! Complete the tasks and get rewards! Don't forget to join our Discord! -
By Large Sells · Posted
Skype: Live:LargeSells Discord: LargeSeLLs#7167 DiscUniqueID: 321388776200994816
-
-
-
-
Topics
-
Question
horato
Hello,
Iam trying to sniff and edit existing l2j packets to be able to connect with my GOD client (dont tell me its waste of time pls, I already know that ^^). Is here anyone able to tell me where I can find the packet structure? Yesterday I had GOD client with protocol 415 and packet structure from this site. It was working nice. Today I updated my GOD client and protocol changed to 411. Ofc it stopped working (CharSelectInfo packet was obviously changed so I cant see my chars in login screen properly) but the structure which PHX shows me seems to be same like in the old version of client.
So how can I get the actual structure? I've tried this guide, but without success.
//EDIT: ok, I finally managed to find those packets in engine.dll, they are somewhere around 2045A59E address(or what is it :D). Now, can someone tell me how to read the structure from it? Except the "ddS" part. Or this is the only thing you can get from it and you have to guess what each value stands for? :D
CharSelectionInfo:
Thx
Link to comment
Share on other sites
7 answers to this question
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.