Socket Overview

Mantis rigging nodes utilizes many of the same standards as Blender's other node editing workspaces in terms of color choice for data types and connection types via shapes. For the sake of a comprehensive guide, the following list will quickly cover the color coordination of datatypes and shapes used in Mantis Rigging Node sockets and any conflicts between the two, using the same color descriptions as used by Blender's documentation:

• Matrix: Sea Green (Conflict)

Matrix socket has the same color as Blender's geometry socket

• xForm/object: Orange
• Relationship: Forest Green
• Deformer: Dark Blue
• Geometry: Dark Green (Conflict)

The color of the geometry socket does not match the color of the geometry socket found in geometry nodes

• Driver: Magenta (Potential Conflict)

The driver socket is barely different from the shader node texture socket.

• Driver Variable: Dark Orange
• fCurve: Yellow (Internal Conflict)

The fCurve socket shares the same color as the custom color set socket which can be confusing

• Collections: White
• Boolean: Black (Conflict)

The color of the boolean socket not only doesnt match Blender's standard, the black color of the socket wire is easy to lose in the dark background of the editor

• Boolean Vector: Dark Brown
• Integer: Lime Green
• String: Grey (Internal and External conflict)

Not only does the color of the string socket match the curve node socket, it also doesn't match the color of the geometry node's socket

• Custom Color Set: Yellow (Potential Conflict)

while probably not a problem, this is more of a color vector data type as it stores 3 seperate colors, and not just one singular color like the standard color datatype

• Curve: Grey (Internal Conflict)

Im not sure if curves are being treated like an object/xform, or they should have their own distinct color socket from them, but ehy probably shouldn't be grey

• Morph Target: Deep Orange
• Float: Light Grey
• Vector: Slate Blue
• Keyframe: Azure blue

---

Next: Node Function Overview