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
Game code is comparable to building a house by creating then dropping pieces into place using GPS coordinates. Everything still has to function, and not conflict yet the work putting them in place is done indirectly instead of directly. Mods get their name because they modify existing game files keeping with the analogy a mod would be like telling the game the bed which was formerly a twin is now a king, the sheets are now a different material, of the bed frame is now different. However those modifications require the bed to be found as expected for the mod to work, and the change not conflict with anything else. This means mods are designed for the base code to be the same as when they where last updated. The more expansive the mod the more likely any update will alter what the mod is trying to modify which breaks the mod. The two ways around this is waiting for the mods to update, or downgrading the game back to a version the mods worked with.