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
To give an accurate answer to this question, we need to look at tML’s history.
In 1.3, we used the mod browser, a raspberry pi-run server inside a shoebox that acted as a repository for mods. All mods had a size limit of 50MB (unless otherwise given express permission to use more). It was pretty slow and went down often, also being tied to one of the developer’s networks.
We decided in 1.4 to make the switch to Steam Workshop as a way to provide a much more stable and expansive service. Now, we have no direct size limit, and the workshop will never go down unless it’s a maintenance day. The Workshop also makes it much easier to search for and subscribe to mods, as well as making the creation of mod packs a tad easier. We still however offer the in-game mod browser for ease of convenience, much like how GMod doesn’t force you to use one or the other. Moderation is also much easier as again, only one person had access to the mod browser during 1.3, and depending on the activity of said person, it’d be a much slower process to have things get done.
There’s probably other internal reasons I am not aware of, but that’s what I remember based on discussions. Hope this helps clear everything up :)
See you space cowboy…
-Æ