Skip to content
MOMU EMULATOR THE SERVER OWNER’S LIBRARYNeed a hand? Get support ↗
MOMUEMULATOR
简体中文
CONFIGURATION REFERENCE

CustomBuyVip.txt

VIP purchase tiers and costs

4.MuServer/Sub-1/Data/MOMU/CustomBuyVip.txt
Section table6 recorded fieldsutf-8-sigRecorded file structure
Recorded file structure

Verify the active copy and owning role before editing. Recorded structure does not prove feature activation.

APPLICATION / RELOAD/reload spk

Apply on the owning role. Startup-only settings require a restart; spawn/event reloads can reset active state.

Open full tutorial
Recorded column order
Index	Exp+	Drop+	Days	Coin1	Coin2	Coin3	VipName

Field reference

Names and observations come from the supplied files. “Not established” means the unit/range/enum is not verified. Keep a known working value until confirmed.

Section / parameterMeaning and verified limits
mainStable identifier in this table. Keep references unique and consistent; its namespace depends on the file.
mainObserved parameter Days. Its exact unit, accepted range or enum meaning is not established by the schema alone; retain a known working value and validate this module before changing it.
mainWCoinC amount when this system uses the documented WC currency mapping; verify the local enum.
mainWCoinP amount when this system uses the documented WP currency mapping; shown as FC in several MOMU interfaces.
mainGoblin Point amount when this system uses the documented GP mapping.
mainObserved parameter VipName. Its exact unit, accepted range or enum meaning is not established by the schema alone; retain a known working value and validate this module before changing it.

6 fields · 1 / 1

Learn how to apply a change

Built around the supplied MOMU configuration snapshot. Reference entries flag alternate copies and unconfirmed fields. Match the guide to your deployed version; archived packages and live gameplay were not audited by publishing these pages.