安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
Master file itself hasn't broken however.
-- on another note : Enenera has new SW mods, so there's always those
In addition, I do not approve of my user base being harassed to remove & uninstall my mods.
Let alone after I had left WC, to suddenly have it flip off my workshop.
So no, turning it off isn't good enough.
They can fuck themselves.
So not only would I suffer every single bug of WC, I'd suffer every single new 'build' of WC being exclusive which means possibly dozens of dependencies trying to kill each other, even if I removed the hostile code myself, a user just has to not notice 1 single instance of WC in their mod list, and mine gets deleted from the entire game.
So I would be constantly getting invisible errors in my user error reports, from possibly a single mod using WC of any kind just shutting mine down, flashing error code that doesn't exist, while concealing itself from crash logs.
Akin to if SE itself decided randomly one day, to uninstall other space games, lock them out, and hide that it did it one day.
This text & deletion is hidden from the Crash log, meaning when this thing breaks another mod it has concealed that it was the source of the problem.
So lets say I add any block with a Vanilla TypeID of say any Turret, any fixed-mount gun or a flare, that block is then instantly deleted & locked from the world automatically, and no new blueprints are allowed to have them either -- effectively stripping entire typeIDs from the game itself.
(Part 1)
I rather spend my time doing game development than fighting a script mod that got full of itself.