From 7245e06afc1816a82f4dd08ea80311ff63dd31c0 Mon Sep 17 00:00:00 2001
From: neifion-00000000 <91289495+neifion-00000000@users.noreply.github.com>
Date: Sat, 1 Apr 2023 04:59:24 -0500
Subject: added clarity to groupID definition (#889)

group 0 does not apply, so added >0
---
 docs/loot_template.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'docs')

diff --git a/docs/loot_template.md b/docs/loot_template.md
index b240730..3bf1543 100644
--- a/docs/loot_template.md
+++ b/docs/loot_template.md
@@ -140,7 +140,7 @@ Loot mode examples from the Flame Leviathan fight in Ulduar:
 
 ### GroupId
 
-A group is a set of loot definitions processed in such a way that at any given looting event the loot generated can receive only 1 (or none) [item](#item) from the items declared in the loot definitions of the group. Groups are formed by loot definitions having the same values of [entry](#entry) and **GroupId** fields.
+A group is a set of loot definitions processed in such a way that at any given looting event the loot generated can receive only 1 (or none) [item](#item) from the items declared in the loot definitions of the group. Groups are formed by loot definitions having the same values of [entry](#entry) and **GroupId > 0** fields.
 
 A group may consists of **explicitly-chanced** (having non-zero [Chance](#chance)) and **equal-chanced** ([Chance](#chance) = 0) entries. Every *equal-chanced* entry of a group is considered having such a chance that:
 
-- 
cgit