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









Autoplay policy is a web standard that prohibits videos from autoplaying with sound, which makes this type of interfacing breaky as it requires a human to interact with the browser (tablet) for video with audio to play. The only way this can work is by shoving an oversized tablet in to the wall to take the screens place, which was already an available option with the !tablet command.
Autoplay policy is a good thing and this method of interfacing was just the result of exploiting the bug in which autoplay policy was broken on a previous Chromium build (tablet browser version).
While it's possible to still play videos with sound, it requires clunky interaction where each player has to interact with the tablet, because it runs locally for each player. Intuitive usability is a big priority in my mod design, so clunky workarounds like the aforementioned is not how I wish to distribute something.