Name & Ordinals - Sockets 101
How sockets and name-ordinal indexing works for quest and scene nodes
┌─────────────┐ ┌─────────────┐
│ Block A │────▶│ Block B │
│ │ │ │
│ OUT socket │ │ IN socket │
└─────────────┘ └─────────────┘🎬 Enter: Cut
In Cyberpunk:
Normal Story Flow:
V talks to Jackie ───▶ Jackie responds ───▶ Conversation continues
With a Cut:
V talks to Jackie ───▶ 💥 COMBAT STARTS! ───▶ Conversation STOPS
↑
Cut signal🔄 Two Types of Connections:
📬 Now, How Do We Address These Messages?
📝 The Address System:
🤔 But Here's the Tricky Part:
Think of it like this:
The Complete Socket Reference Table
Node Type
Connection Type
Name
Ordinal
Socket Index
Socket Name
Output Sockets (Both Types):
Node Type
Output Type
Name
Ordinal
Socket Index
🎨 ASCII Visual Guide
Quest Node Layout:
Scene Node Layout:
🔗 Connection Flow Examples
Normal Story Flow:
Cut/Interrupt Flow:
Mixed Example:
📋 Quick Reference for Modders
When Creating Connections:
⚠ Common Mistakes to Avoid
DON'T Mix Systems:
Remember the Rule:
Last updated