Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
It's not 'casual modding' territory, but literally 'developer kit' territory.
Info and some videos are here, will be more:
https://wiki.nexusmods.com/index.php/KCD_Before_You_Start
After completing first step we use psql.exe to restore the database from provided dumps.
psql.exe -f Data_reference/modding.sql -U postgres –d ConfigDB -q
psql.exe -f Data_reference/public.sql -U postgres –d ConfigDB -q
Ideally this command should run with no output of any kind (the -q switch hides all non-errors, and there should be no errors). In your database, there should be now a schema called modding with 468 tables.
Unfortunately, in my database, there is no schema called modding, and obviously there are no 468 tables. There are only four schema, "pg_toast", "pg_toast_temp_1", "pg_temp_1", and "public". These commands do not work in the psql.exe as directed.
Can anyone suggest another way?
"c:\Program Files\PostgreSQL\11\bin\psql.exe" -f D:\SteamLibrary\steamapps\common\KingdomComeDeliverance\Data_reference\modding.sql -U postgres -d ConfigDB -q