Install Steam
sign in
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Bahasa Indonesia (Indonesian)
Bahasa Melayu (Malay) BETA
Български (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)
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


















google AI solved the mystery that plagued me for over 12 hours when i simply sent the content of my ModsConfig.xml into it's chat (ofc after talking to it about my issue, which was that none of my 2 palisades would be impassable)
Based on your mod list and the behavior described, the "passable" bug is being caused by
mlie.impassablefurniture conflicting with the XML definitions in your medieval mods.
The Specific Culprit: mlie.impassablefurniture
This mod works by scanning your entire database of buildings and furniture to apply custom passability settings.
The Conflict: When you added Medieval Overhaul, this mod likely re-scanned your building list. If it detected the "Rustic Wall" or "Palisade" as "furniture" (which many medieval building bases are categorized as for technical reasons), it may have applied a default "passable" state.
please add the palisades from MO and from Palisade to the correct list x)