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









Because:
- There's no good univeral rule, some lights will always be broken, you need to target them with id and there's just no way because BaroDevs don't store unique item ids
- As you said it's not safe, it needs some change history, undo command, better light editing ui,
and it's all very painful to make in lua
- And it's hard to sync in multiplayer, those edits are not synced so i have no idea how that works in multiplayer, it needs tons of new net evens to sync it
So it needs to be rewritten from scratch, and i won't do it until:
- Someone would find a way to deduce true item id, idk, from their props or from their position in raw .sub file
- Until i finish my GUI framework because baro gui is dead
- And until mr. NeckRopeMancer finish his great luatrauma rework which should, in particular, simplify networking
So if you save it to the same file it would be modified
Just save it to some other file if you want to test it
which lights are broken? could you give me a screenshot?
also did you touch mod settings?