MMU Usefulness killing modifier bug in Slicer  

MMU Usefulness killing modifier bug in Slicer

Modifiers are forcing unwanted color changes on geometry in Slicer 2.3.x (and likely most versions prior).

Any geometry either manually added in slicer, or brought in with the model import, when changed to type modifier, forces a color change on the rest of the model for the area it occupies, even though it's no longer a "printing" object.  This utterly destroys the ability to use the MMU's multi material capability if you have to have modifiers for any reason.   See Below:

So here's a model brought in via 3MF, manually renamed item by painful item (as Slicer utterly ignores whatever parts model names that had been assigned in the modeler before exporting to 3MF, another PITA Bug).   Note the two green blocks that were built in the modeler, had type changed to Modifier.

And here we can see the two blocks have had speed modifiers added.

And here we can see it's for the most part having the intended effect on the speed locally around the logo artwork.

However when I switch to Color  Print we see this:

The modifier has stomped on the real geometry's color assignment.   This is also viewable in tool view as well:

Is this just a slicer bug or does it actually force MMU filament changes in those areas as well in the GCode?  

I've opened a bug report on this 2 weeks ago but it hasn't even had a single look.   I was told filing bug reports in GitHub was the way to get stuff in the queue for fixes, but maybe not.  

Github Bug Report

Is there a workaround for this?   I'm using modeled in modifiers more and more to solve various printing issues so I don't have to baby-sit the prints by hand, but this kinna wrecks' havoc on the ability to use an MMU.