From c3826d710ae7b080f4e648b3228578b015220c30 Mon Sep 17 00:00:00 2001 From: Lucas Schwiderski Date: Thu, 16 Mar 2023 19:57:19 +0100 Subject: [PATCH] Update 'Migrating from loose files' --- Migrating-from-loose-files.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/Migrating-from-loose-files.md b/Migrating-from-loose-files.md index 811c792..e563223 100644 --- a/Migrating-from-loose-files.md +++ b/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 - 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 `` 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: