安裝 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)