summaryrefslogtreecommitdiff
path: root/examples/readme.txt
diff options
context:
space:
mode:
authorHello=) <hello@themanaworld.org>2024-05-17 12:50:48 +0300
committerHello=) <hello@themanaworld.org>2024-05-17 12:50:48 +0300
commitac4306a8ca7267f6353d14bc39d7427e5167c492 (patch)
tree9db0a66a7411bed2c519bf787cd5ef01007b9f5e /examples/readme.txt
parent08cd08587be5c8d2ce42ae417098c524f683c6ad (diff)
downloadguildbot-master.tar.gz
guildbot-master.tar.bz2
guildbot-master.tar.xz
guildbot-master.zip
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
Diffstat (limited to 'examples/readme.txt')
-rw-r--r--examples/readme.txt13
1 files changed, 13 insertions, 0 deletions
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