Инсталирайте 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)