Steam 설치
로그인
|
언어
简体中文(중국어 간체)
繁體中文(중국어 번체)
日本語(일본어)
ไทย(태국어)
Български(불가리아어)
Čeština(체코어)
Dansk(덴마크어)
Deutsch(독일어)
English(영어)
Español - España(스페인어 - 스페인)
Español - Latinoamérica(스페인어 - 중남미)
Ελληνικά(그리스어)
Français(프랑스어)
Italiano(이탈리아어)
Bahasa Indonesia(인도네시아어)
Magyar(헝가리어)
Nederlands(네덜란드어)
Norsk(노르웨이어)
Polski(폴란드어)
Português(포르투갈어 - 포르투갈)
Português - Brasil(포르투갈어 - 브라질)
Română(루마니아어)
Русский(러시아어)
Suomi(핀란드어)
Svenska(스웨덴어)
Türkçe(튀르키예어)
Tiếng Việt(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
Sidenote: someone added a goblin race.
Start a game, choose basics, and right before the sword lord talks I edit the save reload and try different builds. I set xp to 400k get to lvl 15 I think.
https://github.com/ericfitzgerald/KingmakerCharacterEditor
To me atleast, it's not about combat effectiveness testing, but more of a framework? testing to see ingame what it will become with class x and y with feat z, and to check that the "idea" works in game\theory.
You could do the same on paper, but doing it ingame takes into account all the game peculiarities.
Cant do it on paper yet because bugs.
What should work doesn't normaly work, or in this game, what should work normaly does not work.
That way you could load their save and buy a custom companion at high level.