Tryskell

aCis freemium concept evolved around June 2021 - the money fee is bigger than before (100€ initial fee + 10€/month), but you got access to the Git now and you can get access freely if you contribute enough. Getting 120+ ghosts users was annoying to maintain. No more diff patch share aswell for me. It is a success so far. I should have raised the price way before - people only bows in front of money and indeed, they don't respect free or (almost free) shared content. Not sure if you ever read L2JBrazil content regarding myself - they say I force renames to sell more revisions (which was 1€/revision, one revision being like 15 days minimum of work). Funny community.

L2Reborn used aCis in the beginning (Jan to March 2020) but switched to Lucera. The administrator (which is named p0w3rf1y on my forums, his name is on few changesets) helped for a good time, then simply cut the access to his project without telling me a word. Lucera is a fork of the main L2 RU fork than any RU fork is using (Overlord, L2Scripts, etc). They only downgraded the chronicle. None of the core work is actually done by them, they simply inherit from main RU fork (DefaultAI, geoengine, etc).

I can't wait to see your solo coded L2J IL fork, based on L2J IL latest branch (not based on any dissapointing forks), reviewed by none except yourself, coded in less than 10y. If you provide me evidences you can do equal result (datapack, formula, AI, scripts,...), without any copy-paste from another sources, I'm willing to deliver you my Paypal account.

Themed events (Halloween, Christmas,...) can actually be automatized (using a ScheduledScript on aCis, no clue about other forks). TvT and alike events should be, imo, manually triggered by the server team (ingame reward, ingame announcements... generally generate some warm moments).

It's probably only few lines to add.

aCis' DNA is to provide a free-custom / vanilla experience - people adds their customs to make THEIR servers. So your remarks are perfectly understable, but that's actually accurate compared to my own vision - one vanilla experience, and a ecosystem of people trading/sharing their customs between them. We got far lesser configurations than L2J server itself, by default. Admincommands were refactored to be cut by half (100 admincommands overall). Saying the pack is "basic", well, can be misread - the pack is far to be basic - all main methods were refactored/enhanced, and methods/systems which I judged needed were added (PlayerMemo, for exemple). If you mean it doesn't offer a lot of configurations, well... This is the intention since day 1.

I can confirm that backdoor exists since few months on this pack, since someone shared a server using that source with me around February (I just verified it today to see if it was existing). Potentially all servers using that pack are endangered. I can't confirm if Devlin is the actual author, or if the sources were corrupted by someone else and distributed like that. Except if the topic owner manipulated the database, Devlin seems guilty. @Sh4xMx should provide links about actual payment to Devlin, to certify he used Devlin pack and not a shady share. If the payment is verified, then it means than the source is, by default, corrupted with a backdoor and Devlin is guilty. Backdoors got nothing to do in sources. You simply make you untrusted using that. If you don't believe in your customers, then restrain the sell or don't sell at all. Also such code is extremely easy to spot on. In any case, if you don't want that sort of surprise, you should use the original material ;).

If you use 382 yes, but KejbL uses 399 and TargetHandler were reworked.

<set name="target" val="TARGET_SELF" /> > <set name="target" val="SELF" /> Other than that, no reason it doesn't work. There is probably a core edit to do for the raise of the skill itself, I don't see how it would process different level than 1.

If your point is than a pack is achieved because it got all scripts, I can simply spawn a Frintezza, call it Frintezza.java and you would be happy with that, I suppose. That's not my way of working - never was and never will be. L2JFrozen actually thought like you - hotfixing stuff rather than making clean version of it. We got a clear different point of view about this, so... Do your stuff, I continue to do mine - which will be far superior in the end (until you decide to copy-paste it, fixing one thing and claiming your version is better than mine). To do what you do, you need people like me, to begin with. We can't all be damn bloodysuckers, hotfixing stuff and waiting for someone more competent/skilled to fix it for you.

Movement got nothing to do with L2OFF, globally speaking, and that particular issue is simply due to FloodProtector StopMove. I just tested on AdvExt that behavior, and it's worst than aCis once related FP is set to 0. https://streamable.com/0sm3u3 -> AdvExt PTS Maybe got an actual clue of what is L2OFF, before saying it's far from L2OFF.

I don't think I got some lessons to pick from someone who ninja other ppl work. Ofc you got things since 2014, you can thank some people for that :). From what I know, my scripts and my geodata was also used for a good time - and that time you didn't spend, I spent it for you, basically. I could fork L2JMobius and get "spawn zones since 2014" aswell. Pick your Frintezza, for exemple. Put some fixes upon it, and tell your version was shitty and mine is better. That's basically what you achieved, so far. I'm not that sort of people, but good for you if you are, and if people follow.

