Yotsuba Games
Back to Node List

Patch Merge

patch_merge

Merge two patch documents, letting the overlay win on conflicts

Reviewed
Guide available
The node name and summary are available in English. Port, parameter, and article details are currently shown in Japanese.

Input Ports

NameTypeDescription
ベース
base
PixelPatch
δΈ‹εœ°γ«γͺるパッチ document
δΈŠζ›Έγ
overlay
PixelPatch
δΈŠγ‹γ‚‰ι‡γ­γ‚‹γƒ‘γƒƒγƒ document

Output Ports

NameTypeDescription
パッチ
patch
PixelPatch
η΅εˆζΈˆγΏγƒ‘γƒƒγƒ document

What is it for?

  • Keeping patches separate by purpose and combining them later
  • Layering an additional correction over a base correction
  • Gathering multiple PixelPatch values into one

Overview

Combines two patches into one. At overlapping coordinates, the overlay input takes priority. Merge patches separated by purpose, such as outline corrections and color corrections, before applying them.

Usage tips

  • A clean structure is to edit patches by purpose, merge them at the end, then connect to patch_apply. Place patch_toggle on individual branches to toggle each correction separately.
  • This also merges an automatic difference from image_manual_diff with a hand-drawn pixel_patch.

Related nodes

  • pixel_patch / image_manual_diff β€” supply patches to combine
  • patch_apply β€” applies the combined patch
  • patch_toggle β€” toggles individual patches

Notes

  • When both patches write the same coordinate, overlay wins.
  • If both patches include target dimensions, their dimensions must match.
  • If only one input is connected, it passes through unchanged.

Examples

  1. Pixel Patch A.patch + Pixel Patch B.patch -> PatchMerge -> PatchApply
    • Edit manual corrections separately, then combine them.
  2. ImageManualDiff.patch + Pixel Patch.patch -> PatchMerge
    • Merge an automatically extracted difference with a hand-drawn patch.
Back to Node List
Patch Merge β€” PixPipeline Node Reference