|
|
@@ -31,7 +31,9 @@ To have the engine load such a collection dynamically, we can simply add a colle
|
|
|
|
|
|
This is done by simply checking the *Exclude* checkbox in the collection proxy properties, telling the bundler to leave any content in *monalisa.collection* out when creating an application bundle.
|
|
|
|
|
|
-Note that any resources referenced by the base game package, will not be excluded.
|
|
|
+::: important
|
|
|
+Any resources referenced by the base game package, will not be excluded.
|
|
|
+:::
|
|
|
|
|
|
|
|
|
|
|
|
@@ -51,7 +53,9 @@ There are currently two ways that Defold can store the resources. Choose the met
|
|
|
|
|
|
## Bundling with Live update
|
|
|
|
|
|
-_NOTE:_ Currently, the editor `Build & Run` does not support Live Update. Thus this bundling step is required for testing.
|
|
|
+::: important
|
|
|
+Building and running from the editor (<kbd>Project ▸ Build</kbd>) does not support Live Update. In order to test Live Update you need to bundle the project.
|
|
|
+:::
|
|
|
|
|
|
To bundle with Live update is easy. Select <kbd>Project ▸ Bundle ▸ ...</kbd> and then the platform you want to create an application bundle for. This opens the bundling dialog:
|
|
|
|
|
|
@@ -94,8 +98,9 @@ The engine doesn't keep a reference to any resource in a mount. Once a resource
|
|
|
|
|
|
The mounts are automatically readded upon engine restart.
|
|
|
|
|
|
-_NOTE:_ Mounting an archive doesn't copy or move the archive. The engine only stores the path to the archive.
|
|
|
-Thus, the developer can remove the archive at any time, and the mount will also be removed at next startup.
|
|
|
+::: sidenote
|
|
|
+Mounting an archive doesn't copy or move the archive. The engine only stores the path to the archive. Thus, the developer can remove the archive at any time, and the mount will also be removed at next startup.
|
|
|
+:::
|
|
|
|
|
|
## Scripting with Live Update
|
|
|
|
Björn Ritzl