Importing
Loose .ydd / .ytd files
Select an item and click Import .ydd / .ytd (or right‑click an item → import). The model fills the item; each texture becomes a variant. Files are copied into the project's assets/ folder.
Durty Cloth Tool projects (.dctproj)
Already have projects in Durty Cloth Tool? Import them directly and keep working — no rebuild from scratch.
How to import:
From Home (or the import menu) choose the Durty import.
Point it at the Durty project — either the
.dctprojmanifest or the project folder.The tool reads the manifest, maps every clothing item to the right slot, gender and drawable number, and copies the referenced models and textures into your KOJA project.
What comes across:
All clothing items with their slot, gender, drawable number and name.
Every model and texture variant, de‑duplicated by content — so a big EUP pack often shrinks dramatically on import (duplicate files are stored once).
Component vs. prop typing is preserved.
Durty stores its assets as GUID‑named files in a data/ folder. The import resolves the friendly names and rebuilds a clean, self‑contained KOJA project — you don't need to keep the original Durty folder afterwards.
Dummy / placeholder entries in the Durty project are skipped (they have no real files). If an item looks empty after import, it was a dummy on the Durty side.
Sharing items between projects (.kct)
To move a handful of items between Cloth Tool projects — or share them with a teammate — export them as a .kct package rather than importing a whole project. See Sharing Packages (.kct).
Portability
Every import copies assets into the project and stores paths relative to the project folder. That means you can move or rename the whole project folder freely — the tool re‑resolves everything (and auto‑heals older projects that still held absolute paths) on open.