summaryrefslogtreecommitdiff
path: root/docs/dev/plugins.md
diff options
context:
space:
mode:
authorJordan Wiens <jordan@psifertex.com>2024-02-26 15:38:45 -0500
committerJordan Wiens <jordan@psifertex.com>2024-02-26 15:38:45 -0500
commitbe6d9389670c931fae1fc5c58a847da51ffa1c93 (patch)
tree6c72bf62ac1d9e9e9837701ca58219e276476e34 /docs/dev/plugins.md
parent86686b2901cba24a10fe77f570ad91a222b859a8 (diff)
add warning around improtlib in terms of which plugins dont work with it
Diffstat (limited to 'docs/dev/plugins.md')
-rw-r--r--docs/dev/plugins.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/dev/plugins.md b/docs/dev/plugins.md
index f489f94b..53a1dd87 100644
--- a/docs/dev/plugins.md
+++ b/docs/dev/plugins.md
@@ -35,6 +35,8 @@ The [`add_repository`](https://api.binary.ninja/binaryninja.pluginmanager-module
It's useful to be able to reload your plugin during testing. On the Commercial edition of Binary Ninja, this is easily accomplished with a stand-alone headless install using `import binaryninja` after [installing the API](https://github.com/Vector35/binaryninja-api/blob/dev/scripts/install_api.py). (install_api.py is included in each platforms respective [installation folder](../guide/index.md#binary-path))
+Additionally, some plugin types like Architectures or BinaryViews are only loaded at launch and cannot be reloaded during a running session.
+
For other plugins, we recommend the following workflow from the scripting console which enables easy iteration and testing:
```python