Weapon SA issues
Posted: Sat Aug 22, 2009 6:18 pm
datapack version 4995
Here is my problem:
I am dev on a very small server. My current project is fixing missing weapon sa's for a major update. During my work I noticed that ALOT of weapons, mostly dual swords, that have worked for the longest time now don't work. What I have gathered thru searches is L2J is going to a different SA structure (combining same sa with different levels into one skill). Why in the world would someone remove sa's from weapons without making the updated skill work first?? Having to download OLD datapacks to fix old weapons seems a bit counterintuitive. What is going on?? This is making a simple 2 hour project take days of research to find all the busted SA's.
Here is a good example:
Raid sword*raid sword old code: (from hellbound datapack)
<item id='2599' name="raid_sword*raid_sword">
<for>
<set val='190' order='0x08' stat='pAtk'/>
<set val='83' order='0x08' stat='mAtk'/>
<set val='8' order='0x08' stat='rCrit'/>
<add val='0' order='0x10' stat='accCombat'/>
<set val='325' order='0x08' stat='pAtkSpd'/>
<mul val='1.04' order='0x30' stat='pAtkSpd'>
<and>
<using slotitem="2599;16;4"/>
</and>
</mul>
<enchant val='0' order='0x0C' stat='pAtk'/>
<enchant val='0' order='0x0C' stat='mAtk'/>
</for>
</item>
This datapacks code:
<item id="2599" name="Raid Sword*Raid Sword">
<for>
<set val="190" order="0x08" stat="pAtk"/>
<set val="83" order="0x08" stat="mAtk"/>
<set val="8" order="0x08" stat="rCrit"/>
<add val="0" order="0x10" stat="accCombat"/>
<set val="325" order="0x08" stat="pAtkSpd"/>
<enchant val="0" order="0x0C" stat="pAtk"/>
<enchant val="0" order="0x0C" stat="mAtk"/>
</for>
</item>
Sql database shows no skill linked to this item...is there some miscommunication occuring between people?
Here is my problem:
I am dev on a very small server. My current project is fixing missing weapon sa's for a major update. During my work I noticed that ALOT of weapons, mostly dual swords, that have worked for the longest time now don't work. What I have gathered thru searches is L2J is going to a different SA structure (combining same sa with different levels into one skill). Why in the world would someone remove sa's from weapons without making the updated skill work first?? Having to download OLD datapacks to fix old weapons seems a bit counterintuitive. What is going on?? This is making a simple 2 hour project take days of research to find all the busted SA's.
Here is a good example:
Raid sword*raid sword old code: (from hellbound datapack)
<item id='2599' name="raid_sword*raid_sword">
<for>
<set val='190' order='0x08' stat='pAtk'/>
<set val='83' order='0x08' stat='mAtk'/>
<set val='8' order='0x08' stat='rCrit'/>
<add val='0' order='0x10' stat='accCombat'/>
<set val='325' order='0x08' stat='pAtkSpd'/>
<mul val='1.04' order='0x30' stat='pAtkSpd'>
<and>
<using slotitem="2599;16;4"/>
</and>
</mul>
<enchant val='0' order='0x0C' stat='pAtk'/>
<enchant val='0' order='0x0C' stat='mAtk'/>
</for>
</item>
This datapacks code:
<item id="2599" name="Raid Sword*Raid Sword">
<for>
<set val="190" order="0x08" stat="pAtk"/>
<set val="83" order="0x08" stat="mAtk"/>
<set val="8" order="0x08" stat="rCrit"/>
<add val="0" order="0x10" stat="accCombat"/>
<set val="325" order="0x08" stat="pAtkSpd"/>
<enchant val="0" order="0x0C" stat="pAtk"/>
<enchant val="0" order="0x0C" stat="mAtk"/>
</for>
</item>
Sql database shows no skill linked to this item...is there some miscommunication occuring between people?