Hello cheaters. I want to make shadow items expiring even if player is offline or doesnt wear them.
1. Make counter start when player obtain the item, not when equip it.
2. Remove all checks that can stop the task.
Tryskell: If you speak of aCis, try dropping all ShadowItemTaskManager.getInstance().remove( method calls, and ShadowItemTaskManager onUnequip( content. Basically said, what you want is one time you put the item, the counter continue no matter what.
3. Keep counting when player is offline (db storage).
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
1. You where subscriber 3 years ago.
2. There is no current L2jMobius 2.8 Seven Signs version. Subcriber or not.
3. You have your answer from multiple forums that more items is more delay.
1. Optimize Packet Serialization
Look in ItemList.java or wherever the inventory packet is constructed.
Instead of building the packet with inefficient string concatenation or repeated allocations, use a preallocated buffer and avoid creating new objects for each item.
Mobius sources are Java-based, so profiling with something like VisualVM or YourKit can help see where most time is spent.
2. Avoid Sending the Full List Each Time
Modify the server to send only changed items (diff packets) when the inventory window opens.
Some newer forks implement this as “lazy loading” or paged inventory so the client only loads e.g. 100 items at a time.
3. Limit the Inventory Size Per Page
Instead of showing all 500 slots at once, split the inventory into pages/tabs (100 slots each).
When the user switches a tab, send only that page’s items.
This requires some client-side editing, but it’s the most user-friendly long-term fix.
4. Database & Cache Optimizations
Ensure your items table is indexed by owner_id to make the query for player items fast.
Cache item templates and static data so they are not reloaded every time the inventory is shown.
⚠️ Things to Keep in Mind
Increasing slots from 80 → 500 does not just change a number — it multiplies the workload for packet building and UI rendering.
You can’t fully avoid some extra cost with 500 items, but you can keep it under a few milliseconds if you optimize how and when the data is sent.
i think it's the auto sorting of the interface that sucks, check InventoryWnd script in interface.u, or completely disable the request item list packet when toggling the inventory window (also in InventoryWnd script or similar name)
Question
raF
Hello cheaters. I want to make shadow items expiring even if player is offline or doesnt wear them.
1. Make counter start when player obtain the item, not when equip it.
2. Remove all checks that can stop the task.
Tryskell: If you speak of aCis, try dropping all ShadowItemTaskManager.getInstance().remove( method calls, and ShadowItemTaskManager onUnequip( content. Basically said, what you want is one time you put the item, the counter continue no matter what.
3. Keep counting when player is offline (db storage).
Edited by raF23 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.