-
Notifications
You must be signed in to change notification settings - Fork 0
/
readme.txt
executable file
·167 lines (127 loc) · 5.3 KB
/
readme.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
*** REQUIREMENTS ***
OS:
However MatchDogServer is written completely in Java and is a console program (without GUI),
it has only been tested in a bash shell of a Debain Linux box. It will probably run in other
Linux distributions and it will most likekly NOT run in MS Windows (cmd.exe).
Java:
I used the 1.6 update 3 release of the JDK to write and test the program.
It will probably also work with any 1.5 release of JRE but has not been tested with any earlier release.
Telnet:
MatchDogServer should be able to run telnet binary specified in
the PROGRAM PARAMETERS section of the file 'MatchDogServer.java'.
GNU Backgammon:
In order to successfully run the program you should be able to run gnubg.
MatchDogServer should run gnubg with '-q -t' options (silent, no gui), give
full path to the binary in the PROGRAM PARAMETERES section.
MatchDogServer should be able to open and also to connect
to a socket on on the localhost on the port number specified
in the PROGRAM PARAMETERS section of the file 'MatchDogServer.java'.
FIBS:
The players must use the following 'toggle' settings
to work correctly with MatchDog:
allowpip YES
autoboard YES
autodouble NO
automove NO
bell NO
crawford YES
double NO
greedy NO
moreboards YES
moves NO
notify YES
ratings YES
ready YES
report YES
silent NO
telnet YES
wrap NO
*** SETUP ***
NOTE!
First, some program parameters and at least one user must be set up
in the file 'MatchDogServer.java' before compilation and run.
See comments for the first five variables at the very beginning of the file.
See comment for user preferences setup in the same file.
Also, for the the 'show log' function to work the first five
variables in the included ftpupload.sh file need to be set.
*** COMPILE ***
One way to compile the sources on a Linux a system is to
change directory to the 'bin' folder of the 'MatchDogServer'
folder (or create it if necessary) and issue the following
three commands in a bash shell (assuming that the java
binaries are on the path):
$> javac -d . ../src/jcons/src/com/meyling/console/*.java
$> javac -d . ../src/etc/TorExitNodeChecker.java
$> javac -d . ../src/matchdog/*.java
Make sure files compile without errors. Ignore 'Notes' from jcons.
*** USAGE ***
On a Linux a system, change directory to the 'bin' folder
of the 'MatchDogServer' foldel where the compiled java .class
files are located and issue the following command in a bash shell
(assuming that the java binaries are on the path):
$> java matchdog/MatchDogServer [n]
where [n] is the index number of the player preferences object
in the 'players' map in the file 'MatchDogServer.java'.
There must be at least one user preferences object instantiated
and put in the 'players' map at index 0.
If no command line parameter is given or not a number is given
or there is no user preferences object at that index of the
'players' map, the default user at index 0 is used.
*** FEATURES ***
* several preconfigured users can be stored
* select user with command line argument
* autologin option
* keep track of saved games
* resume saved matches
* a list of 5 preferred players and match lengths
* crawford rule handling
* separate user settings (true or false) for:
- automatically invite preferred players
- automatically invite players when they log in if there is a saved match
- automatically join an invitation for a saved match
- automatically join an invitation
(if this is true, then opponent experence
and reputation is considered before joining)
* opponent experience divider
the followin must be true to join:
[match length] < [opponent experience] / [opponent experience divider]
* opponent reputation limit
the opponent's reputation reported by RepBot must be
greater than this limit
* manual (runtime) switching of a number of settings currently including:
- autojoin, autoinvite, crawford
* option to send commands to fibs/gnubg/gnubg socket from command line
* timeout for inactivity
* player statistics - keeps logs of all matches, dropped ones
* statistics writer - write to stdout or file
* statistics uploader - upload stat file to ftp server and send url to requester
* player statistics files automtically uploaded to a ftp server on user request
-----
* preconfigurable user preferences include settings for:
- fibs user name and password
- a list of 5 preferred players (opponents on fibs)
- autologin to fibs
- maximum match length (when accepting invitations)
- autoinvite preferred players
- autoinvite for saved matches
- autojoin for saved mathces
- autojoin
- match lenght points opponent experience
(i.e match length should be less then opp. exp. / this integer)
- reputation limit (under which invitation is rejected)
- gnubg checkquer play ply
- gnubg cube decision ply
- gnubg noise
- gnubg movefilters
#gnubg settings on commandline
set threads 8
set eval sameasanalysis off
set evaluation chequer eval plies 3
set evaluation cubedecision eval plies 3
set evaluation movefilter 1 0 0 16 0.320
set evaluation movefilter 2 0 0 16 0.320
set evaluation movefilter 3 0 0 16 0.320
set evaluation movefilter 3 2 0 4 0.080
set evaluation movefilter 4 0 0 16 0.320
set evaluation movefilter 4 2 0 4 0.080
external localhost:xxxx