Skins, name colors and appearance-related switches
Appearance data can change a visual selection, a purchase or gameplay bonuses depending on the system. Keep client registrations aligned with server IDs.
The outcome to aim for
Appearance data can change a visual selection, a purchase or gameplay bonuses depending on the system. Keep client registrations aligned with server IDs.
Before you start
Read the complete procedure and its version notes. Record the affected server role and keep an untouched backup outside scanned data folders.
Files you need
One step at a time
- STEP 1
Common.ini SkinSystemSwitch enables the skin system, SkinShopSwitch controls its shop and SkinAdvancedEffectsSwitch controls advanced effects. SkinShopResetHourUTC explicitly uses UTC.
- STEP 2
SkinSystem.xml stores Skin Id, Name, Price, Currency, EffectMask and Shop fields. Keep Id stable when updating prices so existing ownership is not reassigned unintentionally.
- STEP 3
CustomNameColor.ini Enable controls name coloring. The supplied notes recommend selecting one ReqCoin type and leaving other costs at zero; test the actual deduction.
- STEP 4
Use the verified reload path or a maintenance restart, then test purchase, owned selection, insufficient funds, effects off and relog. Missing client artwork must be supplied separately.
Progress is saved only in this browser. Completion is your learning record, not proof of a live server change.
Apply the real change
Use the load method stated in the steps for this system. Startup-only settings require a planned restart. The reload finder below shows recorded groups; confirm whether the particular field is startup-only.
Find the file’s reload instructions →Verify the result in game
If the expected result is missing, restore the backed-up files and repeat the same reload/restart before adding another change.