when will be Korean Input materialized?

[XinKer Kim]

한글 입력 구현은 언제 실현되나요?

There are any plan in OOTP 22?

[Lukas Berger]

Unfortunately this is unlikely to happen in OOTP22, however we've noted the issue and it's on our list to work on this in a future version of the game.

[XinKer Kim]

Originally Posted by Lukas Berger

Unfortunately this is unlikely to happen in OOTP22, however we've noted the issue and it's on our list to work on this in a future version of the game.

이 부분은 적어도 한국어 입력을 지원하지 않겠다는 내부 결정이 났을 때 한국어 포럼에 알렸어야한다고 생각합니다.

OOTPD는 정말 많은 실망을 안겨주네요.

1. 공식 트레일러의 4/23 한국어 버전 출시
2. OOTP GO!의 정식 출시 때 KBO 2군 선수들의 삭제 (및 이후 가명화)

3. 이번작 한국어 입력 계획 없음.


1.에서 소통문제라고 한 건 억지로라도 이해 했습니다.

2.는 명백한 유저 기만이었습니다. 아직까지 제대로 해결되지도 않았고요. 이전 구매 유저에 대한 환불조차 제대로 이루어지지 않았습니다. 최소한 정식 출시 때 공지했어야 하는 부분이었습니다.

3.의 내용 조차 유저가 개발진에게 질문한 후에나 유저들에게 전달 될 수 있다는 사실이 참담합니다.

유저가 포스트시즌 오류 해결 영상을 올리고, 한국어 번역파일 수정파일을 배포하고 있는데 개발진의 유저를 향한 행보가 이래서는 안될 일입니다.

[Lukas Berger]

For what it's worth, as far as point 3 goes, we did indeed tell you as soon as we'd decided this.

Once it was brought up here on the forums again we discussed again whether this was something we would be able to add in this year, and determined that it was unfortunately not possible at this point in time and I posted the reply in the forums immediately after we'd decided that.

As for point 2, all I can say there is this was a decision that had to be taken at the time it was for reasons entirely beyond the control of the OOTP Go development team.

Ultimately I can't imagine there are many companies that are more willing to directly reply to and engage their users than OOTPD is.

Just look at how often we directly answer questions and respond to issues here on the forums. Of course we cannot directly answer everything, there are too many posts and too few of us, but there are very few game companies in the English speaking world I know of that answer anything like the same amount of user inquiries we do and have the development team themselves as involved in the community as our team is. Though I admittedly do not know if many Korean companies are better at directly engaging with users than English language companies are.

However, the fact is we're still a fairly small (or at best medium sized now) development team and this is the first time we've ever taken on such an enormous project as localization in another language.

Add in to that that we're still also adjusting to being part of a larger corporation now and the extra challenge that brings in regard to communication not only with our users and also our parent company.

Given the above, it's probably inevitable that we would make some mistakes and have some hiccups while adjusting to this totally new process for us.

We're sorry for the mistakes made in the process, but we want to do our best learn from the mistakes and communications issues in the process of releasing such a major project and do our best to avoid or at least minimize similar mistakes in the future.

[jiyongppp]

Originally Posted by Lukas Berger

For what it's worth, as far as point 3 goes, we did indeed tell you as soon as we'd decided this.

Once it was brought up here on the forums again we discussed again whether this was something we would be able to add in this year, and determined that it was unfortunately not possible at this point in time and I posted the reply in the forums immediately after we'd decided that.

As for point 2, all I can say there is this was a decision that had to be taken at the time it was for reasons entirely beyond the control of the OOTP Go development team.

Ultimately I can't imagine there are many companies that are more willing to directly reply to and engage their users than OOTPD is.

Just look at how often we directly answer questions and respond to issues here on the forums. Of course we cannot directly answer everything, there are too many posts and too few of us, but there are very few game companies in the English speaking world I know of that answer anything like the same amount of user inquiries we do and have the development team themselves as involved in the community as our team is. Though I admittedly do not know if many Korean companies are better at directly engaging with users than English language companies are.

However, the fact is we're still a fairly small (or at best medium sized now) development team and this is the first time we've ever taken on such an enormous project as localization in another language.

Add in to that that we're still also adjusting to being part of a larger corporation now and the extra challenge that brings in regard to communication not only with our users and also our parent company.

Given the above, it's probably inevitable that we would make some mistakes and have some hiccups while adjusting to this totally new process for us.

We're sorry for the mistakes made in the process, but we want to do our best learn from the mistakes and communications issues in the process of releasing such a major project and do our best to avoid or at least minimize similar mistakes in the future.

I certainly know that you are trying. And I know that few companies communicate user-friendlyly like OOTPD. I think it's quite interesting and I'm always grateful for it.
But you are not a volunteer organization. You are a business, a profit-seeking organization. Korean users are buyers of services, not beta testers either. We have paid a fair price to use the service and therefore have the right to enjoy the promised service.
So to put it bluntly, users don't need to understand about your 'mistakes' at all. If you say about them yourself, you're confessing that you're an amateur, not a professional.
Oh, I'm not trying to convict you. Especially recently, I know Lukas you've been communicating very well so I'm very happy with that. But I hope you show more professionalism as a service as we showed you the sales volume.

[XinKer Kim]

Originally Posted by lukas berger

