1. Open "statusnametable.txt" and "skillnametable.txt" located in the IRO tables folder.
Ex: c:/openkore_ready/tables/iRO
These 2 files have all the EFST skill names, skill spellings, and EFST status names and spellings.
2. Use the EFST style name for the skills and statuses.
The EFST name is always the same regardless of server localization, which makes block coding a lot easier.
Most skill block problems are from an incorrect name or status.If you don't believe me, look at this
skillnametable.txt:
iRO = AL_BLESSING#Blessing#
twRO = AL_BLESSING#天使之賜福#
rRO = AL_BLESSING#Благословение#
kRO = AL_BLESSING#블레싱#
statusnametable.txt:
EFST_BLESSING Blessing
Notice they all have the same EFST name "AL_BLESSING".
3. Check all block commands and options for correct spelling, correct case, and syntax.
All it takes is one tiny mistake to ruin a perfectly functioning block.
Code: Select all
useSelf_skill Impositio Manus { <<< Incorrect spelling, use PR_IMPOSITIO or Impositio_Manus.
lvl 10 <<< lvl 10 on a lvl 5 skill will just cast at max lvl, no effect.
Sp > 45% <<< Incorrect case, use sp in lowercase.
whenStatusInactive EFST_IMPOSITIO <<< Correct spelling, and corresponding skill status.
target_timeout 1 <<< incorrect syntax, "target" options should not be used for self skills.
}4. Check Openkore
Are you using the latest SVN that supports EFST names and not v2.0.7?
Is the status in openkore completely different from the skill?
Perfect example is the sage's Endow Blaze skill, openkore will show Flame Launcher
skillnamestable.txt:
SA_FLAMELAUNCHER#Endow_Blaze#
statusnamestable.txt:
EFST_PROPERTYFIRE Flame Launcher
5. If all of those fail to correct your block, post ONLY the block here.
It really ticks off the forum moderators and patrons alike when you have to scroll through 200 lines to fix 1 letter...
Any Questions?
