add docs

Author: makspll

.luarc.json

@@ -1,7 +1,7 @@
 {
     "$schema": "https://raw.githubusercontent.com/LuaLS/vscode-lua/master/setting/schema.json",
     "workspace.library": [
-        "assets"
+        "assets/definitions"
     ],
     "runtime.version": "Lua 5.4",
     "hint.enable": false,

docs/src/SUMMARY.md

@@ -12,6 +12,11 @@
 - [Callbacks](./Summary/callbacks.md)
 - [Script Systems](./ScriptSystems/introduction.md)
 - [Examples](./Examples/introduction.md)
+- [Scripting IDE Integrations](./ScriptTooling/summary.md)
+
+# Script Tooling
+
+- [Ladfiles](./ScriptTooling/summary.md)
 
 # Script Pipeline
 

docs/src/ScriptTooling/summary.md

@@ -0,0 +1,51 @@
+## Ladfiles
+BMS provides a custom Language Agnostic Declaration format (LAD), which can be used to integrate with other tooling.
+
+If you use `#[script_bindings]` macros, these files will magically contain your code comments, bindings as well as everything else required to drive other powerful integrations.
+
+The declaration file is generated from the type registry and serves as a light abstraction layer simplifying the traversal of all 
+available types and globals as well as functions.
+
+You can customize how / where and if these files are stored using the main BMS plugin group:
+```rust,ignore
+    app.add_plugins(BMSPlugin.set::<ScriptingFilesGenerationPlugin>(
+        ScriptingFilesGenerationPlugin::new(
+            true, // enabled, you can use a compilation feature to disable this here
+            PathBuf::from("assets").join("definitions"),
+            Some(PathBuf::from("bindings.lad.json")), // do also save the ladfile itself
+            "Core BMS framework bindings",
+            true,
+            true,
+        ),
+    ));
+```
+
+This plugin is only available when one of the sub features (like `lua_language_server_files`) mentioned in this chapter is enabled.
+
+
+You might not want to run this pipeline in your final binary, but rather bundle some of the generated files into some sort of development pack for modding. You can use compiler flags like `#[cfg(not(debug_assertions))]` to disable ladfile generation at runtime, or simply disable the lower level features within BMS to avoid compiling related dependencies too.
+
+## Lua Language Server
+
+<div class="Warning">
+    This feature is in early stages, the definitions provide 90% of the way there, but there are rough edges that will need to be worked out
+</div>
+
+[Luals](https://github.com/LuaLS/lua-language-server) or LLS, is an open source language server which integrates with many IDE's.
+
+It is powered by lua specific annotation or definition files which BMS can generate directly from its own LADfiles.
+
+To enable this simply enable the `lua_language_server_files` feature, and a `bindings.lua` definition file will be generated in the LADfile output directory in the `Startup` schedule.
+
+Script writers can then use this generated file by pointing their `.luarc.json` file to these definitions:
+```json
+{
+    "$schema": "https://raw.githubusercontent.com/LuaLS/vscode-lua/master/setting/schema.json",
+    "workspace.library": [
+        "assets/definitions"
+    ],
+    "runtime.version": "Lua 5.4",
+    "hint.enable": false,
+}
+```
+

docs/src/Summary/scripting-ide-integrations.md

@@ -0,0 +1,3 @@
+# Scripting IDE Integrations
+
+See the [script tooling](../ScriptTooling/summary.md) section to find out more about how BMS integrates with other tooling to make scripting easier.