Tryskell

- easy progression kills any gameplay, that's a "not so known" fact. When leveling grinding is kinda boring, it should be enough hard to got a long lifetime (on a very high rate you stay like one month max, on a middle you can stay from 4 months to 1 year, on a low rate you can stay 2 years + depending of server quality). - you should always have something to do, both for pve and pvp boys - that can be events, grinding, etc. If you log ingame and you have nothing to do, you will lose many players after some times. - gameplay must be original, else that's a no point to play on your server. - customs items kill original gameplay, so glowing unbalanced shits => [] - when donators are needed for the server's health, generally donation list is focked up. - original pvp gameplay haven't so much to tweak to be playable. If you give free access to all buffs with 60 hours, lose hope to make any decent balance (I guess you know magical critical rate can reach 30% with 3 buffs). Or you have to tweak each buff one after one... What's the point. - support classes can and should be playable if previous point is respected. If you begin to drop 1/3 of classes, what's the point to PvP.

You should try your luck with the russian team who developped GoD. I don't think many ppl can answer your question (me included), until he tested it himself.

Give far more infos (pack, chronicle, server gameplay, existing website and/or forum, possible community), or I will lock the topic, ty in advance. * /fed_up_of_useless_posts *

You have to implement FourSepulchersManager, and all others related files (needed by or used by manager). There's too data to add, such as XMLs, correct zoning system (L2BossZone), etc.

Such items (extractable, such as pouchs etc) got a special engine in IL packs type, you have to feed extractable_items.csv. On Freya++, and thx to Zoey76 (so far from what I rem), it's now included directly on items XML. The old engine which readed .csv has been heavily modified.

- If your project is connected to the project SVN you simply have to revert changes. - If it's not, well it should (basic rule when you begin to develop : always link your project to a SVN directory to get differences view). - If you found project on Share section from a .rar, just drop it and dl it anew. I'm fedup of non-infos topics so... Gl.

I must agree on that too, as the source code is freely exposed, ppl who code can find means to break it.

Drop the AI file and the line on scripts.cfg, and they won't attack at sight if you wear a weapon.

That sort of stuff is reworked since 5-6 months on my pack. You don't use aCis, or you use a revision you shouldn't use (always use latest). Valakas got 5 pages of drops, and it is working (just tested). You probably use an IL pack for sure, but not mine.

All is clearly explained, Pack User system aswell : I got intention to create/feed it, but currently it's not the time to use it. I just announce the system. I copy paste the announcement post... If you read it entirely without jumping lines, there's nothing special, hidden or mis-explained... Currently I use that membergroup as a 'first step' for ppl who begun to contribute. They got access to private sections (customs sections, Questions, etc), but not on developement topics yet.

Currently the only protections are the ones L2J Freya implemented. There's nothing special, and so far there isn't any rework of protections on current L2J systems.

That. But you got possibilities : join existing packs (Frozen and aCis for the most known), or make your own changes to fix them all. And so far, a good protection means client edition.

No one answered to you, and answer is : you can't. A precompiled version of the pack is made for guests to find and report issues you could find. Giving the quality of reports and your implication on the project, I deliver access to SVN/Timeline (inner circle / pack user). When you get access to svn you can checkout sources and make your own changes on it, make your server as you want, etc. I must add aCis forum is the first barrier. I don't reply anymore to PM about "how to get access...". If ppl can't read announcement section (5 posts on it), well, I can nothing for them. Those days I play a lot on official servers, so I'm kinda off of L2J and of aCis (ppl who made shares aren't commited and then aren't put in Inner Circle). So sorry if I got "low latency" on posts. About the pack review, people says it is good because I think quality > quantity, and that has never changed since the beginning of the project. I verify what I commit, I search infos, and I got enough imagination to code anything I need (and so, I'm not a slave of others's codes). Best exemple is my Baium rework and Dr Chaos. Ofc when a full code is working, I will apply it directly... No point to reinvent the wheel.

