Jump to content

Recommended Posts

Posted

I think that tryskell's project(aCis) is better nowadays because his team always updating new contents of their project(thing that i didn't saw nowadays from other projects...) Also They're skilled and they know how to control a project with its source and other usefull modifications... So I prefer aCis Project

Posted

I think that tryskell's project(aCis) is better nowadays because his team always updating new contents of their project(thing that i didn't saw nowadays from other projects...) Also They're skilled and they know how to control a project with its source and other usefull modifications... So I prefer aCis Project

Atm i'm using aCis and i think i 'll continue using it but i want an overview about the other projects too ..

Posted

Atm i'm using aCis and i think i 'll continue using it but i want an overview about the other projects too ..

 

Believe me bud, if i would like to make a server i would pay for aCis Source ofcourse...

Posted

If it was so worthy, you would manage to use it rather than 2011 L2JArchid as base for your own pack.

 

So, probably not so worthy.

 

Any clue about RU developement regarding IL ? They're kinda sneaky.

you are still forgeting that i started developing my project at 2011 and not last year ;) i didn't have that pack in my possession that year

Posted

Sadly, I missed that topic but anyway.

 

The usage of open source projects is wayyy more recommened to create a server. That happends because at open source everyone is able to contribute bug report and test. In the other hand, private projects are usually created by one or two developers, and that's it.

 

All l2j projects are full of bugs, missing a ton of retail stuff, all these are not a one-man job.

 

Futhermore, you can ask freely for help at (open source)s and actually reciece some answer, but in private projects, at most of the times, the so called developers are busy and by the time they already have money in their pockets.

 

If you ask me, DONT even think to buy a project. Except the fact that you will propably get scammed, the possibilites will be wayy less that the possibilities that an open source project can offer you.

Posted

Sadly, I missed that topic but anyway.

 

The usage of open source projects is wayyy more recommened to create a server. That happends because at open source everyone is able to contribute bug report and test. In the other hand, private projects are usually created by one or two developers, and that's it.

 

All l2j projects are full of bugs, missing a ton of retail stuff, all these are not a one-man job.

 

Futhermore, you can ask freely for help at (open source)s and actually reciece some answer, but in private projects, at most of the times, the so called developers are busy and by the time they already have money in their pockets.

 

If you ask me, DONT even think to buy a project. Except the fact that you will propably get scammed, the possibilites will be wayy less that the possibilities that an open source project can offer you.

thanks.

Posted

The only pack which i would ever buy would be official. official files rock.

 

and who is gonna fix it's bugs? you or ur gonna hire an NCsoft developer ?

Posted

The only pack which i would ever buy would be official. official files rock.

 

Hahaha, nice one :D

 

As xdem said..

Posted

If he would be able to purchase such files, he would be also able to hire people being able to handle them properly. Though stupid example.

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 nevermind, i got what you mean, here's the fix   https://drive.google.com/file/d/1av7OHaGSdnVQtcBgb9MhtiIkxVXy3P2y/view?usp=sharing   CanIngnoreCollision=True CanBeIngnoredCollision=True  
    • <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..