About ModlQ
Sheet A-000 · Revision schedule
The problem
Every BIM team ends up with the same pile of one-off macros and half-finished Dynamo graphs for the tasks Revit itself doesn't handle well — renumbering grids, fixing wall joins, batch-creating sheets from a spreadsheet, auditing shared coordinates before a federated model goes out.
Sound familiar?
The build
So ModlQ packages those fixes as real, tested plugins instead — built against the actual Revit API, every change wrapped in a single transaction you can undo, sharing one license system and one dark dialog theme underneath.
HighlightWalls/Command.cs
var color = function switch
{
WallFunction.Interior => InteriorColor,
WallFunction.Exterior => ExteriorColor,
_ => OtherColor,
};
view.SetElementOverrides(wall.Id,
new OverrideGraphicSettings()
.SetProjectionLineColor(color));Today
That approach is still how every new plugin gets built. The catalog keeps growing; the ribbon tab, license system, and dialog theme underneath it don't change shape to fit each new tool — the tool fits the shape.
75
Plugins
12
Categories
2024–26
Revit versions
Every discipline, one model
Structure, MEP, and architecture built by different teams, meant to line up perfectly — which is exactly what ModlQ's Coordination & Collaboration tools check for.
What we believe
How we build
Built against the actual RevitAPI/RevitAPIUI assemblies for each supported year, not a scripting layer on top.
Step 01
Every command wraps its changes in one Revit transaction, so it's always a single undo away from gone.
Step 02
Every plugin actually compiles against the real Revit API on every push, across every supported year, before it ships.
Step 03
One shared license and update system covers the whole catalog — no per-plugin account to manage.
Step 04
ModlQ is built by a small team of BIM specialists and developers who'd rather ship a working tool than write another wiki page explaining a workaround.