Jump to content

Recommended Posts

Posted (edited)

Last alive server was l2 coyote ,looks like FREYA CLIENT ended with it...

 

From the last freya servers i saw only max 80-130 real online (l2 olynth had 200+ so it was the last real good freya server)

 

 

Hi5 gets easy 400 even 500 online as a PVP SERVER ,wh0t whoat??? why hi5? well i dont know ,i dont care

 

what i am asking is why u give up on Freya client just because some servers sucks or getting old? screw the logic ,why interlude is still alive though its worst client (for me at least ,i rather play a l2off c3 lol) . So yeah ,basically i wanted to make a freya server that will last for a very long time (l2sexi example) and not a hi5 one but now im making a hi5 because of that...

 

So whats the deal ,even epilogue is dead and its my favorite client for pvp servers ,dead where? here? sure! ,look at russians ,they only play epilogue midrates/pvp servers (most of servers are epilogue ,2nd are hi5) so what cuz i dont understand ,it have something to do with people who speak english ,maybe u hate freya/epilogue? 

 

 

Are you clients rascists?

Edited by Karasu
Posted (edited)

I think H5 is that popular cause it introduced many new stuff that improved the game without affecting its essence (as GOD chronicle did with Awakening system).

Edited by Lokus
Posted

I think people who relate clients to population should be hanged with a buttplug in their throats.

 

It makes people believe stupid sht like server quality depends on chronicle.

 

Then you gotta alotta hanging to do....

Posted

I think l2 general die :D i play a lot of years l2 but when i see the GOD GloryDays or Lindvior i Love it....
Its something new and fresh all that think with l2 untill h5 the same and the same the people start bored

The only way is the Interlude a bit closer to old time classic l2...

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



  • Posts

    • sell adena l2rebon signature x1 - 1kk = 1 dollars l2reborn x10 - 500kk = 4 dollars E-Global x Lu4 - 1kk = 2 dollars BOHPTS - x20-x500 TOP PRICE DISCORD - GODDARDSHOP TELEGRAM - MMOPROMO Also on sale are Epic jewelry, Clothes at a very good price
    • Hello Sorry, my Discord is: ave7309
    • “Hello, I’d like to present a short description of the server. Everyone starts equally at max level 80. The server includes a custom buffer, custom class master, custom weapons and armors, custom zones, custom teleporter, custom raid bosses, and much more. I’ll leave a link in the description for those who want to see how everything looks inside. The server is only open on weekends, and you can find more news via the Facebook link.”   https://www.facebook.com/profile.php?id=61578869175323
    • 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.    
  • Topics

×
×
  • Create New...

AdBlock Extension Detected!

Our website is made possible by displaying online advertisements to our members.

Please disable AdBlock browser extension first, to be able to use our community.

I've Disabled AdBlock