Jump to content

Recommended Posts

Posted

many people want to change colors of system chat messages, you can use either some utils, like l2asm/disasm, l2 fileedit, lineage utils, or decipher file with l2encdec, and edit it with hexedit, or other editor (i didn't recomend notepad, or wordpad). i hope, you'll find this info usefull either you want to build own tool to edit this file, or u will be editing it manualy, or u are simply curious.

 

you may find some info about this file also in l2asm/disasm tool, but it's very brief.

 

first 4 bytes is count of messages in file, it's unsigned int32.

next comes messages, one after another.

structure of message is following

C3,C4,C5

Unsigned Int32 id;

Unsigned Int32 unknown; // 01 00 00 00

String message;

Unsigned Int32 group;

4 Bytes rgba;

String item_sound;

String sys_msg_ref;

 

C6,CT1

Unsigned Int32 id;

Unsigned Int32 unknown; // 01 00 00 00

String message;

Unsigned Int32 group;

4 Bytes rgba;

String item_sound;

String sys_msg_ref;

5 bytes on_screen_attrib;

String on_screen_msg;

String source;

 

id - ID of message - messages are numbered ascending, with unique ID, and incement 1 (so, number of messages is also ID o last message)

unknown - 4 bytes, which i still didn't decipher, and didn't found any info about, but for every messages it's in hex 01 00 00 00

message - unicode text of message, can be also ansi, for localized version. it's null terminated string. if you are editing this manualy structure is simple

ANSI first byte - number of message characters, second byte - for ansi, here starts the message text, after message there is 00 (null character)

UNICODE first byte - number of characters, second byte is 01, next message follows, every char ocupies 2 bytes, after message there is 00 (null character)

group - message source group (see explanation for source field)

rgba - it's color of message in order Red,Green,Blue,Alpha Channel (mostly is alpha not used)

item_sound - name of sound resource, it's in form sourcefile.itemname, eg. ItemSound3.sys_failed means, that message has assigned sound sys_failed, from ItemSound3.uax file

sys_msg_ref - system message refference - not sure, but possibly message that triggers additional action in client (like, class change, when you get mail, etc.)

 

as of interlude, there are new attributes

on_screen_attrib - you know that big message, which appears, when match on olympiad started, castle siege started, etc.? this is 5 bytes, related to that message

1st byte - position on screen, if you divide screen to 3x3 matrix, then start numbering from left in row, skipp left down, because there is chat window, it looks like

1 2 3

4 5 6

X 7 8

2nd byte - currently don't know, but on every message it's 0

3rd byte - duration of message (eg. how long is diplayed, in seconds)

4th byte - didn't succesfully decipher, but if it's 1, then message appears, if any other number, message is not displayed

5th byte - didn't successfully deciphered, mostly set to 0, for some messages is set to 1

on_screen_message - this is text, of that big message, format is the same, as for normal message (see above)

source - ansi message, which identifies source of message, this part is also related to message group (see above)

group - source - explanation

0 - none - messages without source (or class if you prefer that term)

0 - siege - castle/fortress siege related messages

1 - battle - nondamage combat messages (successfull defense, critical hit, miss, etc.)

2 - server - general server messages

3 - damage - didn't need explanation (you make damage, you take damage)

4 - popup - message is displayed in popup window

5 - error - if any action produces error, here you go (cancel trade, failed invitation, failed login, etc.)

6 - petition - use of petition system

7 - useitems - didn't need explanation (eg. use shots, potions, enabled shots, equip armor, etc.)

 

if you have any aditional info, about items, that i have not deciphered yet, or any corrections, you are welcome.

 

Credits to mexmer

Source www.postpacific.com

 

PS : If some1 posted it before , delete my topic !

 

 

Mod Edit: Prefix added. => A-Style

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Posts

    • First of all, I never challenged you at any point.   Second, congratulations—this is what you should have done from the start: shown how it worked, how to exploit it, etc. Now, let’s look at the facts:   The flaw requires the person to be the OWNER of the castle.   It requires the use of third-party programs or a modified client—and most private servers don’t even allow the use of modified clients, thanks to their anti-cheat systems.   Are you honestly certain that a castle owner on a private server would risk losing their account just to pull off this exploit? They’d have to be a complete idiot.   You’ve spent months going on about how you discovered a bug that has ZERO impact on the actual gameplay—congratulations.   I’m not saying that flaws are bad or that they shouldn’t be fixed—in fact, the flaw *was* fixed.   What I’m saying is that you’ve been harping on the same point for months, even though the issue had already been resolved in the closed branch.   It’s the prerogative of those who maintain the code to fix things however they see fit, don’t you think?   And learn this: when you report a bug, you MUST: 1- Report the bug (obviously) 2- Explain in detail how the bug occurs 3- Prove that the bug actually happens   And instead of contributing to the project through the proper, public channels, you chose to turn this into a whole circus—I’d just like to understand why...   It’s a good thing everyone in this thread will get to see who the "asshole" is.
    • To use this exploit you have to:   1) Have access to the castle vault, aka you have to own a castle. 2) Send through Adrenaline Engine.BypassToServer(Bypass) as emommy said 3) In the crafted packet you will put a negative amount eg -100000000 What this does is it multiplies it by -1 so it becomes positive. 4) You won't see anything in your inventory, but if you open the castle vault through the Chamberlain you will see that the warehouse now has 10000000 adena. The negative became positive. 5) Withdraw the adena normally and you now have all the adena you need.   I wouldn't bother explaining how to do it, but this idiot (Galagard) wanted to challenge me. And from what I can see, they haven't patched the exploit even if I reported it to them a week ago so it's obvious that people will start sharing it around.   Maybe I should start positing here instead of the official channels.   All public versions of L2JMobius for all chronicles are vulnerable and not patched yet.   And thanks to this idiot (Galagard), everyone now knows.   Baldurian. EDIT:    Ok I just got informed that Mobius decided to accept the fix in the public repo.   So I will now post a proof of the exploit as Galagard requested. Normally I don't do so, but my good friend Galagard who has his nose so far stuck up his asshole, insulted me, and challenged me to show proof:     And to be fair to everyone, this is not an L2JMobius issue as the thread claims. It's L2JServer leftover, so if you have L2JServer derivative packs, you should patch too. 
    • Already fixed in subscriber version, but this bug report is classified as "Invalid" because since the author did not explain the method in detail, the validation flaw does indeed exist—but that alone does not prove it is possible to duplicate adena or any other item by exploiting said flaw. It looks like yet another AI hallucinating a vulnerability, then deducing that it could be used to exploit a different vulnerability. No have proofs in video or a detailed way to reproduce the potential failure Go find something else to do, Baldurian; you don’t even know how to exploit the flaw you reported yourself.
    • Interface sources for P196 (Secret of Empire 2 or aka Fafurion) for Main/Classic. This protocol is commonly used for classic interlude. You can use the xdat editors which support this protocol from my other shares.   NWindow + Interface UC + L2Editor Compiler   Download  
    • Interface sources for P166 (Secret of Empire 1) for Main/Classic. This protocol is commonly used for classic interlude. You can use the xdat editors which support this protocol from my other shares.   NWindow + Interface UC + L2Editor Compiler   Download  
  • Topics

×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..