You just have to copy paste any template you like from npc.sql, then edit it (name, title, stats). Then you add an AI as you said (else the mob can't move). A //spawn id_of_mob (avoid to target something), and you're good.

If you got sources, repost it on original thread or if such topic doesn't exist anymore, reshare it for all in share section in a new thread with a description of the mod. Pointless to send a PM to each ppl asking. That's a sharing community.

Any screenshot about error, complete info ? That's kinda useless to say you got an error, honestly. We guess already you got an error because of the topic's title. Regards.

Downgrading isn't the easiest (imho), you have to remove all kamalol stuff (many things are hardcoded), aswell as changing 90% of all pckets opcodes (and many packets got their composition changed). Theres around 400 packets, and one wrong packet structure can lead to a disaster... Giving the fact *CURRENT* L2J is still not complete (still miss some SCHs, C2 feature), and infos about L2J about stats etc are often wrong (L2J decided to write values of NPCs directly modified by passive skills instead of make it normal than affected by skills), a downgrade is pointless. The fact is, I don't know any downgraded Freya pack, nor even a project trying to make it (both in past or present). I'm perhaps and surely wrong about the existence, still it's not a popular thought. Personally I thought about it 10 mins, then didn't even tried it :P.

Wrong client. Use a Freya client if you use a Freya emulator.

Well error is kinda easy to read. You use a SoE, it tries to find a restart point but doesn't find. Why ? getRestartPoint() @ line 291 tries to search for that point but find nothing. That "nothing" should be something, so feed the info correctly and that will work :P. Btw your /loc is normal and it isn't even related to your screenshot.

There's no perfect pack for sure. Both projects got issues. If you follow my project since the beginning, I always acted the same : I destroy a thing then rebuild it from 0 (or near). It happened with skills engine (for like 3 months), zones (kinda fast), items (2 weeks only ty to DiNoR work), and then DP scripts folder (500+ scripts to rework/remake/test, currently 120~ are made and around 30 need to be checked/commited). Pets were unusable 5 revs ago (where we almost fixed all issues about items, stats, inventories and behaviors) and now are near fully fixed (ty to xblx for his time). aCis is a a community project made for ppl who wants to invest themselves in a pack. I agree the new formula "forces" ppl to contribute, and can give the pack a "private" face. But it's definitively not. Around 12 ppls got access to the pack, it's only up to you to join the community. About the legendary speach about "aCis is made for low/mid and Frozen for high", that's pure bullshit. You're only limited by your imagination and developement skills. The main difference between aCis and Frozen : aCis is intented to be a "blank" pack, which try to simulate a retail behavior (and then let you free to mod it whatever you want), when Frozen is more a toolbox where you can on/off features. Both systems got boni and mali and both systems got different POPULATION. - Frozen has to correct its customs, I have to search retail infos (and gl to find IL infos from 2007). - Shyla is busy with Scoria, when I'm busy with L2J. - Shyla tries to fix, when I try to "refactor" (replace old code by new one) - Forums users are too very different. I personally try to stay in the L2J tradition. A pack must be as neutral as possible. About an eventual merge between aCis and Frozen, you can read that long post (need to be registered). The answer is definitively NO. And if I'm kinda slow at those moments about commits, it's all about L2 which decided to be f2P. So blame NCSoft to make me play to GoD (BH lvl 74 at this time).

So, here we are. One year is gone since the first public release. Many things have be created, corrected, fixed, tested & searched. What begun by a simple individual one-man project became soon an international project followed by thousands of people. In the little world of L2J, between sharks selling crappy shits and free packs whom heart stopped to beat, aCis bornt from the void. The void, not really. From the latest decent emulator for IL, by the creators of the initial project. From that fully bugged piece of trashing shit latest revision, interrupted in the beginning of 2007, many things have been made : 220 revisions of aCis have been released, each one fixing multiples issues, improving the pack in one or another way. The main trend was (and still is) simple : giving you the power to make anything you want from a vanilla pack. You're right, a blank pack, allowing faction system, events engine, or any other gameplay you will decide. No one have to decide what you want for your server, except... You. Those revisions couldn't be possible without you. Testing, reporting issues and grabbing infos... So many things to do in order to make the pack complete. That work can't be made by one man, and that's the reason I decided to change the system, in order to wake up sleeping people who thought they had to wait in order to get a good pack. All that in the hope to bring aCis another life, in order people got access, one day, to a powerful and reliable pack. So Crappy X-mas to all, and long life to aCis : "the show must go on... And cookies have to be cooked". Tryskell. FAQ about aCis "contribute2use" model : http://acis.i-live.eu/index.php?topic=1093.0 Last revisions : http://acis.i-live.eu/index.php?topic=30.0

Just overload the task giving money to castle warehouse... Or at least, take exemple of.

Many PHP scripts uses that value (biggest time online...), so it's automatically updated, and that since IL. There's just no getters for java uses.

Retard answer, but I guess you wanted to be flamed :P. Judging by your answer, you simply have no clue how the current system of aCis is working. Take some time to learn to read (stop vodka* && go to school ?), and perhaps come back later. Haters gonna hate... @An4rchy, the system will be used as long as the pack needs it. It's not (and never) intented to be private. Next step will be to open pack to ppl who want to open a server with it (special membergroup named "Pack User", with SVN/Timeline access). I want to control the flow of servers using aCis, in order those servers contribute too to make aCis a better software. Which means admins of those servers share bugs reports of their own forums. So to resume, a "light" version of L2DC system (I don't ask to ppl to be java devs or whatever), and anyone is welcomed (from the moment he helps aCis and his intentions don't go versus aCis). * You're right, that's crap, as you just said some too

I dunno since when you stopped L2J dev, but since around 2 or 3 years, a java engine has been implemented for scripts. That's one of the reason on aCis (Interlude pack by the way, as Frozen) I decided to port all python scripts to java scripts (all quests, Ais, etc can be ported from python to java). And yes, it's on -beep-ing scripts folder. You can have java on scripts. Time to checkout latest versions ? :P. PS : "scripts" folder was named "jscript" before. It means it has been reworked, because from the time of "jscript" only python was possible. That time is gone, since 2-3 years (perhaps even more).