for what it's worth, as far as point 3 goes, we did indeed tell you as soon as we'd decided this.

이 부분은 적어도 한국어 입력을 지원하지 않겠다는 내부 결정이 났을 때 한국어 포럼에 알렸어야한다고 생각합니다.

한국어 포럼에 명시한 내용이 있다면, 링크 부탁드리겠습니다. 아무렴 이 스레드보다는 해당 공지를 유저들에게 공유하는 편이 더 나을 듯 합니다.

[Lukas Berger]

Originally Posted by XinKer Kim

한국어 포럼에 명시한 내용이 있다면, 링크 부탁드리겠습니다. 아무렴 이 스레드보다는 해당 공지를 유저들에게 공유하는 편이 더 나을 듯 합니다.

It's only mentioned in this thread.

[XinKer Kim]

Originally Posted by lukas berger

for what it's worth, as far as point 3 goes, we did indeed tell you as soon as we'd decided this.

이 부분은 적어도 한국어 입력을 지원하지 않겠다는 내부 결정이 났을 때 한국어 포럼에 알렸어야한다고 생각합니다.

Originally Posted by Lukas Berger

It's only mentioned in this thread.

This means that OOTPD had no idea about the Korean input materialization plan (till I ask you) or thought it is difficult to apply for OOTP22, but overlooked the importance of informing Korean users.

There should be Notifications.

[Lukas Berger]

Originally Posted by XinKer Kim

There should be Notifications.

I do agree that would be ideal.

The reality of the current situation though, is that for now we do not have a Korean community manager. We are looking to add a community manager, but until we do, likely the only announcements that will come directly in Korean will be major announcements issued through Com2uS (new game releases etc).

Information on whether a specific feature will be added to this year's game, whether a specific bug will be fixed and other similar issues will continue to come through our replies (in English, sorry) to individual questions and posts on the forums.

Of course that may change any time, and I hope it will change soon.

For now, replies to posts here by myself, Matt or possibly sometimes another member of the development team (more or less frequently at specific points in time, as we're able to do so) will continue to be the main way we we try to keep our Korean users informed of more specific feature related news and provide answers to specific questions.

[XinKer Kim]

OOTPD can write a thread for Notifications.

I don't expect a detailed patchlog, but OOTPD can write enough about Korean input, bug fixes, and UI updates here. In English would be OK.

The earliest time is when you think it's late.

(one person (=I) have left more than 7,200 comments on the one Korean OOTP online community since March 27 this year. There will be more if other OOTP communities are included.)

You can do much better than me, who are professionals and amateurs.

[Lukas Berger]

Originally Posted by XinKer Kim

You can do much better than me, who are professionals and amateurs.

I mean, yes I do agree, and this fair enough such as it goes.

That being said, just speaking for myself, technically replying here is not in my job description at all and I already work far more than 40 hours a week on my actual job, which is assisting with development of the game and especially maintaining the player database.

I take the extra time to reply here as much as possible because I love the game and the company and want to help our customers, as well as improve the game as much as possible (and have a personal passion for Korean baseball as well).

I will continue to do so as much as possible and my other duties allow, as will other members of the development team like Matt, from time to time.

As much as we do try to focus on communication as a company, we are still not a large development team. Those of us who mainly communicate here on the forums are also those who are working on making the actual game. So our primary focus is on working on the game itself and every minute we spend communicating on the forums is a minute we are not working on the game. So even though communication is necessary, we have to find a balance.

As I mentioned already, ultimately our goal is to hire and integrate a bilingual Korean community manager into our team, and once that happens we'll be able to be much more proactive in communicating with the Korean community.

For now, I do agree we can still probably take some steps to improve the communication in the meantime.

A notifications thread is a very good idea, and we'll consider if it might be possible to implement something like that in the future, where we can at least include some basic information on major issues to keep you better updated.

[XinKer Kim]

Thank you for the detailed story.

It may have been lacking in my expression, but it is not the amount of communication, but the Quality of contents shared.

I will try to share/communicate a series of forum issues to Korean users well.

[Lukas Berger]

Originally Posted by XinKer Kim

It may have been lacking in my expression, but it is not the amount of communication, but the Quality of contents shared.

Yes, this is a very fair point, and I do agree we can improve here.

Originally Posted by XinKer Kim

I will try to share/communicate a series of forum issues to Korean users well.

Thank you for this, it's very much appreciated!

The fact is, even though we are slowly growing larger, we still depend a great deal on volunteers and community members help, and we greatly appreciate that we have such dedicated fans who are willing to do so much to help us improve the game

[XinKer Kim]

완전히 새로운 담론입니다.

Even if Korean input is not implemented, it would be good to search in English.

for now, OhJi-Hwan is searchable (no Korean name XML case, Case-sensitive required), but 오지환 is not Searchable (Korean name XML case).

Is it possible that search 오지환 for [Oh],[Ji-h],etc...?
Case-sensitive required 문제는 해결하지 못해도 괜찮습니다. 한국어 환경에서도 알파벳으로 검색이 가능하다면, UX will be improved.

Of course, the ultimate problem will be Korean input support and searchability with it.

Another problem exist in OhJi-Hwan. Family name is Oh, but it [Oh] and [Ji-Hwan] are attached. there must be SPACE, for Readability(like Oh Ji-Hwan). (is it better that Making another thread?)