Jump to content

Recommended Posts

Posted

Greetings, everyone!

 

(That's another method to cause the same effect, so I'll set up a new thread...)

 

Since the mob names of the treasure boxes got fixed (now they're sharing the same name with the regular treasure chests), it is not possible, to distinguish between Treasure Chest (eating your DX Chest Keys attacking you, dropping same crap as a regular mob) and a Treasure Box (opens, if you use such a key, drops enchants / high amount of adena).

 

Well, actually you can use the IG walker, as already mentioned in the existing thread, to see the boxes on the map / on the moblist, but this is kinda dumb, in my opinion (I got pissed after a few boxes).

 

So I edited the npcname-e.dat.

 

Result:

p000000nedzg1.jpg

 

Just place this file into your ".../Lineage II/system/" dir and start the game.

 

Now you also can set up a regular ingame macro to locate the (good) boxes (/target Treasure Box).

 

But remember : If you pop a box, there's a 50% chance, that this spot gets blocked by a bad one (Chest). So if there are too many chests in your area, just send some of them back to hell. Then some good ones (Boxes) can spawn. ;3

 

Working with C4off servers.

 

 

- Berry

 

 

File URL : http://www.elitepvpers.de/forum/index.php?s=&act=Attach&type=post&id=659724 (that's not a forum link) for C4

 

File URL : http://www.elitepvpers.de/forum/index.php?s=&act=Attach&type=post&id=660390 (also not a forum link) for Interlude

 

File PW : thxjack.epvpftw

 

Posted

Does this one work with an Interlude client?

Well it shouldn't work, couse interlude uses diferent npcname-e.dat(has more NPC's in it).

BUT you could just do the same thing with interlude client

Posted

If someone would upload the interlude file, I would edit that one aswell (although you can do it yourself, it is no big deal at all).

 

Hmm... Dunno, link is working fine for me - I will set it up to a 1-click hoster later.

Posted

Ok the first exploit was from me and i want to tell you some servers like l2dex have autoupdaters...an you cant run l2 without running the updater and if you run the updater it will overwrite your file...and you need to copy it every time so my exploit is  not that dumb

Guest
This topic is now closed to further replies.



  • Posts

    • fixed the flickering , if you noticed to an other specific page please let me know
    • And Discord: https://discord.gg/3aYqWNqb
    • Ofc: https://discord.gg/3aYqWNqb
    • You can find some H5 skins shared in old L2 modding Discords, but most of the higher‑quality ones are either paid or come bundled with full client edits. I usually mix in commissioned work and whatever I can patch myself. On a side note, I fund a lot of these commissions by selling off game items through instant sell cs2 skins, which has been a quick way for me to get some cash for projects.
    • There is no need for gRPC in this case, even tho originally it was gRPC based but since we don't need it to be bi-directional, we switched to simple http requests for the web calls and SSEs for the data streamed from the server. There are distributed locks in place to precent race conditions between actions that can happen between multiple web instances and the server.   Local models can also be slow depending on the model, and most external models can actually be faster than local ones if you use Flash 2.5 or something along those lines. I am running on 512GB of Unified Memory on my Mac Studio M3 Ultra so the speed of the local model for a small model is pretty good but I tested it with Gemini too and it works equally as fast and in some cases faster. The way it works is that I'm using pgvector (one of the benefits of moving to Postgres) to search the data and see what the player can see etc and there is some batching of the next few actions for 2-4 seconds for the user until the next LLM request fires. The batching also includes branching on logic so if they for example fall under some HP they will move to kiting instead of attacking or maybe they heal etc.   Everything is authed and permission-based. The server and the backend of the frontend have secure communication between them, either with a symmetric key (not recommended for production) or a certificate (the recommended way), so there is no worry. It's all tied to the account's access level, etc., so nobody can make an action that they normally wouldn't be allowed to do. Even the MCP is token-based, and there are prompt injection protections in place. The MCP is audited, and every mutation needs confirmation. The admin area is only accessible to the admin account anyway so normal users can't access it.  
  • 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..