OOTP22 KBO Rules Inquiries

[wer33]

1.In OOTP22, when you play KBO, you can see that it is in line with MLB as you proceed with the trade. Veteran preferences in trade setting rather than promising players would be right for KBO.

2. The KBO FA system has a player compensation system. This part is not implemented in OOTP22 Do you have any thoughts to add it?

3. The KBO posting system has the right to negotiate first. This will also be necessary for OOTP22.

[XinKer Kim]

1. 글로벌 설정에 있는 AI setting - trade preference 를 Global이 아닌 League에 할당한다면 (그게 가능할지 궁금하네요) 각자 리그에 맞는 트레이드 가중치가 작동될 것 같습니다.

2. 의향이야는 있겠으나 구현할 방법을 못찾고있을겁니다.. 방안에 대한 제시가 필요해요.

3. He mean, "Players who transferred to overseas leagues through the posting system will return to their own leagues, The original team has the right to negotiate first."
실제로, 포스팅시스템을 통해 해외진출을 한 선수(e.g. ByungHo Park, Hyun-Jin Ryu, Ha-Seong Kim)가 KBO로 복귀하기 위해서는, 무조건 원소속팀(포스팅 이적료를 받은 구단)으로 복귀해야만합니다. NOT FA. (In order to obtain FA qualification, four years is required.)

[Lukas Berger]

So to reply to this, I believe the AI trading preferences are global and not local. I'm not sure how easy or hard it might be to implement league specific trading preferences, but I can at least add that to the list of ideas we're considering for future versions.

That being said, even for MLB many users prefer to tweak and change this themselves to reflect their own feeling on exactly how much value to put on younger/older players, so I'm not sure that even with league specific settings we'd ever be able to set a default that will make everyone happy. This is probably a setting people will always want to change for their own games.

2. Basically, I'd agree with what XinKer Kim mentions. This is something we'd like to add in the future, but it's probably a little tricky to implement and to balance this, so it's something we'll have to think about.

We would welcome suggestions on how this should be implemented.

3. I wouldn't imagine this would be terribly hard to add, but it's not really something we had prioritized for this year. I'll bring this up with the development team on the list of potential future improvements.