安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
Great mod btw!
C. If you have any other mods installed, some of them may interfere for one reason or another. This doesn't happen very often but it's safer to develop your mod with a vanilla setup first (unless you make an addon for another existing mod of course; small QoL patches are normally non-instrusive and can be used as well) and only then install other mods to see if things work together.
A. If you move your dungeon's connectors to another layer (for example from "objects" to "anchors" or the other way around), Tiled may not like this and either refuse to spawn certain dungeon parts or give a similar error. So it's usually best to keep connectors where they are.
B. If your dungeon uses custom tilesets, you should look through them and check if they're set up properly. Sometimes Tiled bugs out and switches the ID numbers of objects in a tileset. I've had a similar issue with microdungeon generation because of this, setting the correct ID numbers resolved it.
"Fatal Error: Access violation detected at 00007FF7E4A6D772 (Read of Address FFFFFFFFFFFFFFFFF)