This has been hinted by NetSysFire and makes some sense.HEADmaster

Add example of files guildbot uses, both online list and configuration,
giving guild captain level access to be able to control bot at all.

Bot wouldn't let unknown arbitrary nicknames to control itself,
only persons listed in guildmembers.txt with relevant access level
are allowed to control bot.

Reported-By: NetSysFire

3 files changed, 21 insertions, 0 deletions

diff --git a/examples/guildmembers.txt b/examples/guildmembers.txt
new file mode 100644
index 0000000..901ca5f
--- /dev/null
+++ b/examples/guildmembers.txt
@@ -0,0 +1 @@
+testchar,20,Crew of Red Corsair
\ No newline at end of file
diff --git a/examples/online.txt b/examples/online.txt
new file mode 100755
index 0000000..5a45844
--- /dev/null
+++ b/examples/online.txt
@@ -0,0 +1,7 @@
+Online Players on The Mana World (2024-03-24 22:59:22):
+
+Name                          
+------------------------------
+testchar                      
+
+1 users are online.
diff --git a/examples/readme.txt b/examples/readme.txt
new file mode 100644
index 0000000..3978154
--- /dev/null
+++ b/examples/readme.txt
@@ -0,0 +1,13 @@
+This directory contains example of guild save file and online list
+to help to get bot going on local test servers.
+
+Place these files in directory where bot's binary resides:
+guildmembers.txt
+online.txt
+
+Production server supposed to use guildmembers.txt to store guild
+membeship and online.txt is actual list of online players exposed
+by TMWA server.
+
+Example guildmembers.txt sets testchar as captain (lv 20) of 
+Crew of Red Corsair guild (same guild as in real TMW)
\ No newline at end of file