PvP, WoE, GvG, & Battleground Releases
Sign in to follow this
Followers
0
Scripts that pertain to PvPing, WoE & GvG, & Battelgrounds.
Example: PvP ladder, PvP room, Party vs Party, WoE Controllers, Capture the Flag
28 topics in this forum
-
- 337 replies
- 89376 views
-
- 20 replies
- 15911 views
-
- 68 replies
- 41033 views
-
- 36 replies
- 15499 views
-
- 1 reply
- 4700 views
-
- 56 replies
- 18849 views
-
- 13 replies
- 7739 views
-
- 6 replies
- 5013 views
-
- 16 replies
- 6668 views
-
- 11 replies
- 4942 views
-
- 2 replies
- 2969 views
-
- 104 replies
- 28620 views
-
- 0 replies
- 2470 views
-
- 8 replies
- 3777 views
-
- 0 replies
- 2122 views
-
- 0 replies
- 1922 views
-
- 0 replies
- 1963 views
-
- 0 replies
- 2004 views
-
- 0 replies
- 2105 views
-
- 0 replies
- 2061 views
-
- 4 replies
- 4676 views
-
- 3 replies
- 3940 views
-
- 1 reply
- 3505 views
-
- 29 replies
- 9712 views
-
- 3 replies
- 3340 views
Sign in to follow this
Followers
0
Announcements
-
Featured Topics
-
-
Latest Commits
-
Topics
-
-
Posts
-
By kikongkalyo · Posted
any update with this plugin please? it is not working with the latest Herc version -
By KredoPW2025 · Posted
Question: Where exactly is this clientinfo, and how/where to edit? -
-
//= METHOD A (fast): copy a known-good IMF //= 1) Open data.grf in GRF Editor → Tools → IMF Editor (or Search “.imf”). //= 2) Find a job that already layers correctly (e.g. Soul Reaper): data\imf\soul_reaper.imf //= 3) Extract that file, then import it back renamed to your target job’s IMF (e.g. novice.imf), //= or change the mapping in: data\luafiles514\lua files\datainfo\imfnametable.lub //= 4) Save GRF → test in-game. //= METHOD B (precise): reorder layers in the IMF Editor //= 1) Tools → IMF Editor → open the target .imf //= 2) Set draw order (top → bottom): //= HeadTop //= HeadMid //= HeadLow //= Body //= Shadow //= 3) Apply to ALL actions/directions → Save → import back → test. //= IMPORTANT: //= • Don’t use RagLite JSON to re-encode .imf (that’s why you saw “compile” errors). //= Let GRF Editor open/save the binary .imf directly. //= • If nothing changes, check you don’t have a loose “data\imf*.imf” overriding the GRF, //= and make sure your custom GRF loads last. //= • If your client uses imfnametable.lub, update the mapping there. //=================================================== //= STEP-BY-STEP (DETAILED) //=================================================== //= A) Prepare //= • Backup data.grf/rdata.grf. //= • Close the game client. //= //= B) Find/Map //= • Path to IMFs: data\imf*.imf (use GRF Editor search). //= • Optional map file: data\luafiles514\lua files\datainfo\imfnametable.lub //= (links job → IMF filename). //= //= C) Fast Copy (no editing) //= • Extract working job’s .imf → import it renamed to target job, OR edit imfnametable.lub to point to it. //= //= D) Manual Fix (if you must keep same filename) //= • Tools → IMF Editor → open target .imf → set layer order: //= HeadTop, HeadMid, HeadLow, Body, Shadow //= • “Apply to all actions/directions” → Save → Import → Save GRF. //=================================================== //=================================================== //= TROUBLESHOOTING //=================================================== //= • Change not showing: //= - Another GRF or a loose “data\imf*.imf” overrides yours. Ensure your custom GRF loads last. //= • Only some animations fixed: //= - You didn’t mass-apply to all actions/directions (walk/attack/cast/idle). Re-apply and save. //= • “Compile” / invalid file when using RagLite: //= - Stop using JSON route. Use GRF Editor’s IMF Editor to open/save binary .imf directly. //= • Still weird on one class: //= - Copy IMF from a class that renders correctly and map it via imfnametable.lub. //=================================================== -
Can try this : - No cards/refine/copying — it purely swaps based on ID, making it safe and clean. - Works only on EQI_HEAD_TOP, but you can easily extend to: EQI_HEAD_MID EQI_HEAD_LOW - Just add your pairs like this: setarray .ItemPair$[0], "3524,3525", // Hokage Helm "3526,3527", // Another custom headgear "3528,3529"; // and so on
-
-
Download Statistics
