Jump to content

Recommended Posts

Posted

Hello,

I am looking for a method to use local images inside the Lineage 2 Interlude client. Specifically, I want to use the <img src="path/to/image.png"> tag to display PNG or BMP files in the in-game HTML reader.

 

How can I achieve this?

Posted
1 hour ago, lampros1996 said:

Hello,

I am looking for a method to use local images inside the Lineage 2 Interlude client. Specifically, I want to use the <img src="path/to/image.png"> tag to display PNG or BMP files in the in-game HTML reader.

 

How can I achieve this?

You can't. The image needs to be stored in the client, inside any kind of client package (ukx, utx, usx, uax, u, etc).
You can't send images from server to client.

Posted (edited)
8 hours ago, 911reg said:

You can't. The image needs to be stored in the client, inside any kind of client package (ukx, utx, usx, uax, u, etc).
You can't send images from server to client.

What about Clan Insignia (emblem), is it not available on Interlude? We can send picture from the server to the client like that on HF, which are then stored in, and acceessible from, the Crest.utx.

Disclaimer: I haven't played interlude for 15+ years, so pardon my memory lapse.

Edited by Salty Mike
Posted
4 hours ago, Salty Mike said:

What about Clan Insignia (emblem), is it not available on Interlude? We can send picture from the server to the client like that on HF, which are then stored in, and acceessible from, the Crest.utx.

Disclaimer: I haven't played interlude for 15+ years, so pardon my memory lapse.

I'm pretty sure you can, ye, but definitely not png images

maybe if someone builds a system to show images by sending like 1500 crests to build a big image? :^)

Posted (edited)
2 hours ago, 911reg said:

I'm pretty sure you can, ye, but definitely not png images

maybe if someone builds a system to show images by sending like 1500 crests to build a big image? :^)


You sure can. You just gotta send them with the Insignia/Emblem packet, and not the clan/ally crest one. The images are saved exactly as PNG files in L2jEternity and they show up just fine. Sure they are not MB in size, but up to 150kb each, which is not that small in terms of dimensions - 256x256 px. In comparison, the crests are 20-30 times smaller. So, to cover the entire background of the Community Board, you'd need like 2 rows of 3 images. Not terribly bad, imo. 😄

Edited by Salty Mike
Posted (edited)
1 hour ago, Salty Mike said:


You sure can. You just gotta send them with the Insignia/Emblem packet, and not the clan/ally crest one. The images are saved exactly as PNG files in L2jEternity and they show up just fine. Sure they are not MB in size, but up to 150kb each, which is not that small in terms of dimensions - 256x256 px. In comparison, the crests are 20-30 times smaller. So, to cover the entire background of the Community Board, you'd need like 2 rows of 3 images. Not terribly bad, imo. 😄

As far as i'm aware they're smaller in older clients, including h5 (64x64?)

Either way it seems impractical to me, i'd rather throw a texture in a proper utx and call it a day

Edited by 911reg

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

    • TG Support: https://t.me/buyingproxysup | Channel: https://t.me/buyingproxycom Discord support: #buyingproxy | Server: Join the BuyingProxy Discord Server!  Create your free account here
    • I think you should check the video more carefully you missing something very important 😛      
    • Im responding to an anonymous account with 3 posts, almost no background, and practically zero useful information added to the discussion. On top of that, the topic title is misleading  calling it "Lucera Source Code" gives a completely different impression from what is actually being presented.   I didn’t say anything different. Therefore, I have no clue how his process produces the same desirable result.   And here you are creating drama. Your topic title clearly says "Lucera Source Code," which is not actually the case, or at least that’s how it looked when I first clicked on it, so I don’t think I was completely off. There’s also no significant information about your process like  what difficulties you faced, what tools you used, or anything else meaningful. Yet you still expect others to provide value based on what? I’m not talking about your project itself which, by the way, good job. I’m talking about the topic itself as a source of value for this forum, because right now it doesn’t really offer much in that regard. So regarding the semantics, yes, wording does matter.  
    • You are funny guy! 😄 😄 😄    I was working with Lucera long before “AI apps” became fashionable. This was not something I generated in one day with a prompt. It took me years of work, testing, debugging and fixing broken decompiled code.   Of course a decompiled source is not the original private repository with the original comments, history and developer structure. Nobody said it is the same Git repository. But saying it is only “guesses” is also wrong.   When you decompile, rebuild, fix thousands of compile/runtime issues, restore broken logic, reconnect scripts, fix bad casts, repair database calls, compile it again and run it in-game, at that point it is no longer just a guess.   It becomes a working reconstructed source base!   The important part is not whether it is byte-for-byte identical to the original private source. The important part is that I can now work directly inside the code, change core logic, rebuild scripts, fix bugs and continue development without being locked behind closed binaries.   Does it compile? Yes. Does it run in-game? Yes. Can I modify core systems directly? Yes. Can I continue development independently? Yes.   So call it reconstructed, decompiled, cleaned, restored or whatever name you prefer. The result is still the same: I have a working source environment that gives me control over the lucera2 project.   And that was exactly the goal!   🙂 
  • 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..