bitsquid_dt/dtmt
bitsquid_dt/dtmt
2
Fork 0
Code Issues 35 Pull requests 1 Projects 1 Releases 3 Packages 1 Wiki Activity
Var Dump: 
dumpVar: only available in dev mode
Mailing List

Update 'Migrating from loose files'

Lucas Schwiderski 2023-03-16 19:57:19 +01:00
parent 414aee7d40
commit c3826d710a
1 changed files with 6 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

8
Migrating-from-loose-files.md

@ -5,9 +5,13 @@ To migrate Lua files from a loose file structure to something that can be built
- a `dtmt.cfg` that defines the mod's metadata, entry points and packages - a `dtmt.cfg` that defines the mod's metadata, entry points and packages
- at least one `.package` file that includes your Lua files - at least one `.package` file that includes your Lua files
Check out the reference create your `dtmt.cfg`: [`dtmt.cfg` Reference](dtmt.cfg-Reference) One way to quickly generate a skeleton would be to use `dtmt new` in a new location as outlined in [Building your first mod](Building-your-first-mod), then moving files over from your old location.
The `resources` section can be adapted from the contents of your `.mod` file. All instances of `<id>` are intended to be replaced with the value you specify in `id = ""`, which must be the same value you pass to DMF's `new_mod` and `get_mod`. If you want to migrate manually, or need to edit things, read on:
To create your `dtmt.cfg` use the file reference at [`dtmt.cfg` Reference](dtmt.cfg-Reference).
The `resources` section can be adapted from the contents of your `.mod` file. The example uses `DMF` for the mod ID, wou'll want to use your own here, which must be the same value you pass to DMF's `new_mod` and `get_mod` in your code.
The `.package` file supports wildcards, so the most simple version would look like this: The `.package` file supports wildcards, so the most simple version would look like this: