Procházet zdrojové kódy

Mention variant information in bundle hooks

Vlad Protsenko před 5 roky
rodič
revize
fd84180385
1 změnil soubory, kde provedl 1 přidání a 0 odebrání
  1. 1 0
      docs/en/manuals/editor-scripts.md

+ 1 - 0
docs/en/manuals/editor-scripts.md

@@ -190,6 +190,7 @@ Existing lifecycle hooks that `/hooks.editor_script` may specify:
 - `on_bundle_started(opts)` — executed when you create a bundle or Build HTML5 version of a game. As with `on_build_started`, changes triggered by this hook will appear in a bundle, and errors will abort a bundle. `opts` will have these keys:
   - `output_directory` — a file path pointing to a directory with bundle output, for example `"/path/to/project/build/default/__htmlLaunchDir"`
   - `platform` — platform the game is bundled for. See a list of possible platform values in [Bob manual](/manuals/bob).
+  - `variant` — bundle variant, either `"debug"`, `"release"` or `"headless"`
 - `on_bundle_finished(opts)` — executed when bundle is finished, be it successful or not. `opts` is a table with the same data as `opts` in `on_bundle_started`, plus `success` key indicating whether build is successful.
 - `on_target_launched(opts)` — executed when user launched a game and it successfully started. `opts` contains an `url` key pointing to a launched engine service, for example, `"http://127.0.0.1:35405"`
 - `on_target_terminated(opts)` — executed when launched game is closed, has same opts as `on_target_launched`