安裝 Steam
登入
|
語言
簡體中文
日本語(日文)
한국어(韓文)
ไทย(泰文)
Български(保加利亞文)
Čeština(捷克文)
Dansk(丹麥文)
Deutsch(德文)
English(英文)
Español - España(西班牙文 - 西班牙)
Español - Latinoamérica(西班牙文 - 拉丁美洲)
Ελληνικά(希臘文)
Français(法文)
Italiano(義大利文)
Bahasa Indonesia(印尼語)
Magyar(匈牙利文)
Nederlands(荷蘭文)
Norsk(挪威文)
Polski(波蘭文)
Português(葡萄牙文 - 葡萄牙)
Português - Brasil(葡萄牙文 - 巴西)
Română(羅馬尼亞文)
Русский(俄文)
Suomi(芬蘭文)
Svenska(瑞典文)
Türkçe(土耳其文)
tiếng Việt(越南文)
Українська(烏克蘭文)
回報翻譯問題
While yes, these other mod hosting websites exist, if a game on steam has workshop support, it is highly unlikely for people to want to post in nexus mods. If they have the ease of access of the Steam Workshop, with the much larger audience there, then most people will not post in Nexus mods. (Which is what happens with a lot of games).
The best solution is asking the modder to also release the content on platforms such as moddb or nexusmods.
I have mods on Steam, Nexus Mods, and Thunderstore.io.
It sounds silly but it is a PITA to maintain the mods on multiple sites. Steam and Nexus mods both have their own special version of BBCode. Thunderstore.io is great since it supports markdown.
I even wrote two utilities to convert Markdown to Nexus BBCode and Steam BBCode and it is still a pain.
None of them have an automated way to upload or update a mod.
Generally if there is Steam Workshop support, I won't bother with the other sites.
In my personal experience, my mods on Workshop have about 10x more subscriptions/unique downloads than the other sites.
I'll add a github repo link in the mod's description for other stores; but not many modders do that.
Come on, someone must have figured out some CI/CD. You even did some like you said on "I even wrote two utilities to convert Markdown to Nexus BBCode and Steam BBCode and it is still a pain."
Heh. One would think.