If you can't understand what is SpawnManager and what it actually offers as possibilities, be sure then adding any random Frintezza found on the internet will fit your needs.

I know my profits are neglictable, and that's why I'm restrictive about aCis usages / terms of agreement. That project was never meant to make money, so the minimum is to respect my rules. People don't understand multiple thousands of hours were spent - almost freely. That's also why I raised prices, since people only respect money and not the hard work. @Kara you can test PTS and figure out by yourself.

If we speak about Interlude, my pack is still actively updated - we introduced few weeks ago new SpawnManager, few days ago we released complete drop/spoil rates edit based on L2OFF rates and manor domains (seeds territory zones). Hasha actually focus about implementing properly the AI system (would take few months), I personnally introduce numerous new event types (PARTY_KILLED, PARTY_ATTACKED, SEE_ITEM, NO_DESIRE, etc), and eventually the Desire system (under thoughts). aCis got its own PTS named Blackbird since few weeks to test latest revision, anyone can logon and test it. There are tutorials on aCis forums about installation, and people shared a lot of customs adapted to aCis. For all infos, join the Discord / forums and read the content. 542 people donated between july 2012 and june 2021, 16 ppl donated since new system introduction. If you speak about other chronicles, well, you got L2J for H5.

It's already fixed on rev 401. As stated in the changeset, it's linked to follow state behavior.

If you provide and restrict some areas, notably Marketplace, to "not that much" randomers, then there is no benefits to generate a new forum account. Marketplace should be accessible to ppl with positive contribution, to begin with.

I would prefer to get the ban history of a people, on a visible scale (directly under his name) and no matter if he is unbanned one day. It should stay visible. That would give some hints about that people "general" behavior.

That's the main point of a wiki, but not a forum. If anyone can edit anything, without any type of history or rollback, be sure some clowns will abuse of their powers. I agree moderators close topics way too fast, and either should select themselves the best answer, or let the topic author to pin the good solution. About the pin solution, you can reward the topic author himself to use that feature (with a badge, point reputation, etc). The "good solution" provider would earn even more contribution points. Those contribution points can then be "traded" for services, goods, ads. Maybe @Maxtor crypto would have a use ? ;)

It is basically done introducing an "int" into WorldObject class, storing the actual instance. Then in the knownlist system (setRegion + getKnownType methods), you filter objects based on distance (as always), and by that int. There are plenty of shared systems on MxC, for different projects (mine included).

Public repository is actually rev 382, so @ExTrEmEDwarfis right. L2JBrazil = clowns.

Well, calling 6 times (for 2nd and 3rd classes) a method is what I would call messy :). You can eventually put parameter as "ClassId..." to cut the calls. Also, in your exemple canClassIdJoin can be return getMemberCount(classId) < classId.getPartyLimit();

Edit and introduce getClassId() checks here : if (activeChar.getParty() != null) { for (L2PcInstance player : activeChar.getParty().getPartyMembers()) { if (player != null && player.isHealerClass() && !player.isInStance()) { healers++; if (minus != 2 && (player.getPvpFlag() != 0 || player.getKarma() > 0 minus = 2; } } } There are no easy ways to do it, so it gonna be messy if your point is to checks all classes.

You will probably end breaking another part of the geodata simply checking one spot. A geodata file is a huge square, so you better have some visual tool to directly see (and an easy one is the ///geodata client tool). Also, fixing one invisible wall doesn't mean you don't have another issue elsewhere. As said others, geodatas are basically the same (since generation is easily done, and always produce the same result). The only different versions are handmade, and depending about your project's geoengine, they will also be handled differently depending about what people actually did. Understand a "good" geodata on an edited geoengine which use different rules can be simply "terrible". Finally, some invisible walls can be explained by : - you use an invalid geodata for the client version (a simple exemple on IL, around Gludio there are some rocks in some versions, and in another client version there aren't those rocks). So if you use a geodata from one version to another, you can either lack geodata if your client got rocks but your geodata was made on old client revision, or you can have invisible walls if your client doesn't have rocks but your geodata was built on a higher client version. You should check with a visual tool exactly what happens, because an ivnisible wall with the shape of a rock would mean your geodata is definitively not made for your current client, and you will have issues elsewhere for sure. - NCSoft itself added walls.

Do you still have some errors ? Sido moved the forums to another host, it's known from past host change than DNS are broken for some days, even after the move itself. Also, we got some banrules with either IP range / entire domains because of spambots. The forums itself isn't shutdown, aswell as the project. You can also join our Discord, to get access to the main infos, or simply chat. Hopefully, the forums design will be edited soon.