安装 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(越南语)
Українська(乌克兰语)
报告翻译问题






Also, why can't we edit comments, Valve? T.T
setltileprotection 1 false
setltileprotection 1 true
should be
settileprotection 1 false
settileprotection 1 true
Whoops.
settileprotection 0 false
settileprotection 0 true
setltileprotection 1 false
setltileprotection 1 true
These commands require /admin to be active, and I use these commands far more than any of the ones listed in the screenshot you shared, so the inclusion here would be incredibly useful.
Ideally, you could use the same hotkey to set to true, then to false (if true, set to false, and vice versa) but that's optional.
Story missions (AKA instance dungeons) and multiple mods (such as Felin mod) use settileprotection to prevent the player from modifying or destroying specific regions or constructs.
You can try this out yourself in any of the story missions, such as the Grand Pagoda Library, or in the instance dungeons such as Dreadwing mission. Make sure /admin is active, then use /settileprotection 0 false and then you can destroy blocks/objects (and collect them!) in these worlds.