Jump to content

Recommended Posts

Posted

An well developed java interlude server had ~1200 online without any crashes.

ppl talked about host :)

and a well developed java serv cand have ~4k ppl, look at dex (lineage.ro) ;)

 

Not only you, i can bet, if aCis is finished and works properly, at least 85% of new servers(ofc with developers that know/understand 1-2 things) will use l2jaCis.

nah, i bet there will be smth like this 40% kiddos using acis to add custom and sell here on the market,

20% servers online will be with lol customs added stupid and lot of errors.

10% ppl starting QQ on forum, cuz they will be to noob to do smth by themself.

and 10% pro servers that will mean something for L2, and from this maybe 2% will donate smth for tryskell work.

and rest of 10% IL servers will still use crappy shits.

Posted

Hiho all, I see my topic is spammed so :D.

 

To answer to Intrepid, as he seems to know all on all, currently my server is the lightest on ram use at begin from current & old free IL projects (didn't test privates, so I don't talk about). Well that doesn't mean many things, still 50mo ram is 50mo (depending on pack, difference can go to 100mo).

 

About the guy doing his own pc specs thread in my own topic :P. Your computer is pretty old, and as intrepid said, result will be low, whatever chronicle or pack used (whatever says Intrepid, I don't think L2Emu can handle 100 ppls with such hardware). I'm more optimistic than Intrepid, I would say until 40 players could play, but quality of play can be hurt. You should add at least 1 giga ram, imho.

 

There is no servers using aCis atm, and it's better like that. Pack stopped to got live statut from the moment I begun skills refactors. The live statut will be available around the end of skills refactor, and the correction of 1 critical issue. You won't have any problem to launch pvp type servers.

 

For your own information, skills aren't only players skills. They're NPC skills, augments, items effects, SAs... Some skills even use others skills (signets, active augments). If we talk about players' skills, they're done. Others are under refactoring.

 

Intrepid, "keep your poison in your mouth", I already collected your card. http://lotrtcgdb.com/images/LOTR04154.jpg

 

Once more, don't post saying negative things for nothing. I guess you didn't even read timeline or checkout project.

Posted

Hiho all, I see my topic is spammed so :D.

 

To answer to Intrepid, as he seems to know all on all, currently my server is the lightest on ram use at begin from current & old free IL projects (didn't test privates, so I don't talk about). Well that doesn't mean many things, still 50mo ram is 50mo (depending on pack, difference can go to 100mo).

 

About the guy doing his own pc specs thread in my own topic :P. Your computer is pretty old, and as intrepid said, result will be low, whatever chronicle or pack used (whatever says Intrepid, I don't think L2Emu can handle 100 ppls with such hardware). I'm more optimistic than Intrepid, I would say until 40 players could play, but quality of play can be hurt. You should add at least 1 giga ram, imho.

 

There is no servers using aCis atm, and it's better like that. Pack stopped to got live statut from the moment I begun skills refactors. The live statut will be available around the end of skills refactor, and the correction of 1 critical issue. You won't have any problem to launch pvp type servers.

 

For your own information, skills aren't only players skills. They're NPC skills, augments, items effects, SAs... Some skills even use others skills (signets, active augments). If we talk about players' skills, they're done. Others are under refactoring.

 

Intrepid, "keep your poison in your mouth", I already collected your card. http://lotrtcgdb.com/images/LOTR04154.jpg

 

Once more, don't post saying negative things for nothing.

 

What i tried to point out is until theres no server running with your pack you cant really have result :)

 

PS.: the memory footprint can be lowered easily but dont be so high about the footprint key is runtime(thats why i said the servers) :)

Posted

To got some followers, it has to work. And to work, it needs followers :).

 

I agree with you on this point : people won't bother with project until it isn't live-able. This is the bad part, as I need feedbacks now, and not after all is done and working well.

 

Just think more about your words. Words can hit harder than swords.

 

The memory footprint is a fast appreciation, and as I said higher, "it doesn't mean many things".

Posted

You have to stop to move in order to see others ppls and npcs.

 

It came when I refactored L2Character positioning, and it's not a report from anyone, I commited it knowing the issue (I prefer to say instead of hear "failed pack").

 

From the moment you have the control of what you are doing, there is no real problems. The real problem would be to discover a bug and you have no idea where to search in the code in order to correct it (like packets issues, which are pretty hard to handle because of the lack of infos and possibilities of debug). This is definitively not the case.

 

I didn't bother until now, but it will have to be corrected before or around skills refactor end.

 

