安装 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(越南语)
Українська(乌克兰语)
报告翻译问题




Instacrashes can definitely be a headache, here are a couple of things you can try to get a map running again - these don't always work, but I find them often helpful in developing a custom map.
1: Check the "player-prev" text file in the parent folder to the "mod" folder. Somewhere in the file will be a line starting CityDefinition.FromUGC: Loading (your map name) from JSON.. Under this line will be errors that the game picked up during launch. I find this most useful when the game launches successfully but says "error in loading (map name)", or words to that effect.
2: Remove your new map from the mod folder and start with a clean map file you know works. Copy and paste information to replace part by part, testing a launch each time, and creating backups of successes. This takes a little longer, but can help if you really can't find the source of an error.
3: Check spellings and ID links between files - this may be the issue if the mod guide code isn't working. It could also be a missing or unnecessary comma.
Hope this helps - error fixing for custom maps can be a pain to resolve!