安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
讨论规则及指引
0 
举报此帖
So far we've been handling whitelisting in two ways:
- we have a dedicated modding section on our Discord, where people just ping me with whitelist requests. Other people on the discord can already advise if something is "whitelistable"
- before an update, i'll browse the workshop to see if there are mods that qualify to be whitelisted and add them (if i don't forget it :D )
Do you think this works, or is there some part missing?
Maybe implementing a new tag for mods would work; one that the game can read and let you know in game whether a selected mod will block Prestige.
Currently, the Diamond Upgrades mod blocks all achievements. I tested this: achievements with perpetual unlock conditions, like unlocking new gameplay features, were only gotten after the mod was disabled, and any mods that require an instance, such as beating a certain size map, were not credited at all, even after Diamond Upgrades was disabled. If that's not intentional, it might want to be checked.
I think it would be best to have that in the workshop directly, so tags are a great idea. I'll add one for prestige whitelist.