AutomationForgePipelines
Every released version of AutomationForgePipelines, newest first. Latest 0.1.1.
AutomationForgePipelines0.1.1Free, closed source
| Set | AutomationForge |
| Role | addon |
| Latest | 0.1.1 — 8 September 2026 |
| Versions here | 2 |
| Depends on | AutomationForge |
0.1.x
0.1.1
8 September 2026 · Download (763 KB) · Release on GitHub
- Packaging fix: the release now carries everything the register allows.
BuildPlugin's filter excludesConfig/and everypublic_extrapath, so earlier zips shipped without them.
0.1.0
28 August 2026 · Download (759 KB) · Release on GitHub
- A pipeline that runs from data, and a register of what is still wrong
- Keys come from named fields, and a bad one is refused before it runs
- A pipeline you can open and edit, and the parent survives its own expansion
- A second run does no work, which was the whole point
- Scope is not optional, and a filter is how you say it
- Refuse to write over something we did not make
- A pipeline an agent can write without a graph existing
- Wires decide the order, so the graph can branch and rejoin
- Nodes somebody else writes, in C++ or in Blueprint
- A run that outlives the call that started it
- The wait, proven against a solve that really takes minutes
- A pipeline you can open, wire, and now edit
- Left to right, and a graph you can actually run from
- A gate: the one construct that is not about data
- Output paths belong to the pipeline, not the project
- The hands Kimodo never generated, and a gate that can test a number
- Wires you can see, undo on the keyboard, and assets you pick
- A details panel you can fill in, and nodes with names
- Readable node titles, and a handoff
- A run that reported success while doing the wrong thing
- A step needs what a step needs, and not twenty other things
- Runs you can look at, and the decisions a gate is waiting for
- Cost before commit, for real this time