Korea’s probability disclosure requirements apply not only to the existence of a probability table but also to the accuracy, precision, accessibility, and consistency of the information presented to users.
Game developers and live-operations teams frequently encounter practical questions involving decimal places, repeating decimals, rounding, and probability totals that do not add up to exactly 100%.
This guide answers five common questions based on Korea’s Game Industry Promotion Act, its Enforcement Decree, and the Ministry of Culture, Sports and Tourism’s official Guideline on the Disclosure of Probability Information for Probabilistic Items.
Korea’s statutory probability disclosure system took effect on March 22, 2024.
A separate amendment effective August 1, 2025 introduced civil liability for failing to disclose probability information or displaying false information. When a violation is intentional, a court may determine damages of up to three times the recognized loss.
This is not the same as an administrative penalty equal to 3% of a company’s total revenue.
A legislative proposal introduced in December 2025 discussed an administrative surcharge of up to 3% of revenue or KRW 1 billion in certain cases. As of this article’s publication date, that proposal should not be described as an enacted amendment.
In addition, qualifying overseas game operators became subject to Korea’s domestic agent requirement on October 23, 2025. Failure to designate a required domestic agent may result in an administrative fine of up to KRW 20 million.
Answer: No.
Probability information must generally be displayed as a percentage. When rounding is necessary, the probability may be rounded at a decimal place that is at least four positions lower than the decimal place containing the first non-zero digit.
This is a positional decimal rule. It should not be simplified into a general “four significant figures” rule.
For example:
The value 0.0012% stops only one decimal position below the first non-zero digit and therefore does not provide the precision contemplated by the Enforcement Decree.
Where the actual probability is a finite decimal, displaying the exact value is generally clearer than introducing unnecessary rounding.
Engineering teams should document one consistent rounding method and apply it to the in-game display, website disclosure, and any supporting regulatory materials.
Example: 0.01023%
Answer: If 0.01023% is the exact applied probability, it may be displayed as 0.01023%.
Zeros appearing within a decimal do not create a separate legal rule. The important questions are whether the displayed value is accurate and, if a longer value has been rounded, whether the permitted decimal position has been used.
For example:
A team should not shorten a rate merely because the shortened number appears to contain enough significant figures. The Korean rule is based on decimal position, not a general significant-figure calculation.
Example: 1/3 = 33.333333…%
Answer: A repeating probability may be displayed as a rounded percentage or through a fraction, function, or explanatory text when that format is easier for users to understand.
For example:
Korea’s Enforcement Decree expressly permits fractions, functions, and text when those methods communicate the probability more clearly than a percentage.
The law also permits rounding under its prescribed precision standard. It does not require engineering teams to use FLOOR or TRUNCATE.
Truncation may create a displayed probability that is lower than the applied probability. Rounding may create a displayed value that is slightly higher or lower. The legally relevant point is whether the display method follows the applicable rule and accurately represents the underlying probability.
From an engineering perspective, the server value, disclosure value, and UI string should be generated from the same approved source or calculation method.
Example: 12.345%
Answer: If 12.345% is the exact applied probability, it is generally preferable to display that exact figure.
The existence of an integer component does not mean that a rate may automatically be shortened based on four significant figures.
For example, changing 12.345% to 12.35% introduces a different displayed value. That change should not be treated as automatically compliant merely because the result appears sufficiently precise.
If the applied probability is a longer or repeating decimal, the operator should use the rounding standard under the Enforcement Decree or present the probability through another permitted format.
A practical disclosure policy should distinguish between:
The calculation method should be documented and applied consistently across every disclosure location.
Answer: First confirm that the underlying probability distribution is correct. Then increase the display precision or use another permitted format if necessary.
Small differences may occur when individual probabilities are rounded separately. For example, a displayed table may total 99.9999% or 100.0001% even though the unrounded system probabilities total exactly 100%.
Recommended steps include:
Confirm that the server weights, denominator, conditional exclusions, and individual probabilities are correct before assuming the difference is caused by rounding.
Adding decimal places may reduce or eliminate the visible discrepancy.
If percentages make the underlying mechanic difficult to understand, another format permitted by the Enforcement Decree may be more appropriate.
A supplementary note may state:
Individual probabilities are rounded in accordance with the applicable display standard. As a result, the sum of the displayed probabilities may differ slightly from 100%.
This explanation does not excuse inaccurate individual probabilities. It should only describe a genuine mathematical difference created by permitted rounding.
The applied probabilities should reflect the approved game design. Arbitrarily modifying server values or selected displayed values merely to force the visible total to 100% can create a more serious inconsistency.
The safer approach is to improve precision, explain the rounding effect, or use another legally permitted presentation method.
Before publishing a probability table, verify that:
TheGameAgent supports global game developers and publishers with probability disclosure reviews, technical compliance assessments, regulatory-response materials, and corrective-action coordination.
A well-designed probability disclosure process should allow the engineering, operations, and compliance teams to reproduce every public percentage from the approved live configuration.
A step-by-step guide for global developers preparing a Korean adult-only game rating application, including required materials, review timing, and store integration.
A practical guide to GSOK’s game-advertising standards, monitoring process, major compliance risks, and pre-launch review checklist.
The Soul Strike case shows how broad “ad-free” claims can create Korean consumer-protection risk. Learn how KFTC enforcement and GSOK self-regulation apply.
© 2026 TheGameAgent.
All rights reserved.
