Linked & Reusable Snippets with Automatic Sync#590

Snippets are a great way to improve print automation, but right now they don’t stay linked once they are added. As soon as a snippet is inserted and saved, it becomes static code and is no longer a snippet. This makes it hard to maintain reusable logic across multiple printers.

A common use case is having a special farmloop or push-off G-code script that applies to certain prints. Ideally, this logic could live in a single reusable snippet and be referenced by multiple printers or print profiles. When the snippet is updated, all printers using it should automatically receive the change.

The current workaround is to build large scripts with complex if/else logic based on printer or model, but these quickly become hard to read, maintain, and scale.

It would be very useful to support linked or synchronized snippets that remain references instead of being inlined. Editing the original snippet should propagate changes everywhere it’s used, with an optional way to detach it if local customization is needed. This would greatly improve maintainability, reuse, and scalability for print farms.

Additionally, mistakes caused by snippets being out of sync are not just simple errors. Incorrect or outdated G-code can easily damage a printer, destroy a print bed, or ruin valuable parts. In a print farm environment, a single unsynchronized change can become very expensive very quickly, which makes reliable, centrally managed snippets even more critical.