Just wanted to add that as the person that originally developed the octoprint plugin and did the initial work for Marlin, I really appreciate the systematic way this has been approached in RRF and documented in this thread. Well done. Now, to "standardize" where to put those object labels relative to wipes/retractions....

@t3p3tony I had brainstormed a bit on how to avoid pausing. It would be possible to have a comment/command that would provide the number of lines to skip ahead, something like M486 Q1652. Downside is that it would require either the slicer or some post processing to insert them.

@t3p3tony I had brainstormed a bit on how to avoid pausing. It would be possible to have a comment/command that would provide the number of lines to skip ahead, something like M486 Q1652. Downside is that it would require either the slicer or some post processing to insert them.

I was thinking more in terms of what a slicer considers to be an object. Right now PrusaSlicer/SuperSlicer already have "; stop printing objectX" tags that can be used for termination as you suggest. But as of right now post-object wipes are not considered part of the object, they come after the stop printing comments. This wastes time and movement. Cura uses NONMESH object tags which work fine. However, it defines all supports as NONMESH and not as parts of objects, so you can never cancel the supports along with the individual object.

Just wanted to add that as the person that originally developed the octoprint plugin and did the initial work for Marlin, I really appreciate the systematic way this has been approached in RRF and documented in this thread. Well done. Now, to "standardize" where to put those object labels relative to wipes/retractions....