Hello everyone,
I’d love to propose a feature or share an idea around improving modularity in Wire patches.
One of the things I find myself doing often is reusing the same patching patterns across different projects or even within a single patch. Currently, this can get quite messy—especially as patches grow in complexity and layers of logic stack up. What I’d love to see is the ability to create a custom reusable sub-patch, similar to a library component, that acts like a single node.
Concept:
- A new patch type—something like “Wire Library Component”
- It would:
- Accept various data types as inputs
- Output a desired data type (or multiple outputs)
- Behave exactly like a native Wire node/component
- Be saved as a separate patch and instanced inside other patches
If I improve or fix logic inside this custom module, every patch using it would update automatically. This would make complex logic much easier to organize, maintain, and share with others.
Here’s a simple example of a pattern I created recently that I’d love to reuse—but if I copy/paste it into multiple places, it quickly becomes hard to manage:
Benefits:
- Cleaner, more readable patches
- Easier maintenance and iteration
- Encourages modular design
- Faster development workflows
- Opens the door for user-shared utility modules
And if the devs see this—could something like this be possible?
Thanks,
Ben