From 090d77054c028d79c4413c265d0ed973753ea1af Mon Sep 17 00:00:00 2001
From: Lars Simon Winzer <lars.winzer@stud.unibas.ch>
Date: Thu, 19 Mar 2026 15:46:25 +0100
Subject: [PATCH] Add: Protocol schema modification template

---
 .gitlab/issue_templates/protocol_change.md | 42 ++++++++++++++++++++++
 1 file changed, 42 insertions(+)
 create mode 100644 .gitlab/issue_templates/protocol_change.md

diff --git a/.gitlab/issue_templates/protocol_change.md b/.gitlab/issue_templates/protocol_change.md
new file mode 100644
index 0000000..9846910
--- /dev/null
+++ b/.gitlab/issue_templates/protocol_change.md
@@ -0,0 +1,42 @@
+## Protocol / API Change
+
+### Summary
+<!-- Brief description of the protocol change -->
+
+### Affected Commands / Responses
+<!-- Which commands or response types are being added, changed, or removed? -->
+
+| Command | Response | Type of Change | Description |
+|---------|----------|----------------|-------------|
+|         |          | New / Changed / Removed | |
+
+### New / Changed Syntax
+```
+<!-- Before / after or new command syntax here -->
+<!-- Example:
+BEFORE: LOGIN UNAME=<username> PASS=<password>
+AFTER:  LOGIN USERNAME=<username> PASSWORD=<password>
+-->
+```
+
+### Affected Implementation Layers
+<!-- Which components / classes need to be updated? -->
+- [ ] `Session`
+- [ ] `User` or `UserRegistry`
+- [ ] `Tokenizer` / `RequestTokenClassifier`
+- [ ] `ProtocolParser`
+- [ ] `CommandParserDispatcher` + corresponding `CommandParser`
+- [ ] `CommandHandler`
+- [ ] `Response` hierarchy
+- [ ] `GameEngine` or `GameState`
+- [ ] Client-side (create your own issue and create link)
+
+### Migration Strategy
+<!-- If breaking change: how will migration be handled? -->
+
+### Motivation
+<!-- Why is this protocol change necessary? -->
+
+/label ~protocol
+
+/label ~server