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
The only way for a District to be placed on a resource, is to have that resource be harvestable. The game will then remove the resource when you place a district down on top of it. There is nothing that modders can do about that due to that code being outside of modder control. This mod makes all resources harvestable programmatically (all modded resources supported). This mod then listens for a lua code event that triggers when a resource is removed from the map. If the resource removal was due to a district being placed on top of it, that resource will be put back into the hex. Any resource under a completed district or wonder, will act the same way as if a city was placed on it. Any mod (like this) that uses lua code to make changes to the game map/units/cities will likely cause desyncs in multiplayer.