Probability-based item compliance in Korea requires more than publishing a percentage table. Server-side probabilities, in-game information, website disclosures, and change notices must remain consistent throughout the game’s lifecycle.
Korea’s Game Industry Promotion Act and its Enforcement Decree establish requirements covering numerical precision, probability changes, multi-stage mechanics, variable rates, and pity systems. These requirements create a shared responsibility across engineering, live operations, publishing, and compliance teams.
Probability information must generally be displayed as a percentage in a form users can easily understand.
Korean law does not require every probability to be displayed to exactly four decimal places. When rounding is necessary, however, the value may be rounded only at a decimal place at least four positions after the first non-zero digit.
For example:
Displaying the value simply as 0.0012% or 0.0011% may not provide sufficient precision.
Where percentages are difficult to understand, fractions, functions, or explanatory text may be used when they communicate the probability more clearly. Truncation is not automatically safer than rounding; the displayed value must accurately reflect the probability applied by the game.
Although not legally required, a Single Source of Truth can prevent discrepancies between server logic and public disclosures.
Studios should:
Fixed-precision decimals, integer weights, or rational representations may help prevent conversion errors between server and display values.
When disclosed probability information changes, the operator must publish the change details and effective time in advance.
The notice must generally appear:
The notice should be published before the changed item becomes available for sale.
Relevant changes may include:
If advance notice is genuinely impracticable because of an urgent correction or another unavoidable reason, the information must be published without delay after that reason has been resolved.
Korean law does not require a universal before-and-after table. Nevertheless, a comparison table showing the previous rate, new rate, affected item, effective time, and applicable version is a strong compliance practice.
A safer deployment process is to:
Automation through an internal API or structured data format is not legally required, but it can reduce copying errors and publication delays.
Korean rules address capsule-type, enhancement-type, and composition-type probability-based items. If one mechanic falls within multiple categories, the requirements applicable to each stage must be considered.
For example, a paid box may randomly provide materials that are later used in a random fusion system. If both the box-opening and fusion stages independently qualify as regulated probability-based mechanics, the applicable probability information for both stages should be disclosed.
A deterministic stage does not become probabilistic simply because it follows a loot box. Each stage should be reviewed according to whether paid items are involved and whether the outcome is determined by chance.
Some rates change according to the number of attempts, previous failures, owned items, gameplay progress, or other user-specific conditions.
The disclosure should explain:
This includes escalating rates, wishlist systems, duplicate protection, and probability adjustments based on previous outcomes.
For pity systems, the disclosure should also identify:
If the probability remains constant until the guaranteed attempt, that structure should be stated clearly. If it increases at defined thresholds, the relevant rates should be disclosed in an understandable form.
No single visual format is mandatory. Depending on the mechanic, studios may use a percentage table, attempt schedule, formula, function, or explanatory text. The essential requirement is that the disclosure accurately explains the probability and the conditions affecting the result.
Studios should maintain:
Pity, fusion, wishlist, and dynamic-weighting logic should also be documented. Website disclosures should be searchable and easy to verify, rather than relying solely on image-based tables.
If direct in-game display is impracticable because of the volume of information, the game may provide a direct link to the relevant website disclosure page where permitted.
Probability disclosure is a continuing operational obligation, not a final legal review performed after development.
Generating server configurations, public disclosures, change notices, and verification records from the same controlled source can reduce errors and make regulatory responses more efficient.
For related enforcement and consumer-risk considerations, see Korea’s Zero-Tolerance Era: Why Probability Errors Are Now Business-Critical.
TheGameAgent supports global game developers and publishers with probability-disclosure reviews, technical compliance assessments, evidence preparation, Korean regulatory communication, and corrective-action coordination.
GRAC is expanding Korea’s probability-based item user protection framework through a new partnership focused on damage relief, joint responses, and research.
Korea is moving to strengthen Domestic Agent requirements for overseas game companies. Here are six key proposed changes involving user protection, supervision, Korean affiliates, and enforcement.
A practical breakdown of how GRAC screens probability reports, verifies game data with technical experts, and coordinates enforcement and user relief.
© 2026 TheGameAgent.
All rights reserved.
