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








That means the more data the world has the longer the call will take, which can take seconds to execute on some worlds which translates to freezes.
It's also not the kind of thing you call once and forget about it because it's data at that point in time, so it needs to be called frequently to be aware of changes (what are in the slots, selected slot, etc)
It also doesn't contain any info about the page you're on and that's quite confusing.
Additionally you won't see any icons because mods can't draw textures dynamically, they require a transparent material definition which means I'll have to take every block's icon and make a definition from it which certainly won't include mods... and from what I tried the transparent material definitions can't be added dynamically via code either.
So... basically it's not worth the performance hit and effort to get a crappy result :P