安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
Using this next time.
Dynamic Towns was developed and released after receiving permission from TofuSojo, the author of Trading Posts Grow Into Towns. So it is not compatible because it is a replacement.
To keep the AI competitive, there's a scripted mechanism to help the AI place villages in optimal locations if they're falling behind the expected number of towns per city over the course of the game. (This is important because I don't have direct access to the AI worker placement logic in Civ V... only a DLL mod can directly edit the AI's logic.)
And thank you!
*Gratz on the newborn.
I actually recommend leaving adjacency enabled for villages. You may find scenarios as a city planner where you want to build several villages next to each other, with the foresight that one will grow into a town and the other into a large town later on.
It isn't really optimal to build villages where they won't grow into towns eventually, and since towns can't be adjacent to each other, this is the main mechanism that discourages building villages next to towns unless you have a good reason.
If you do build a village next to a town, you'll get a thematic message telling you the village's growth has stagnated. (This won't happen if the village can grow into a large town because it's in a great location!)