1) COMMON : MESSAGE OGS MODERATORS
2) COMMON : GENERATE THE APIKEY
- 3A1) Download and install nodejs and npm
- 3A2) Install gtp2ogs.js with npm
- 3A3) Recommended : Upgrade gtp2ogs.js from old branch to “devel” branch (latest)
- 3A4) Optional : Edit the gtp2ogs.js file (for example show winrate on OGS)
- 3A5) Run gtp2ogs.js (beta)
- 3A6) Run gtp2ogs.js (official)
- 3B1a) Preparations
- 3B1b) Download and install nodejs
- 3B2) Install gtp2ogs.js
- 3B3) Recommended : Upgrade gtp2ogs from old branch to devel (latest) branch
- 3B4) Optional : Edit the gtp2ogs.js file (for example show winrate on OGS)
- 3B5) Run gtp2ogs.js (beta)
- 3B6) Run gtp2ogs.js (official)
If you're a user, you can use another branch than the default gtp2ogs devel or latest release by copy pasting another branch and overwriting existing files.
You can skip the rest of the page: Next Page ->
You can tweak gtp2ogs to behave as you intend, preferably in a new branch.
You can skip to Next Page -> or read the example if you're curious:
Below you will find a historical example before the --komis option existed, to workaround bots that only support komi 7.5 (PhoenixGo).
For example my AI cannot play a game if the komi is set to another value
than 7.5 (for example 6.5 , 0.5 , 85.5 220.5, etc) , it gives the error
message ? unacceptable komi.
To avoid that, since there is no --komis argument in gtp2ogs.js that would
reject games without the wanted komi (would be 7.5 for me), then a trick is
to lie to the AI, telling it that all games are played with a komi of 7.5
even if it’s not true :
The endgame scoring may become wrong because the AI is playing as if komi was 7.5 while it’s not always true, but this is not a problem in unranked games because most games end by resign.
In gtp2ogs.js (now moved to game.js):
i replaced this.command("komi " + state.komi);
With this.command("komi " + 7.5);
This is just an example