From c95b6d8d0ad88cd89029d1e14c9376ff4ed03a4b Mon Sep 17 00:00:00 2001 From: Jonathan Arndt Date: Fri, 23 May 2025 08:44:16 -0700 Subject: [PATCH] Update architecture drawing for Plugin load sequence. --- Plugins.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Plugins.md b/Plugins.md index c6791e7..6b1681c 100644 --- a/Plugins.md +++ b/Plugins.md @@ -22,7 +22,7 @@ Essentials is meant to be a lightweight framework and an extensible basis for de One or more plugins can be loaded to the /user/ProgramX/plugins as .dlls or .cplz packages. When the Essentials Application starts, it looks for any .cplz files, unzips them and then iterates any .dll assemblies in that folder and loads them. Once the plugin assemblies are loaded the Essentials Application will then attempt to load a configuration file and construct items as defined in the file. Those items can be defined in either the Essentials Framework or in any of the loaded plugin assemblies. -![Architecture drawing](https://pepperdash.github.io/Essentials/Essentials%20Plugin%20Loading%20Sequence.png) +![Architecture drawing](https://pepperdash.github.io/Essentials/docs/images/Plugin%20Load%20Sequence.png) ## What Must be Implemented in a Plugin for it to Work?