Jump to content

Recommended Posts

Posted

If you use regular L2J spawnlist, you can rework it using L2OFF territory system, because everything is plain wrong.

Not my priority, i just need npcs as in l2j.

 

In fact the russians that worked on this pack before me had the l2off territory system for gracia final working but i deleted it.

Posted (edited)

Not my priority, i just need npcs as in l2j.

 

In fact the russians that worked on this pack before me had the l2off territory system for gracia final working but i deleted it.

 

You got the (by default) advantage to "be forced to" recode everything ; I mean, if nothing is your priority (except the 20k players part), you will simply end with L2J.

Edited by Tryskell
Posted

I'll be happy with that. Will you? :)

 

Not sure about which part I should be happy, but no, L2J (notably IL version) isn't an aim for me, since I start from here. Otherwise I would simply use L2JIL :D.

 

And I clearly doubt you will be happy to port L2J AI system and rethink it later on.

Posted

And I clearly doubt you will be happy to port L2J AI system and rethink it later on.

Oh no there is not way im using l2j's AI.

Posted

Unity have territory support if you wanna port it.

 

Free version have some spawn object recycling issue but nothing hard to figure out

Posted

Unity have territory support if you wanna port it.

 

Free version have some spawn object recycling issue but nothing hard to figure out

Oh does it? I actually haven't check your sources guys. Will give it a look, thanks for bringing it up.

Posted

Oh does it? I actually haven't check your sources guys. Will give it a look, thanks for bringing it up.

Shared FandC or Tales files have got it too. It is not much more complicated than l2j server spawn manager, you also need to convert l2off spawnlist to format prefered by you. It would be waste of time to work on that thing twice.

  • 2 months later...
  • 3 months later...
  • 2 months later...
Posted

I created a plan of attack to remove any unimplemented piece of functionality from the project and i started that yesterday.
Also some refactoring took place.

The plan is to remove pretty much everything that i didn't write myself (or the contributors) and re-implement them properly.
What several people told me is that the project might work as a classic project (as there is no other opensource classic project around).
Will tinker with some packet magic over the weekend after the cleanups and see how that goes.

  • 4 months later...
Posted (edited)

Special thanks to JetBrains for providing .NET Rider and Resharper licenses for the development of L2dotNET.

 

I'm currently thinking of migrating the project to Classic.

Edited by .Elfocrash
  • 3 weeks later...
Posted

Special thanks to nihrom for his contributions to the project.

 

Introduced Console commands, Monster Die and he's been refactoring.

(I don't know who you are, so if you see this PM me)

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

    • Anything that is not a kernel level anticheat is totally useless on todays market. You cannot properly prevent botting because, without kernel access, you cannot detect injected DLLs or inspect processes at the level required to stop them. It's good to see people contributing and trying different approaches, but in general, you won't be able to prevent bots from accessing and operating on your server with a usermode anticheat alone. There is a solution that I have not posted or shared with anyone that can fully prevent Adrenaline/Helper from being used on servers. However, I want to give it more time before discussing it publicly so I can see how people attempt to bypass anticheat systems. As I said, kernel level protection is the only thing that can effectively stop Adrenaline usage. When combined with HWID bans, TPM validation, and other hardware based checks, bypassing the protection becomes significantly harder.
    • Improved lucera2 fake appearance (SKINS) system with a more reliable equipment redraw, ensuring skin changes refresh properly in-game without requiring relog or manual armor re-equip. This fixes cases where the client could keep showing the previous armor model after changing appearance    
    • 🚀 IronLock Shield - Closed Beta Testing Hello everyone, We are currently looking for Lineage II Interlude server owners interested in participating in the closed beta phase of IronLock Shield. IronLock Shield is a security platform designed specifically for Interlude servers. Features include: ✓ Secure Launcher Architecture ✓ HWID-Based Licensing ✓ Anti-Debug Protection ✓ DLL Injection Detection ✓ Manual Map Detection ✓ Session Protection ✓ Replay Protection ✓ Runtime Integrity Verification ✓ Secure Update System Selected servers will receive 1 month of free access in exchange for testing and feedback. Website: https://ilshield.com If you are interested, feel free to send me a private message or contact me through Discord. Thank you.
    • GX-EXT Pack – 30% Discount Until Wednesday, June 17 Hello everyone, We are offering a special 30% discount on the GX-EXT Pack until Wednesday, June 17. GX-EXT is a complete extension pack for Lineage II servers, focused on performance, stability, gameplay improvements, custom systems, and server-side/client-side enhancements.
  • 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..