OOTP’s KBO implementation feels structurally neglected despite official licensing

heroes21v · 01-10-2026, 10:48 PM

I want to share feedback specifically from the perspective of a KBO-focused user. This is not a complaint about realism preferences, but about long-standing structural and product-level issues that have not improved over multiple releases.

1. Incomplete Korean localization
Despite KBO being officially supported for several years, Korean localization remains noticeably incomplete. Many settings menus and even some newly introduced features are still displayed only in English.
This goes beyond translation polish — it creates a usability gap for Korean users and gives the impression that KBO support is not treated as a first-class feature.

2. Overwhelmingly MLB-centric assumptions
Several design choices clearly prioritize MLB logic, even where they directly conflict with KBO reality.

* KBO All-Star Game
The game disables the All-Star Game on the grounds that KBO is a single league. However, in reality, KBO has long operated All-Star Games by dividing teams into internally defined groups. This is a clear case where real-world KBO rules are overridden by MLB-based system limitations.

* Player name display issues
Korean player names are often displayed in awkward mixed formats (e.g., surname in Korean with given name romanized). This is not how names are used or recognized in KBO contexts and breaks immersion in a league where naming conventions are culturally significant.

* Coaching staff structure and development philosophy
In recent years, KBO teams have increasingly emphasized player development as a core organizational policy. This has led to the creation and active use of new staff roles such as assistant coaches, development-focused staff, and mental skills coaches. These roles are not cosmetic; they reflect how KBO teams manage players, especially younger ones, over the long term.

However, OOTP’s coaching system is effectively locked to an MLB-style structure. Users cannot create new coaching roles or meaningfully differentiate responsibilities to reflect league-specific priorities. As a result, KBO teams in OOTP are forced into a one-size-fits-all coaching model that ignores the league’s evolving development-oriented approach.

3. Minimal evolution beyond an MLB framework
Although OOTP is a yearly release, improvements tend to be incremental system upgrades rather than meaningful league-specific design.
From a KBO user’s perspective, the game feels like an MLB-centric engine with KBO functionality “layered on,” rather than a league modeled with its own assumptions, priorities, and constraints.

4. Need for league-specific core settings
Given that OOTP is a long-running title and now under Com2uS ownership, it feels reasonable to expect deeper structural differentiation between leagues.
For future versions (notably OOTP 27), separate and explicit MLB/KBO configuration layers — affecting rules, presentation, AI priorities, and UI defaults — seem necessary rather than optional.

5. Why this matters
OOTP is one of the very few baseball games with an official KBO license, and fundamentally it is an excellent baseball simulation.
I purchased OOTP 26 specifically for KBO play, but ultimately requested a refund due to the MLB-oriented systems and underdeveloped KBO experience. This post is not written out of hostility, but out of genuine hope that future versions will treat KBO as more than a secondary mode.

At present, KBO in OOTP feels supported in name and database, but not in design philosophy. That gap is what I hope can be meaningfully addressed going forward.

01-10-2026, 10:48 PM	#1
heroes21v Bat Boy Join Date: Jan 2026 Posts: 4	OOTP’s KBO implementation feels structurally neglected despite official licensing I want to share feedback specifically from the perspective of a KBO-focused user. This is not a complaint about realism preferences, but about long-standing structural and product-level issues that have not improved over multiple releases. 1. Incomplete Korean localization Despite KBO being officially supported for several years, Korean localization remains noticeably incomplete. Many settings menus and even some newly introduced features are still displayed only in English. This goes beyond translation polish — it creates a usability gap for Korean users and gives the impression that KBO support is not treated as a first-class feature. 2. Overwhelmingly MLB-centric assumptions Several design choices clearly prioritize MLB logic, even where they directly conflict with KBO reality. * KBO All-Star Game The game disables the All-Star Game on the grounds that KBO is a single league. However, in reality, KBO has long operated All-Star Games by dividing teams into internally defined groups. This is a clear case where real-world KBO rules are overridden by MLB-based system limitations. * Player name display issues Korean player names are often displayed in awkward mixed formats (e.g., surname in Korean with given name romanized). This is not how names are used or recognized in KBO contexts and breaks immersion in a league where naming conventions are culturally significant. * Coaching staff structure and development philosophy In recent years, KBO teams have increasingly emphasized player development as a core organizational policy. This has led to the creation and active use of new staff roles such as assistant coaches, development-focused staff, and mental skills coaches. These roles are not cosmetic; they reflect how KBO teams manage players, especially younger ones, over the long term. However, OOTP’s coaching system is effectively locked to an MLB-style structure. Users cannot create new coaching roles or meaningfully differentiate responsibilities to reflect league-specific priorities. As a result, KBO teams in OOTP are forced into a one-size-fits-all coaching model that ignores the league’s evolving development-oriented approach. 3. Minimal evolution beyond an MLB framework Although OOTP is a yearly release, improvements tend to be incremental system upgrades rather than meaningful league-specific design. From a KBO user’s perspective, the game feels like an MLB-centric engine with KBO functionality “layered on,” rather than a league modeled with its own assumptions, priorities, and constraints. 4. Need for league-specific core settings Given that OOTP is a long-running title and now under Com2uS ownership, it feels reasonable to expect deeper structural differentiation between leagues. For future versions (notably OOTP 27), separate and explicit MLB/KBO configuration layers — affecting rules, presentation, AI priorities, and UI defaults — seem necessary rather than optional. 5. Why this matters OOTP is one of the very few baseball games with an official KBO license, and fundamentally it is an excellent baseball simulation. I purchased OOTP 26 specifically for KBO play, but ultimately requested a refund due to the MLB-oriented systems and underdeveloped KBO experience. This post is not written out of hostility, but out of genuine hope that future versions will treat KBO as more than a secondary mode. At present, KBO in OOTP feels supported in name and database, but not in design philosophy. That gap is what I hope can be meaningfully addressed going forward.