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
Good question. It depends on the modding interface with the game's coded API, what language the embedded scripting environment and game engine pipeline is in, its code structure and system specs, and other factors. You have to do it to find out on a case-by-case basis unless you use a newer, more optimized language and more predictable performant and tested-true coding methods involving knowledge of how processors waste time shuffling high-level excess data around from memory to caches. You know they (CPUs), and GPUs even more so, have the ability to run billions of complex computation instructions per second, right? And most operations can be simplified dramatically if you put some thought into it (as AI has been showing us up by thousands of times, without even using neuromorphic non-von-neumann computation frameworks).
Now if only developers could keep up..