Object Gpencil Modifier Move Down

Object_GpencilModifierMoveDown nudges a grease pencil modifier one slot down the stack. Grease pencil modifiers, like mesh modifiers, evaluate in order, and that order decides the final look: a GP_NOISE run before a GP_SMOOTH gives you wobbly-but-smoothed strokes, while the reverse gives you smooth-then-wobbly. Order is half the battle, and this node is one half of the reordering tool - its sibling Object_GpencilModifierMoveUp does the opposite.

When you'd reach for it

You'll hit it most often after a copy or an add. Object_GpencilModifierCopy dumps the duplicate at the bottom of the stack, which is rarely where you want it. Object_GpencilModifierAdd appends wherever the stack currently ends. So the typical sequence is: add or copy a modifier, then walk it into position with move-up/move-down, or jump it straight there with Object_GpencilModifierMoveToIndex. If you're fine-tuning the stack order one slot at a time, this is the node.

How it works

Thin auto-generated wrapper over bpy.ops.object.gpencil_modifier_move_down. It makes your BPY_OBJ active, moves the named modifier down by one position, and passes the object back through. Inputs:

• BPY_OBJ (optional) - the grease pencil object.
• modifier (STRING, default empty) - the name of the modifier to move.

Output: BPY_OBJ, the same object, with the stack reordered.

The naming problem, again

Every node in this family addresses modifiers by name, and this one is the most punishing about it, because moving the wrong modifier is a silent mistake - the stack just isn't what you expected. Blender's auto-naming (copy creates Name.001) makes it worse: if you copied GP_Noise and want to move the copy, you must type GP_Noise.001. There's no dropdown and no list node in the pack, so either keep deliberate names or check the object's modifier list in a debug output before wiring this in.

One more thing to know: moving a modifier to the top or bottom of the stack when it's already there is a no-op - the node succeeds, nothing visibly changes. That's normal, not a bug.

Install and gotchas

Standard pack install:

cd ComfyUI/custom_nodes
git clone https://github.com/avatechai/avatar-graph-comfyui.git
cd avatar-graph-comfyui && python -m pip install -r requirements.txt

or ComfyUI Manager → "Avatar Graph". House rules: Python 3.10 for bpy==3.6.0, ~2.5GB SAM checkpoint + mediapipe models on first load, scene resets every run (so stack order is rebuilt fresh each execution), and --enable-cors-header for live preview.

Object_GpencilModifierMoveDown is a small, precise tool. It won't do much alone - but stack order is the difference between "this looks great" and "why is this jitter applied after the smoothing," and this node is how you fix the latter.