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

ForceIT.ini

ForceIT seasons, matchmaking, scoring and rewards

4.MuServer/Sub-1/Data/Custom/ForceIT.ini
INI156 recorded fieldsutf-8-sigCustom compatibility path
Custom compatibility path

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

APPLICATION / RELOAD/reload forceit

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

Open full tutorial

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
ForceITActivation flag where this file uses 0/1: 0 off, 1 on. Nested switches affect only that entry.
ForceITForceIT score required to win; documented range 1..10 and 1 means first kill wins.
SeasonStable identifier in this table. Keep references unique and consistent; its namespace depends on the file.
SeasonDisplay text. Preserve format placeholders such as %s and %d; translate text without renaming technical attributes.
SeasonObserved parameter EndDate. 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.
RatingObserved parameter InitialRating. 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.
RatingObserved parameter WinPoints. 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.
RatingObserved parameter LosePoints. 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.
MatchmakingObserved parameter StartRatingGap. 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.
MatchmakingObserved parameter RatingGapStep. 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.
MatchmakingTime parameter named in seconds. Preserve any documented minimum/maximum and check the affected operation.
MatchmakingObserved parameter MaxRatingGap. 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.
MatchmakingObserved parameter MaxConcurrentMatches. 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.
MatchmakingTime parameter named in seconds. Preserve any documented minimum/maximum and check the affected operation.
Top1Reward1Activation flag where this file uses 0/1: 0 off, 1 on. Nested switches affect only that entry.
Top1Reward1Item category when used as an item coordinate. Packed ID = category×512+index; some tables use Group for a different grouping.
Top1Reward1Item number or packed item identifier according to this row. Verify whether a separate category column exists.
Top1Reward1Item/character/requirement level according to the owning entry. Use the context and valid definition range.
Top1Reward1Quantity/amount or number of reward definitions according to the owning entry. Keep linked counts consistent.
Top1Reward2Activation flag where this file uses 0/1: 0 off, 1 on. Nested switches affect only that entry.
Top1Reward2Item category when used as an item coordinate. Packed ID = category×512+index; some tables use Group for a different grouping.
Top1Reward2Item number or packed item identifier according to this row. Verify whether a separate category column exists.
Top1Reward2Item/character/requirement level according to the owning entry. Use the context and valid definition range.
Top1Reward2Quantity/amount or number of reward definitions according to the owning entry. Keep linked counts consistent.
Top1Reward3Activation flag where this file uses 0/1: 0 off, 1 on. Nested switches affect only that entry.
Top1Reward3Local currency/reward enum. Its numbers are not interchangeable between Poker, shops, events and quests.
Top1Reward3Quantity/amount or number of reward definitions according to the owning entry. Keep linked counts consistent.
Top1Reward4Activation flag where this file uses 0/1: 0 off, 1 on. Nested switches affect only that entry.
Top1Reward4Local currency/reward enum. Its numbers are not interchangeable between Poker, shops, events and quests.
Top1Reward4Quantity/amount or number of reward definitions according to the owning entry. Keep linked counts consistent.

156 fields · 1 / 6

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.