Результаты поиска по запросу: *

Paperdolls are accounted for in my estimation since they are an integral part of a packet or two. Same for differences with shortcuts, enchanting, etc. The time estimation is solely for the java part and mainly for the initial implementation so that it works like it does on HF. Except for here...

That's why I went with a newer protocol. They have the ex_packet structure visible directly in the interface.u.

I strongly disagree. It could be easier, if you don't know how to code, but it will never be faster. You could learn how to code and upgrade the packets faster than applying all the needed amendments to make it 100% IL/HF or whatever-like. And if you know how to code, upgrading the packets could...

посмотреть

посмотрим

There is a test server with test client you can check, but long story short - no. You would still have to put a solid amount of work/time into the client/patch. Do not get me wrong, many things are already there, but not everything. For example, the sky dome will be glitchy here and there, the...

Cannot unless you have: 1. Access to sources. 2. A java developer. 3. A client developer.

I'm unable to open said zones that can change their effects through the packet with L2Editor. All other zones open just fine. Does anybody know how to fix it and is willing to share a solution? Any hints, ideas and suggestions are more than welcome. Thanks in advance! This is the error I get...

посмотрим

посмотрим

For this, you need to create custom packet(s), for which Rolo has already presented a link to the guide. It is the easiest/most straight-forward way that I know of, and the best thing is - it works. 😁

I am of the opinion that several things can be improved upon and others can be introduced: 1. Monetization - the monetization structure should be changed, namely, there should be a monthly recurring fee for tech support, else Mishanya does it all for free. 2. Community engagement and...

в копилку

The easiest way is through a well-placed RequestServerBypass() packet (in Interface.u), which you will intercept at a very specific point. If it is not sent, then you deduct they are not using your interface and you kill the connection.

You are sending the StatusUpdate packet with the wrong type IDs. CUR_DP = 0x27 MAX_DP = 0x28

GOD! Your first reply (version of your message) was the answer. Mobius sends 100 for MagicLampType (hard-coded value). Changed to 0 and is now fixed. TYVM!

Has anyone faced such an issue, where the EXP gained would be shown as Magic Lamp EXP on Essence/Eva version, as seen in the screenshot below? And if you had, how did you fix it? I would imagine it must be something client side, but the same thing happens with completely clean client too, so...

Do your AutoUse of buff scrolls, etc, work? Does your autofarm window "activate/toggle" (the animation activates)? Because it looks like you might not be sending the "ExAutofarmSettings", "ExActivateAutoShortcut()" etc packets, or at least not with the correct Packet IDs/Opcodes. From the...

"дырок нет"

Посмотреть