Project Structure
A standard Kaledis project follows a specific structure to ensure tools work correctly.
File Layout
Section titled “File Layout”my-game/├── .vscode/ # Editor settings│ ├── settings.json # VS Code specific settings├── assets/ # Game assets (images, audio, fonts)│ └── logo.png├── luau_packages/ # Dependencies managed by Pesde├── src/ # Source code│ ├── main.luau # Entry point│ └── components/ # Game components├── kaledis.toml # Main configuration file├── pesde.toml # Pesde package manager config├── .luaurc # Luau configuration├── kaledis.schema.json # Schema for config validation└── .gitignore # Git ignore fileKey Directories
Section titled “Key Directories”Contains all your Luau source code. Kaledis transpiles files in this directory.
- Entry Point: Usually
main.luau. Can be changed inkaledis.toml.
assets/
Section titled “assets/”Place your static assets here. Kaledis copies these files to the build output.
- Referenced in
kaledis.tomlunder[project] asset_path.
luau_packages/
Section titled “luau_packages/”Generated by Pesde. Contains external libraries.
- Do not edit manually. Use
pesde addto manage dependencies.
Key Files
Section titled “Key Files”kaledis.toml
Section titled “kaledis.toml”The configuration file for your project. Defines window settings, modules, and build options.
pesde.toml
Section titled “pesde.toml”Configuration for the Pesde package manager. Defines dependencies and package scripts.
.vscode/
Section titled “.vscode/”Contains generated settings to help VS Code understand Luau types and Kaledis configuration.