Jump to content

Recommended Posts

Posted

I'm pleased to say that Mart officially join the L2dotNET development team.

 

Mart has been helping me from the very beginning cleaning up the old shitcode and adding modern one.

 

He also has some really nice stats.

MartLegion85 commits / 802,538 ++ / 814,922 --

 

To compare, hereis mine.

 

Elfocrash69 commits / 865,680 ++ / 78,761 --

 

So yeah, what else i can say. When i started the project i though no one would give a shit, but it seems that i was wrong.

  • 2 weeks later...
Posted

For those you might not know, i just finished moving to my new house. This was the main reason why the development is a bit slow lately. 

The next update will involve the new packet model they we currently use for the login service to be used for the game-service too.

 

However that a long process, so i will be working on a branch and later once it's tested i will merge it.

 

Thanks

Elfocrash

  • 3 weeks later...
Posted (edited)

Inventory Reworked

Major code refinements. Everything (naming, casting, methods, linq) is using proper C# standards.

The codebase no longer reminds java.

Edited by .Elfocrash
Posted

Added PlayerBag.

 

A session-like player specific dynamic property.

 

By just typing the name of the property you wanna store, it will automatically create the variable no matter the type.

 

Example:

MkWTeeR.png

 

Those are not properties I pre-created. They are made on the fly.

Posted

Just read the whole thread.

 

I'm very surprised by the amount of negative replies and retarded criticism/comparisons made by inexperienced and arrogant users and other butthurt l2 backend emulator owners/contributors.

You can feel the envy through their words, they don't want you to succeed.

 

I've also learnt that the next time i want to start an open source emulator, i shall not make a thread of it.

 

I must congratulate elfo for not minding them and keep his project going.

Good luck mate!

Posted

Just read the whole thread.

 

I'm very surprised by the amount of negative replies and retarded criticism/comparisons made by inexperienced and arrogant users and other butthurt l2 backend emulator owners/contributors.

You can feel the envy through their words, they don't want you to succeed.

 

I've also learnt that the next time i want to start an open source emulator, i shall not make a thread of it.

 

I must congratulate elfo for not minding them and keep his project going.

Good luck mate!

Thanks. I do it in my spare time and i have fun coding it so  I keep on working on it. 

I'm very happy with the progress for a side project. We just finished with major code reworks and now we can easily add functionality.

 

Don't care what people say. Just do your thing.

Posted (edited)

Update time

 

  • Fixed the movement bug
  • Total Game service packets reworked (Everything except the sending ones are using the new struct)
  • Moved most of stuff that don't cause redundant references to the main lib
  • Added DedidatedThreadPool for future use
  • Fixed several NREs

Now we can safely finish the known objects and the zones.

 

 

Don't forget to star and fork the project if you wanna contribute.

Thanks.

Edited by .Elfocrash
Posted

Spicy updates. After brainstorming how to get rid of that stupid switch that handles the incoming packet I ended up with this.

 

From:

9sAyhs7.png

 

To simply:

JFOcIkj.png

 

Nice and clean. Thanks.

Posted

ConcurrentDictionary is similar to ConcurrentHashMap ? Cause atm you simply need a HashMap, as you simply use it to check, and that map is fed normally only once (and content never replaced, removed or edited anew).

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

    • try this one instead. The one he shared affects every single NPC/player character in the game, the one I posted only affects player characters  https://drive.google.com/file/d/1UtccbD9e50x3WEnQBab2PTZnBHwpcGYM/view?usp=sharing or perhaps i misunderstood; if you could please post a full explanation of the problem you're having with the files, unfortunately i think whatever you're using to translate to english is a bit bad
    • <dailyReward days="28" autoOpen="true" minimumOnlineTimeSeconds="30" oneRewardPerIP="true" resetIfMissDay="true">   For now, I have these settings in the XML—this is the V1 version I created, though I plan to make further improvements over time. Of course, I’ll also add more protections—MAC, HWID, and perhaps others like account-based restrictions—to make it more secure. We can also implement non-tradable items to further enhance the system's security. I’ll keep posting updates and refining both the system and the interface. I might make a video tomorrow; if you look at the top, you'll see the "auto-open" feature can be toggled on or off, allowing users to rely solely on the `.daily` command. Cheers! Note: If I sell it in this state, I’ll provide support and roll out updates to users. I’m not forcing anyone to buy anything; I’d even provide the patch files so that anyone with the necessary skills can add features, modify it, or improve it further.
    • If the problem is that the target is lost, the action of aiming at another character, upon losing collision, does not allow aiming.   This one works as it should, allowing you to target characters
    • MICROTEXT AND WATERMARKS BREAK MOST RENDERINGS Microtext and watermarks aren’t just small decorative details. They are one of the most common reasons a document fails verification, even when it looks decent at first glance. The issue is that these elements are almost impossible to reproduce “by eye.” Microtext requires precise geometry and legibility at a very small size, while a watermark needs the correct density, transparency, and accurate placement relative to other security features. Any deviation becomes obvious during detailed inspection. ▪ What’s most often done wrong: - microtext is drawn too thick or blurry - the watermark is made either too visible or almost invisible - the positioning between microtext and watermark is ignored - the original printing technology isn’t taken into account when choosing density and shape - The stronger the document’s security features, the less room there is for approximation. What matters here isn’t visual similarity, but accurate reproduction of the original technical characteristics. If your document contains microtext and watermarks, this is always an area that requires extra attention. Write to us in DMs. We’ll review your case and point out exactly which details need the highest precision during rendering. › TG: @mustang_service_ms ( https:// t.me/ mustang_service_ms ) › Channel: Mustang Service ( https:// t.me/ +JPpJCETg-xM1NjNl ) #drawing #microtext #photoshop #editing #watermarks
  • 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..