By the way, Rev 65 is out.

Posted

This thread should be sticked. :]

Not really

Only good for IL, a so old chronicle, i don't think one of the most important L2 forums support so old chronicle projects 6_6!

Posted

Not really

Only good for IL, a so old chronicle, i don't think one of the most important L2 forums support so old chronicle projects 6_6!

Yeah.. So old.. Just google for interlude servers, and look, how many players are playing at interlude servers. Imo at about ~30%, so think what ur talking about, mate.

Posted

Yeah.. So old.. Just google for interlude servers, and look, how many players are playing at interlude servers. Imo at about ~30%, so think what ur talking about, mate.

 

that 30% in reality is like 0,30%...you see rpg-club holds more player than the whole il community.

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

    • 🏆 UPDATE: CLAN RACE — R$ 300 (PIX in Brazil, or the equivalent in USDT/PayPal) for the first clan ready for World B PvP Worlds opens on Friday, September 25, 19:00 BRT (GMT-3). Everyone starts together, from scratch. The challenge: the first clan with 9 members ready to enter World B wins. Ready = level 51, World C registered and the full C set equipped (weapon, armor and jewelry) with at least 3 attributes on each piece. Only Queen Ant stands between you and World B. Rules: main character only; 9 different people, each on their own PC; the server records the exact time each member became ready. Deadline: October 14. Sign up your clan on our Discord (link on the site): l2mog.com/pvp
    • 🚀 L2-Gold Custom PvP – Beta Test is LIVE! 🚀 Hey guys! We are opening a brand new Custom PvP server and looking for passionate players to help us test it out before the official grand opening! 💥 What we offer: High Rates & Custom PvP Gameplay Custom NPC Buffer, GM Shop & Global GK Balanced classes and epic custom items Interlude with c4 skills 🎁 Beta Rewards: Every active tester who reports bugs or gives feedback will receive Exclusive Custom Rewards on the official launch day! 🛑 No website needed yet! All files, patch, and support are inside our Discord. 🔗 Join Beta Test Here: [https://discord.gg/9qkSxQtTq]
    • "CAN YOU DO A BULGARIAN REVOLUT?" – WE DID. FIRST DRAFT, NO EDITS The request came in short: a photo of a bank card, Bulgaria, Revolut. We said yes and asked the only question that matters – what data. The client was on the road, asked for a couple of hours, then sent the lot: number, expiry, CVV, payment system, bank, cardholder name. Then came the part the client never sees: - ran the number through Luhn – the check digit has to add up, otherwise the card is dead the second anything automated looks at it - matched the BIN to the issuer: Revolut in Bulgaria isn't a "local bank", the cards run through Revolut Bank UAB. The number range has to actually belong there, not just start with the right digit - built the current design, not a five-year-old picture: vertical layout, flat laser print instead of embossing, correct chip module, contactless mark where it belongs - the payment system logo – with the right gradient where the circles overlap and the wordmark sitting exactly where it should. A small thing that kills half the fakes out there - and finally, physics. Plastic has to catch light: a highlight along the edge, a micro-shadow under the chip, a faint fingerprint. A phone shot, not a render Sent the draft for approval. The client looked it over, signed off with zero corrections – final files went out. One pass, no rework. A card is a deceptively simple document. Looks like a rectangle and sixteen digits. In reality it's maths in the number, a tie to the issuer, a current design and light on plastic. Miss any one of the four and the file gets exactly two seconds of attention. Need a card for a specific bank and country? Message us. We'll tell you straight what's realistic for your case – then build it. { all data published with the client's consent} › TG: @mustang_service_ms ( https:// t.me/ mustang_service_ms ) › Channel: Mustang Service ( https:// t.me/ +JPpJCETg-xM1NjNl ) #drawing #card #photoshop #revolut #case
    • ============================================================               CLExt Classic Interlude: v7.80 ============================================================   01. Fixed ValidateLocation handling and player/client position synchronization. 02. Added protection against invalid coordinates and characters falling under the map. 03. Improved XY/Z position and heading validation. 04. Fixed MoveToLocation and MoveToPawn packet conversion and target validation. 05. Fixed TargetSelected, TargetUnselected and MyTargetSelected packet handling. 06. Improved GeoData Z-location handling and disabled unsafe PathNode modifications. 07. Added ExUserInfoInventoryWeight support. 08. Fixed inventory weight and maximum load synchronization. 09. Fixed incorrect 0% inventory weight after character login. 10. Added automatic inventory weight updates after EnterWorld and inventory changes. 11. Added inventory weight packet spam protection and safe weight caching. 12. Fixed BuyList and SellList inventory, slot and weight synchronization. 13. Improved NPC target and Buy/Sell packet validation. 14. Reworked mail attachment inventory and weight validation. 15. Added all-or-nothing mail attachment receiving and safe retry handling. 16. Fixed stackable mail attachment validation and INT_MAX overflow protection. 17. Improved COD Adena validation and post-mail inventory weight refresh. 18. Improved Warehouse Deposit and Withdraw validation. 19. Added protection against malformed warehouse item counts, DBIDs and amounts. 20. Added warehouse INT_MAX, CItem and pSID validation. 21. Improved warehouse anti-dupe protection. 22. Reworked the HTML Cache system for improved stability and memory usage. 23. Added lazy HTML loading instead of loading ~20,000 files during startup. 24. Fixed HTML Cache startup crashes with large HTML collections. 25. Added thread-safe HTML Cache access and Clear/Reload support. 26. Added bad allocation, invalid HTML and oversized HTML protection. 27. Reduced HTML Cache RAM usage, startup allocations and disk I/O. 28. Added HTML Caching ON/OFF with live HTM loading support. 29. Fixed ToggleCachingHook and added VS2005-compatible live HTML handling. 30. Fixed ShortcutInit processing and skill synchronization order. 31. Improved shortcut item validation, augmentation handling and va_list safety. 32. Added LiveMode Ability Point system. 33. Added inventory-item-based Ability Points with configurable pointItemId. 34. Preserved the original level-based Ability Point system as fallback. 35. Fixed incorrect Ability Point display and inventory synchronization. 36. Improved Ability skill learning and point validation. 37. Improved OfflineShopRestore loading and FakePC/DBID handling. 38. Added safer OfflineShopRestore socket limits and batch processing. 39. Prevented thousands of restore sockets from loading simultaneously. 40. Added delayed, non-blocking OfflineShopRestore after server startup. 41. Improved OnEnterWorld initialization order and stability. 42. Improved inventory weight, SkillList and acquired-skill initialization after login. 43. Added VIP integration to the EnterWorld process. 44. Added safe UserExtData initialization without modifying the native User structure. 45. Improved duplicate Bronch Jewel and equipped-slot protection. 46. Improved Bracelet, Belt, Bronch and general UseItem validation. 47. Improved general packet, UserSocket, User, pSD and Creature validation. 48. Added safer INT32/INT64 packet handling and malformed-packet protection. 49. Improved L2Server startup memory usage and lazy resource loading. 50. Reduced unnecessary startup allocations. 51. Improved account-only KeyEngine authentication and remote account validation. 52. Removed account expiration-time requirements. 53. Added updater/restart design without requiring CLExtUpdate.exe. 54. Improved CLIEXT HWID, shared-memory and client/server version validation. 55. Improved ReadFile/WriteFile hooks and MemoryProtector handling. 56. Added UoPilot and Extreme Injector detection handling. 57. Reworked VIP point loading, saving and database synchronization. 58. Fixed VIP Level 0 initialization and first VIP activation. 59. Fixed vip.htm activation after login and from party-shared points. 60. Fixed VIP points being incorrectly reset before successful activation. 61. Improved VIP progression from Level 1 through Level 7. 62. Added proper VIP Level 7 MAX/DONE behavior with no Level 8 requirement. 63. Disabled further VIP point collection after reaching maximum level. 64. Reworked VIP BonusInfo/ReceiveVipInfo packet synchronization. 65. Fixed VIP tier, points, duration and level requirement packet fields. 66. Added VIP duration, tier, point and User validation protections. 67. Added safer 64-bit VIP EXP and party EXP calculations. 68. Preserved subclass maximum EXP protection. 69. Improved ItemDataEx validation during character loading. 70. Fixed augmentation loss during login, relog and server restart. 71. Added safe restoration of augmentation IDs directly from the database. 72. Added CItem, pSID, pExItem and User validation during ItemDataEx loading. 73. Improved Shadow Item mana and item lifetime loading. 74. Preserved item protection timeout data during character loading. 75. Added augmentation loading diagnostics and protected valid augmentation data. 76. Preserved database value 0 for genuinely non-augmented items. 77. Added RaidBoss Status synchronization with the World Map. 78. Fixed alive/dead RaidBoss status updates after spawn and death. 79. Added RaidBossStatus as the source of truth for RaidBoss map packets. 80. Fixed RaidBoss map status synchronization after server/database loading.
  • 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..