Tryskell

Use antifeedmanager, and if you haven't, implement it.

Track uses of damage variable. There's a formula to calculate it, then a formula is applied to calculate critics (x2 damage), than... blablabla.

What's the point, there's like 95% of missing features.

DP side, skills folder, 0800-0899.xml.

Read initial topic, it's explained.

From C4 to IL it's net.sf.l2j, not com.l2jserver Use ctrl+shift+O to correct imports...

switch is more easy to read, and from what I know is faster than a serie of if. Added to that, a clear code == less errors at the end. @one_1, glad my code works.

Report to L2J forum if you use current L2J release. If you use old/nightlie build I invite you to check yourself current L2J release to see if it's corrected. If not, go report to L2J forum.

You only need to edit L2.ini and to share with others. All others system folder files must be from original client, not from another, except if you like the way one server edited his client stuff and you want to ninja it. Locally, you can edit your hosts file aswell, that avoid to touch to your client.

Ugly code : if ((item.getItem().getItemType() == L2ArmorType.HEAVY) && (activeChar.getClassId().getId() == || (activeChar.getClassId().getId() == 9) || (activeChar.getClassId().getId() == 92) || (activeChar.getClassId().getId() == 93) || (activeChar.getClassId().getId() == 23) || (activeChar.getClassId().getId() == 24) || (activeChar.getClassId().getId() == 101 ) || (activeChar.getClassId().getId() == 102 ) || (activeChar.getClassId().getId() == 36) || (activeChar.getClassId().getId() == 37) || (activeChar.getClassId().getId() == 108) || (activeChar.getClassId().getId() == 109)) { activeChar.sendPacket(new SystemMessage(SystemMessageId.CANNOT_EQUIP_ITEM_DUE_TO_BAD_CONDITION)); return; } Not ugly code : if (item.getItem().getItemType() == L2ArmorType.HEAVY) { switch(activeChar.getClassId().getId()) { case 8: case 9: case 92: case 93: case 23: case 24: case 101: case 102: case 36: case 37: case 108: case 109: activeChar.sendPacket(new SystemMessage(SystemMessageId.CANNOT_EQUIP_ITEM_DUE_TO_BAD_CONDITION)); return; } } It means IDs used ARE GOOD ONES. If you failed giving good classes Ids, don't expect it works fine.

Normally, SVNVersion doesn't have any incidence on build. Nor the DP/Core link. Errors on DP are "normal" until you don't link DP && core, about core itself, you didn't show any error about, but as I can see you got errors.

Use java for quests if you use postIL stuff. If you use IL or lower, just open a python quest (datapack/jscript) and see the syntax.

It's not because you create another thread you will have another answer. Read/work on my answer : http://maxcheaters.com/forum/index.php?topic=216847.msg1880491#msg1880491 Here's a full example of implementing a zoneType, in this case, artifact zones to restrict cast : http://trac.assembla.com/acis_project/changeset/115

<offtopic> Three asses better than one, HeRaCleS will be all time right. Until you find a pick with 4 fine asses. </offtopic>

That's the same message on GS logs when you startup your GS, go leech from here :P.

- You said yourself the answer in your picture. cf. "You don't have JDK7 to blablabla". - Added to that, you miss svnversion.exe (can leech from my project or any other project if you don't find it). - Added to that, your DP isn't linked to your core. cf. http://l2jserver.com/forum/viewtopic.php?f=40&t=10726 Since some days, L2J uses JDK7 instead of 1.6, because some used functions come from JDK7.

Just create a zoneType and associate it a zone. Then in onEnter, you must do many checks, such as: - if in party, break party - store old name of player and generate a new one, then broadcastUserInfo. - can't chat in clan/alliance/PM Etc etc, depends of your ask. Basically this is the TownWar system.

Same message over and over :D. Any ETA time of public release (even pre-pre-pre-beta ?). Intrepid spotted :-*. Edit @Vago : they supposed to use solar power when we still use petrol. Let's see if there is enough sun...

Second column is questId, 3rd is condition value, 4th is quest name, 5th is condition name, 6th is condition description, etc etc. You will suffer to find all values (3 are related to radar, one to name of radar points on, etc etc). On java side, the only thing you have to care of is the id of the quest (column 2). That's the only link between client and java. So create a new quest on scripts/, edit scripts.cfg and that's enough.

That's the answer, if you're blind, don't badmouth me. And you could share with others what you did to correct it. Finally, and it's not me who do rules, packs aren't allowed. So /hate more, because you're wrong from A to Z.

Issue related to your db connexion setup. Just give good infos to it. Most probable is about password, as *NeverMore* said.

Don't yeil at me if it's wrong, that's how the 2nd exemple is written.

NPE at the random function, that's kinda special lol. You use L2JFrozen so share with them, here it's pointless, no support for pack except L2J/L2JFree.

Don't expect such things exist. There is no point someone write a "book/e-book" about how work L2J. There will be so much things to write than it is a project itself. No one dares to busy with since 2005, so no one will dare to busy in future. Christmas wishlist : - L2J IL for dummies (learn to correct all mistakes to get a retail server) - make money in 10 minutes for dummies - become president for dummies And so on, the "for dummies" collection can be big.

For example, or even change the average damage. Editing what you linked, you will simply affect on the possibility to make a critic. So if you critic 100% see here, if you want critic is x1,5, it's still here, for average damage BBBBBBBBBIIIIIIIPPPPPPPPPP it's not here ^^.