From 21a5a8c9d1d84188f99a371bb3139a8b07f868e0 Mon Sep 17 00:00:00 2001
From: C4 <29991504+TheIllusiveC4@users.noreply.github.com>
Date: Wed, 6 Dec 2023 15:41:59 -0800
Subject: [PATCH] Clarify operation in slot registration

---
 docs/curios/slot-register.md | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/docs/curios/slot-register.md b/docs/curios/slot-register.md
index 775a841..ad1a8ef 100644
--- a/docs/curios/slot-register.md
+++ b/docs/curios/slot-register.md
@@ -53,6 +53,15 @@ related to that slot type.
 | `use_native_gui` | boolean                      | `true`                          | `false`  | When `false`, does not add the slot type to the native Curios GUI                                                    | `false` if any do not use the native GUI    |
 | `render_toggle`  | boolean                      | `true`                          | `false`  | When `false`, does not allow the slot type to toggle its rendering                                                   | `false` if any do not allow render toggling |
 
+:::info
+**Which `operation` value should I use?**
+
+In most cases, `"SET"` (also the default if no value is defined) will accomplish the desired result. It denotes that a
+slot type should have a certain amount of slots by default, with the highest value among all consumers being used.
+`"ADD"`and `"REMOVE"` are inherent slot modifiers and are based on the amount of slots specified by all `"SET"`
+operations, the result of which can change based on the mods/datapacks loaded.
+:::
+
 ## Example
 ---
 ```json