Zeeyo

That's an integer variable designed to be used by the AI. Each NPC instance has a separate set of these vars. There is absolutely no difference which vars to use. You simply need to make sure you do not interfere with the logic of the parent classes. Of course, if you override associated handlers not to do 'super()', you can then reuse vars that are in use by parent class(es). There's really nothing more into it. Also, I must point out that TALKED is extremely biased towards showing wiseman_challenge_5. You might think the code guarantees a 20% chance for each page, but in reality you will be getting wiseman_challenge_5 at a rate of 41%. These are the actual page show rates: 1 – 20% 2 – 16% 3 – 12.8% 4 – 10.24% 5 – 40.96%

The PC point accumulation was also used in NA on HF and later in GoD+ (they even gave PC point pack items and had a PC point lottery). Still, I'd like a complete guide. It is pretty easy to set up a char to be able to use features in NPCs (PC point teleports/buffs/wyvern/etc), but is that really all about the PC event? Also, is the point gain rate configurable somewhere? How are valid codes determined?

Actually, this looks like either incorrect (missing) default schema in DSN (should be lin2db or whatever you named it, e.g. "c4_l2db"). For hAuthD, verify that you use both C4 = 1 and the correct BF key. In-file comments will tell you exactly what to do.

Hi guys, I know there was a guide (I don't recall the forum) about the l2off PC Cafe system, what it is comprised of and how to setup the account (and/or character(s)) to allow them to use PC Bang features. The thing is, I cannot seem to find anything. Perhaps it was about L2OFF premium features in general, because I can't seem to get google to find it for me. I know there is a specific bit to set in a certain mask field value in the DB, and then you can use the NPCs. But I would also like to know more about the UI-related features (is it only the level indicator). Your help is highly appreciated. P.S. Could anyone also point me to any info about PremiumD or it's emulator? I also seem to be failing to pick correct keywords to find those discussions.

Yes. No, I don't do validation l2phx-style. I validate using l2off pts servers without extenders and then extrapolate definitions for intermediate protocols. I also have an emulator that allows me to log in using any client (and yes, it allows me to see NPCs in 336 AND 377-660 AND 69x and later at the same time); I then inject custom-built packets and see if the presentation matches my expectations. For everything that is not implemented client side, l2off logic is used (e.g. if you change sub while setting up a general manufacture, your higher-levelled recipes will be marked as "unable to be created" in the packet, but the client will not display them any different than others you have the create common item level on your sub) (also, henna info lists mark hennas as applicable or not applicable to your class/level inside the packet, but client presents them all the same) For certain features that are bugged in l2off (e.g. related to items that were not designed to be traded or GM view packets (656 and 83)), I aim for correct presentation in the associated client. NP works as a transparent proxy – nothing that would be flagged as a virus by overzealous AV manufacturers. Yes, it works only with standard encryption, so if the client maintains a parallel connection to negotiate encryption with a 3rd party and then ciphers everything according to this separate LIVE key stream, it will not work. Plus, when I called for suggestions before opensourcing this app, I didn't get any to add socket interception or to scan/inject process memory. Also, these features likely could only work on NA clients/servers, where pretty much every security feature is disabled (currently, even GG is not required to play on NA servers). Korea, on the other hand, has everything forced: GG, NI, SO, now even factual ini validation. And they eventually ban if the client fails the check, which is a pain since they also require real ID. For now, I do not have plans for aggressive interception methods. But yes, I would want them as optional features… some day.

I do plan to do that eventually. After all, the reason I made the opcode site was because the incremental loading in NP meant that without actually using NP (or checking out and using ctrl+shift+r) it becomes somewhat hard to follow which opcodes and structures are used for a specific protocol version. For now, you can just browse the NP source for structure XMLs. But beware: most packets in HF folder were validated from non-builder perspective, and the rest were filled in from l2j sources (which means they are most likely wrong). Most new packets in valiance folder were generated from GDL & later non-incremental loading XML files. THERE WERE ISSUES with opcode assignment, so some definitions are lost or incorrect (I still have the file in legacy format, but I never actually re-validated them). Most new packets in ertheia folder were generated from korean Ertheia non-incremental loading XML file. Same issues as with Epeisodion (a.k.a Valiance). Right now, I am finishing up with validating C4 packets (though there are still a few left to validate from C2). After that, I'll move to GF, though I will try my best to investigate C5 (due to so many pledge features originally implemented there) to Gracia P2 while dealing with GF. After that, I plan to review HF, legacy GoD, GDL and kr Ertheia files. Only then would I publish the structures in a format similar to how this opcode website works.

I have opened this thread in the morning to check up on what's new, but I'll have to go soon. Please check this post later today, I will edit it to include cases that I have already stumbled upon. Yes. That's why you have these special 'constant' opcodes in protocol definitions, e.g. <protocol id="54" alias="Infinite Odyssey" category="IO"> <version date="2015-04-22">24</version> <primary> <constant>0x12</constant> <constant>0xB1</constant> <constant>0x11</constant> <constant>0xD0</constant> </primary> <secondary count="269"> <constant>0x70</constant> <constant>0x71</constant> </secondary> <definitions dir="infinite_odyssey" /> </protocol>As these are known to not participate in CM opcode shuffling. Plus, without this obfuscation, NP would be pretty much useless. I honestly have no clue what you are talking about. While doing manual validation, I do take note of what are the client-known structures of certain packets (due to the aforementioned reasons, I only include them as found in the latest client). See the XML comments in this file.

Technically, yes and no. Yes, these opcode mappings were generated automatically. No, because I did some manual validation, as in certain protocol versions, there have been some issues (the generator was being updated, so older lists of older protocols had some opcodes incorrectly skipped/assigned, or doubly assigned some opcodes). I also tried to synchronize packet names with reality, so a few might not exactly match what's in that exact client – the name would come from a later client (see the large explanation below), because the original name is misleading due to changes to logic. For packets that never had a name (some private store packets) had their names assigned manually. 'DummyPacket's that to this day serve a very specific purpose had a name assigned based on how equivalent packets for other features were named. And the biggest letdown you may notice, is the missing SendPrivateStoreBuyBuyList (replaced with SendPrivateStoreSellList). NOT THIS AGAIN. Look. The strings are manually maintained by NC employees. So if someone forgets to update some packet, e.g. 'RequestPartyMatchConfig' for like 3 years after it's structure and logic has been already changed to 'RequestListPartyWaiting', it does not mean that packet still is 'RequestPartyMatchConfig' for these additional 3 years. The same applies to structure strings, EXCEPT it seems that on updates, NC omits certain fields ON PURPOSE. That's why usually the structure presented for widely used packets like ItemList, CI, UI and similar will be outright wrong. E.g. with CI and UI, it is often that you see something like this: You start with some baseline protocol version (some fields may be omitted) A protocol version update arrives, which does not specify CI/UI structure change In reality, you find out new fields have been added, and not necessarily at the end of the packet Another protocol version update arrives, which does specify new fields in CI/UI, but omits those you already found In reality, you find out that the omitted fields are still there Another protocol version update arrives, which specifies even more new fields in CI/UI, but those you found are still nowhere to be seen In reality, you find out that omitted fields are there, and not all new fields are specified AGAIN Another protocol update; both omissions are nowhere to be found, but new fields have arrived This goes on and on with various packets… So really, NC with its project-based workflow and employee migration between them (some employees simply leave) DOES NOT CARE to maintain those structure strings properly (sometimes, that also applies to packet names). Since there is no way to automatically check whether the structure string is up-to-date (esp. if 'x' is involved), I'd rather not present them. Yes, for a fair amount of "simpler" packets, that would work. But that can easily cause people to believe that those strings are actually correct, and fall right into a trap. If someone would like, I could try to jog my memory and check up my validated structs against NC (client) structs to give you at least 10 packets over various protocol versions, where the client struct is just wrong (and continues to be wrong for extended amounts of time).

Pictures are worth more than words. This one doubles as a hyperlink. Additionally, you can view individual packet opcode summaries, such as this for RequestBR_GamePoint: (also accessible from a protocol version's overview) The lists are made for NA L2, which should be fine for NA/EU/RU servers. Neither PTS nor Korean protocols are included. So if you are looking for (e.g. KR-only) 597, 598, 599, 19, 21 or similar ones, you're out of luck.

Hey guys. I would like some information about what is allegedly leaked. Is this just another /script/ leak like Freya? Any thread with complete info on what is available? I do not require the files itself nor excerpts from them. Just info. EDIT: Apparently from the marketplace thread it's a full pack.

I can verify this. C0 336, C1 419 (meifu) [x86] C4 654/656 (PP IRC, ragezone) [x64] - all work on (output of winver)

Any particular reason you are not using https://code.google.com/p/l2oep/source/browse/trunk/L2OFFRetail/L2C4Retail/Script/npcdata.txt? (this comes from a mixed C3 557/560/C4 656 release, which was dubbed "C4 PTS" x64 C4 leak) An alternative is the ragezone live pack, which afaik is just a more complete version with fixes (a.k.a. modifications).

Hi guys, remember the PostPacific C4 leaked CN l2off share? There were many things amiss and many have been dealt with since then. Still, it seems I am unable to find a few missing parts: AuthGateD for L2AuthD_60215. (If it is easier to comprehend game protocol versions, then 654/656. In case of 656, then as it is, right off the NA C4 installer) Media part #2s for lin2db, lin2comm and lin2clancomm. (Not the sqls, missing CN backup parts) Any help is appreciated.

Hi, thanks for the contribution, I will make sure to check it out. Some of my findings: According to Engine.dll, the attached client system is for prelude live (377). According to DBScript (rebelstrik), this is definitely prelude LIVE. (Alliances, pet nickname, etc is only supported by the 377 client) Geodata contains three files modified on 2010-12-24 and all three are damaged (cannot be loaded). It's Gludin, EG and Elmore[Orc]. I guess I can always use C1 PTS's geo, since C0[377] was equivalent, or so I am told. As far as I see, the main difference between the two packs is that the 2nd one has the original ai.obj and does not have geo/pn. Anyway, the 377 server plays fine on a 336 client. Thanks again!

Definitely interested :)

Oh well :(. Thanks for the info though.

Hi guys, I have already looked through google search results, but it seems all I can come up with is long dead links. I am looking for an either prelude live (377 client) or prelude pts (336 client) l2off pack. Perhaps someone has one stockpiled and could upload it somewhere for me? Not interested in extenders that make a C1 (or later) server compatible with prelude clients. Also not interested in C1 (or later) servers, regardless if clean or with extenders. Thanks in advance.

The title says it all. If you look up the DNS history, there is no server online at the old address, so this is not a domain name hijack. They're simply gone.

3. xEnemy has some

Reproducible - any teleporter (this one is in TI): 19 27 61 10 48 3C 00 68 00 74 00 6D 00 6C 00 3E 00 3C 00 62 00 6F 00 64 00 79 00 3E 00 26 00 24 00 35 00 35 00 36 00 3B 00 3C 00 62 00 72 00 3E 00 3C 00 62 00 72 00 3E 00 3C 00 61 00 20 00 61 00 63 00 74 00 69 00 6F 00 6E 00 3D 00 22 00 62 00 79 00 70 00 61 00 73 00 73 00 20 00 2D 00 68 00 20 00 74 00 65 00 6C 00 65 00 70 00 6F 00 72 00 74 00 5F 00 34 00 37 00 31 00 39 00 31 00 37 00 30 00 37 00 30 00 34 00 5F 00 30 00 5F 00 35 00 37 00 5F 00 31 00 32 00 30 00 39 00 30 00 33 00 32 00 39 00 39 00 39 00 5F 00 33 00 22 00 20 00 6D 00 73 00 67 00 3D 00 22 00 38 00 31 00 31 00 3B 00 46 00 3B 00 31 00 30 00 31 00 30 00 30 00 30 00 34 00 22 00 3E 00 3C 00 66 00 73 00 74 00 72 00 69 00 6E 00 67 00 3E 00 31 00 30 00 31 00 30 00 30 00 30 00 34 00 3C 00 2F 00 66 00 73 00 74 00 72 00 69 00 6E 00 67 00 3E 00 3C 00 2F 00 61 00 3E 00 3C 00 62 00 72 00 31 00 3E 00 3C 00 61 00 20 00 61 00 63 00 74 00 69 00 6F 00 6E 00 3D 00 22 00 62 00 79 00 70 00 61 00 73 00 73 00 20 00 2D 00 68 00 20 00 74 00 65 00 6C 00 65 00 70 00 6F 00 72 00 74 00 5F 00 34 00 37 00 31 00 39 00 31 00 37 00 30 00 37 00 30 00 34 00 5F 00 31 00 5F 00 35 00 37 00 5F 00 31 00 32 00 30 00 39 00 30 00 33 00 32 00 39 00 39 00 39 00 5F 00 33 00 22 00 20 00 6D 00 73 00 67 00 3D 00 22 00 38 00 31 00 31 00 3B 00 46 00 3B 00 31 00 30 00 31 00 30 00 31 00 35 00 36 00 22 00 3E 00 3C 00 66 00 73 00 74 00 72 00 69 00 6E 00 67 00 3E 00 31 00 30 00 31 00 30 00 31 00 35 00 36 00 3C 00 2F 00 66 00 73 00 74 00 72 00 69 00 6E 00 67 00 3E 00 3C 00 2F 00 61 00 3E 00 3C 00 62 00 72 00 31 00 3E 00 3C 00 61 00 20 00 61 00 63 00 74 00 69 00 6F 00 6E 00 3D 00 22 00 62 00 79 00 70 00 61 00 73 00 73 00 20 00 2D 00 68 00 20 00 74 00 65 00 6C 00 65 00 70 00 6F 00 72 00 74 00 5F 00 34 00 37 00 31 00 39 00 31 00 37 00 30 00 37 00 30 00 34 00 5F 00 32 00 5F 00 35 00 37 00 5F 00 31 00 32 00 30 00 39 00 30 00 33 00 32 00 39 00 39 00 39 00 5F 00 33 00 22 00 20 00 6D 00 73 00 67 00 3D 00 22 00 38 00 31 00 31 00 3B 00 46 00 3B 00 31 00 30 00 31 00 30 00 31 00 35 00 38 00 22 00 3E 00 3C 00 66 00 73 00 74 00 72 00 69 00 6E 00 67 00 3E 00 31 00 30 00 31 00 30 00 31 00 35 00 38 00 3C 00 2F 00 66 00 73 00 74 00 72 00 69 00 6E 00 67 00 3E 00 3C 00 2F 00 61 00 3E 00 3C 00 62 00 72 00 31 00 3E 00 3C 00 61 00 20 00 61 00 63 00 74 00 69 00 6F 00 6E 00 3D 00 22 00 62 00 79 00 70 00 61 00 73 00 73 00 20 00 2D 00 68 00 20 00 74 00 65 00 6C 00 65 00 70 00 6F 00 72 00 74 00 5F 00 34 00 37 00 31 00 39 00 31 00 37 00 30 00 37 00 30 00 34 00 5F 00 33 00 5F 00 35 00 37 00 5F 00 31 00 32 00 30 00 39 00 30 00 33 00 32 00 39 00 39 00 39 00 5F 00 33 00 22 00 20 00 6D 00 73 00 67 00 3D 00 22 00 38 00 31 00 31 00 3B 00 46 00 3B 00 31 00 30 00 31 00 30 00 31 00 35 00 35 00 22 00 3E 00 3C 00 66 00 73 00 74 00 72 00 69 00 6E 00 67 00 3E 00 31 00 30 00 31 00 30 00 31 00 35 00 35 00 3C 00 2F 00 66 00 73 00 74 00 72 00 69 00 6E 00 67 00 3E 00 3C 00 2F 00 61 00 3E 00 3C 00 62 00 72 00 31 00 3E 00 3C 00 61 00 20 00 61 00 63 00 74 00 69 00 6F 00 6E 00 3D 00 22 00 62 00 79 00 70 00 61 00 73 00 73 00 20 00 2D 00 68 00 20 00 74 00 65 00 6C 00 65 00 70 00 6F 00 72 00 74 00 5F 00 34 00 37 00 31 00 39 00 31 00 37 00 30 00 37 00 30 00 34 00 5F 00 34 00 5F 00 35 00 37 00 5F 00 31 00 32 00 30 00 39 00 30 00 33 00 32 00 39 00 39 00 39 00 5F 00 33 00 22 00 20 00 6D 00 73 00 67 00 3D 00 22 00 38 00 31 00 31 00 3B 00 46 00 3B 00 31 00 30 00 31 00 30 00 31 00 35 00 37 00 22 00 3E 00 3C 00 66 00 73 00 74 00 72 00 69 00 6E 00 67 00 3E 00 31 00 30 00 31 00 30 00 31 00 35 00 37 00 3C 00 2F 00 66 00 73 00 74 00 72 00 69 00 6E 00 67 00 3E 00 3C 00 2F 00 61 00 3E 00 3C 00 62 00 72 00 31 00 3E 00 3C 00 61 00 20 00 61 00 63 00 74 00 69 00 6F 00 6E 00 3D 00 22 00 62 00 79 00 70 00 61 00 73 00 73 00 20 00 2D 00 68 00 20 00 74 00 65 00 6C 00 65 00 70 00 6F 00 72 00 74 00 5F 00 34 00 37 00 31 00 39 00 31 00 37 00 30 00 37 00 30 00 34 00 5F 00 35 00 5F 00 35 00 37 00 5F 00 31 00 32 00 30 00 39 00 30 00 33 00 32 00 39 00 39 00 39 00 5F 00 33 00 22 00 20 00 6D 00 73 00 67 00 3D 00 22 00 38 00 31 00 31 00 3B 00 46 00 3B 00 31 00 30 00 31 00 30 00 36 00 34 00 38 00 22 00 3E 00 3C 00 66 00 73 00 74 00 72 00 69 00 6E 00 67 00 3E 00 31 00 30 00 31 00 30 00 36 00 34 00 38 00 3C 00 2F 00 66 00 73 00 74 00 72 00 69 00 6E 00 67 00 3E 00 3C 00 2F 00 61 00 3E 00 3C 00 62 00 72 00 31 00 3E 00 3C 00 61 00 20 00 61 00 63 00 74 00 69 00 6F 00 6E 00 3D 00 22 00 62 00 79 00 70 00 61 00 73 00 73 00 20 00 2D 00 68 00 20 00 74 00 65 00 6C 00 65 00 70 00 6F 00 72 00 74 00 5F 00 34 00 37 00 31 00 39 00 31 00 37 00 30 00 37 00 30 00 34 00 5F 00 36 00 5F 00 35 00 37 00 5F 00 31 00 32 00 30 00 39 00 30 00 33 00 32 00 39 00 39 00 39 00 5F 00 33 00 22 00 20 00 6D 00 73 00 67 00 3D 00 22 00 38 00 31 00 31 00 3B 00 46 00 3B 00 31 00 30 00 31 00 30 00 30 00 30 00 35 00 22 00 3E 00 3C 00 66 00 73 00 74 00 72 00 69 00 6E 00 67 00 3E 00 31 00 30 00 31 00 30 00 30 00 30 00 35 00 3C 00 2F 00 66 00 73 00 74 00 72 00 69 00 6E 00 67 00 3E 00 3C 00 2F 00 61 00 3E 00 3C 00 62 00 72 00 31 00 3E 00 3C 00 61 00 20 00 61 00 63 00 74 00 69 00 6F 00 6E 00 3D 00 22 00 62 00 79 00 70 00 61 00 73 00 73 00 20 00 2D 00 68 00 20 00 74 00 65 00 6C 00 65 00 70 00 6F 00 72 00 74 00 5F 00 34 00 37 00 31 00 39 00 31 00 37 00 30 00 37 00 30 00 34 00 5F 00 37 00 5F 00 35 00 37 00 5F 00 31 00 32 00 30 00 39 00 30 00 33 00 32 00 39 00 39 00 39 00 5F 00 33 00 22 00 20 00 6D 00 73 00 67 00 3D 00 22 00 38 00 31 00 31 00 3B 00 46 00 3B 00 31 00 30 00 31 00 30 00 37 00 33 00 39 00 22 00 3E 00 3C 00 66 00 73 00 74 00 72 00 69 00 6E 00 67 00 3E 00 31 00 30 00 31 00 30 00 37 00 33 00 39 00 3C 00 2F 00 66 00 73 00 74 00 72 00 69 00 6E 00 67 00 3E 00 3C 00 2F 00 61 00 3E 00 3C 00 62 00 72 00 31 00 3E 00 3C 00 61 00 20 00 61 00 63 00 74 00 69 00 6F 00 6E 00 3D 00 22 00 62 00 79 00 70 00 61 00 73 00 73 00 20 00 2D 00 68 00 20 00 74 00 65 00 6C 00 65 00 70 00 6F 00 72 00 74 00 5F 00 34 00 37 00 31 00 39 00 31 00 37 00 30 00 37 00 30 00 34 00 5F 00 38 00 5F 00 35 00 37 00 5F 00 31 00 32 00 30 00 39 00 30 00 33 00 32 00 39 00 39 00 39 00 5F 00 33 00 22 00 20 00 6D 00 73 00 67 00 3D 00 22 00 38 00 31 00 31 00 3B 00 46 00 3B 00 31 00 30 00 31 00 30 00 37 00 34 00 30 00 22 00 3E 00 3C 00 66 00 73 00 74 00 72 00 69 00 6E 00 67 00 3E 00 31 00 30 00 31 00 30 00 37 00 34 00 30 00 3C 00 2F 00 66 00 73 00 74 00 72 00 69 00 6E 00 67 00 3E 00 3C 00 2F 00 61 00 3E 00 3C 00 62 00 72 00 31 00 3E 00 3C 00 62 00 72 00 3E 00 3C 00 2F 00 62 00 6F 00 64 00 79 00 3E 00 3C 00 2F 00 68 00 74 00 6D 00 6C 00 3E 00 00 00 00 00 00 00 01 00 00 00Interpretation (formatted the one-line html for your convenience): OID: Milia, Gatekeeper [NPC] (1209032999) Message: <html><body>&$556;<br><br> <a action="bypass -h teleport_4719170704_0_57_1209032999_3" msg="811;F;1010004"><fstring>1010004</fstring></a><br1> <a action="bypass -h teleport_4719170704_1_57_1209032999_3" msg="811;F;1010156"><fstring>1010156</fstring></a><br1> <a action="bypass -h teleport_4719170704_2_57_1209032999_3" msg="811;F;1010158"><fstring>1010158</fstring></a><br1> <a action="bypass -h teleport_4719170704_3_57_1209032999_3" msg="811;F;1010155"><fstring>1010155</fstring></a><br1> <a action="bypass -h teleport_4719170704_4_57_1209032999_3" msg="811;F;1010157"><fstring>1010157</fstring></a><br1> <a action="bypass -h teleport_4719170704_5_57_1209032999_3" msg="811;F;1010648"><fstring>1010648</fstring></a><br1> <a action="bypass -h teleport_4719170704_6_57_1209032999_3" msg="811;F;1010005"><fstring>1010005</fstring></a><br1> <a action="bypass -h teleport_4719170704_7_57_1209032999_3" msg="811;F;1010739"><fstring>1010739</fstring></a><br1> <a action="bypass -h teleport_4719170704_8_57_1209032999_3" msg="811;F;1010740"><fstring>1010740</fstring></a><br1> <br></body></html> Title: None (0) Response: Yes (1) Notice, that each bypass contains %npcObjectId% (after replace, ofc).

You know what one good thing started with GoD, and is now done on every single update? Removing obsolete, useless systems: SSQ, Castle Sieges, TW (goodbye easy nobility), all quests*, crafting & materials, etc etc. * some starter NPCs remain, but quests are broken, like Hidden Truth series. Replaced by few short high reward quests which do not take time nor effort to implement. So yeah, if YOU would jump to Dimensional Strangers straight ahead, you'd be much more correct if you claim you have it more retail-like than if you stick with HF (terribly outdated) and below. It works BOTH ways here. Too bad nobody actually did this, as I see.. Now before you write another 50 pages of comments, I'd like to point out that we went far offtopic. First of all, this thread does not belong in L2OFF section, after all. Secondly, this whole discussion should be moved to... L2 general discussion? I think it would be best if someone closed this thread and moved it to archive, after all. BECAUSE: I have my answer, and these 1,5 additional pages of butthurt comments between two kids is making my eyes hurt. I love this quote. It shows the stereotypical L2 developers attitude towards the server side. Behold, after 7-8 years (first reference found in ru C3 network protocol description), l2jserver manages to implement 0xB5 AllianceInfoPacket, only when some unknown contributor gives the full format to them. No matter how much YOU want to sound elite - EVERY SINGLE PACKET HANDLING CODE IS DONE CLIENT SIDE and all values can be inferred from UE code, without the need of sending some "omg I don't know what is this" "NULLED" values, which somewhy is the fetish of L2 developers since the beginning (C1 leak repurposed for C2/C3/C4, l2jserver 0.x.y). HOWEVER, your point is 100% true - if you look at l2j or at l2off extenders, you are guaranteed to win any claim that aside from few (< 10) exceptions, ALL new packets will be done WRONG (with your so-called "NULLED" values). Take a look at Castle Siege** related packets - Att/Def registration, siege time selection list - these were NEVER completed, and now CS is gone altogether, so they WILL NEVER BE. They are fucking wrong, because There are no devs who care. All they want when they do not get a L2OFF episode X RC leak is to get packets working only to the point where they can play on their "OH YEAH MAKE ME COME" C1 server (I hear C1 was later replaced by IL, and supposedly with GF nowadays). No idea why they love those obsolete chronicles so much. ** - this feature has already been removed from L2 gameplay.

Same can be said about L2OFFs with extenders:

The more you play on actual NA retail, the more you understand what kind of shitty server they run - constant NPC server crashes (luckily, nowadays it gets rebooted in a few minutes; in HF times it used to take a few hours). The geodata is shit, with invis walls in both newer and old, C1-esque territories (lol @ Forsaken Plains near GC - you move and you stop, even though the terrain is completely flat, but your char insists you move around an invisible wall). As I recall from HF and GoD, the same shit is with the area right below the GC (might be fixed now, haven't checked yet), which is also C1-esque. Features get disabled due to critical exploits, because fixes are always delayed to the next (or the second next, or the third next) maintenance: at the moment of speaking, all fishermen are disabled. There are plenty of nonworking quests, some quests randomly show you an empty HTML (and do not refund lost quest items). However, what I always liked about L2OFF is the movement (10x better than l2j's insta-turn; except PvP bots on off still managed to pull that off... somehow?) and, of course attack and skill use system (also 10x better than l2j, where you can keep shooting arrows and using skills without any delay inbetween, resulting in nonsensical attack speed). While it is no doubt good that OFF has new features, at least in NA retail (I mostly played HF and some GoD, before they started promoting 'login to win' events) if you actually use them, you can't even deal with how buggy they are. Naturally, if you have a KR account, then things are a bit different, let's say the client is not mutilated for a start...

I was looking on what to replace dated sniffers to sniff retail packets, and discovered this: By any chance, could someone elaborate on: What is the name of this sniffer? Where could I get it? What is the latest protocol version supported?

Surfing various L2 related sites, I managed to harvest this screenshot: Despite the different Korean font, I could not identify the chronicle - does this mean that someone leaked Epeisodion++ L2OFF?