安裝 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（越南文）
Українська（烏克蘭文）
回報翻譯問題
獎勵
Reddit 
Thanks for not doing that. I've seriously unsubbed from somewhere around 10 mods since WOTC came out, manually installing from backups because the authors just couldn't stop screwing up an already good thing.
No, Legacy is specifically a bad choice, because it was used for the game breaking practice of using original mod page for WOTC version, and reposting old mod on a new page.
Changing the names of existing products is always a bad idea.
Let me give an game example, where principle applies to moids as well.
Tomb Raider was a game that launched an entire series, it earned the right to that name.
In 2013 a remake attempted to steal the name, and add the "Classic" suffix to the original.
Many use Tomb Raider (2013), for the remake, and leave original alone.
I prefer to use, Tomb Raider - A Survivor is Born, but still only rename the remake.
I use the same standard for mods, the original has earned it's name, and needs no suffix.
The WOTC remakes, are the only mods needing a suffix, and WOTC fits every one of them.
So apparently all you care about is the choice of the word "LEGACY" over "VANILLA/LONG WAR 2 VERSION"? Answer: it's shorter.
Not sure why you care. As you point out, I did it the right way. If you're already a subscriber you don't have to unsub or resub to anything; it just works, as always. And I can't be expected to account for the negative associations you have in your head with the word "LEGACY".
"Legacy" has been very badly used, first by the MCM, and other mods since.
Where they repurpoosed the original version to WOTC, and created a new "Legacy" mod, Breaking the existing installs of all users, for no benefit.
Thankfully that bad idea seems to have died, and at least this is still the original mod.
Adding "Legacy" to the name needlessly associates this mod, with that bad practice.
Immersive Names WotC
This is the new mod, and needs a new name, adding the WOTC suffix is the best solution.
Both mods have same name, and thus load order positions, it's the most appropriate name.
Immersive Names
The original name, for an unchanged original mod.
We know it's for the base game, because Immersive Names WotC isn't. No change needed.
Please put the name back to the original one, no need to ever change it,
Here's the Community Mod Launcher: https://github.com/X2CommunityCore/xcom2-launcher/releases
It's so much quicker than Firaxis' own.
With the .XComMod thing I was just referring to the "RequiresXPACK=true" line the WoTC SDK adds. Unfortunately if you set that to False then, counter to logic, the Firaxis launcher will still show a warning for the vanilla game. Regardless of what a mod does, even an INI edit, the warning will be shown for one game or the other.
So, basically, all I'm asking is if you do see some issues whilst using the combined mod with WoTC then please remember those of us who're using just this one.
I can live without the .XComMod boolean: I use the Community Mod Launcher. If you notice any naming issues in your play through a code update to this as well as the Nations combi one would be appreciated.