Tryskell

type can (and was on IL) be a number. That still referencing on the list AzuCeMaZem gave. Numbers goes from 0 to 17 So far, it's the near complete list, if not the whole list.

Personally about the thing you are talking, guys, I just don't bother anymore if I can't answer directly to the topic. If he doesn't give proper informations, topic should be deleted/locked directly, without any warn. If people are too stupid to don't read rules, their problems. I'm fed up to try to understand brainless topics. They show no respect for helpers, so why to show respect for them. Anyway, my quote is a simple answer, that fit with all chronicles. Just try that. Checkout a Freya project, and search for AntiFeedManager with Eclipse search tool.

They must use the same stackType/level in order they bypass each other.

From what I know, it's client hardcoded. You can only use what exist. I got no idea if you can add a new channel, but if you can, it's first on client.

At that time (december), L2JValor added some securities, and I thought it was better to run from that to run from nothing. There is atm nothing coming from L2JValor anymore (even their "social stuff" was ugly coded), so mentioning it's "based on"... As said Ceptimus, I removed all customs. The finality is, I had more work to remove customs and correct their own errors than taking a regular L2J pack and adding their "securities" (on around 140 revs at this time, there was like 10 "good" - mostly 1 line - fixes). But hey, 6 months ago... I got nothing to hide. If I wanted to hide, I wouldn't begin project at rev 1, but at rev 11-12. PS : http://l2topzone.com/forum/greek/%28project%29l2j-valor/ Even from Fixes part, 90% was broken and had to be reworked (MMOCore outdated, and so long). PS2 : glad someone can read properly a timeline :P.

Dude, just forget to develop if you just wait for codes. You missed a serious point. Even MxC forum rules are pretty clear on it. I haven't to give anything, I answered to your question (twice), if you're just so lazy to even do a search, get lost seriously. I take time to answer, and you throw my answer as if it was shit. Lazy ass.

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.