[Computer-go] CGOS Dropped Connections - Two automatic losses on time.

Don Dailey dailey.don at gmail.com
Tue Nov 9 15:59:55 PST 2010

I think you are slightly misunderstanding the suffix idea.

When you create a bot,  you always choose the name and password.   If one is
already taken of course you have to choose a different one.  This does not

The suffix idea is that if your bot ends with ",c",  where the c is any
legal character,  then any bot with the same prefix (the part before the
comma)  is treated as if it were the same player when it comes to rating the
games.    One the bayeselo page there will only be a single entry  that
represent ALL the players with the same "base" name.

The password however is one that you must create - only 1 user controls 1
name and there is no sharing of password.    If you have a bot called
"joebot,5"  then you own it and nobody else can run that name.    However
someone else can create "joebot,6" and it is understood that they are
"functional clones" of each other.

The primary issue is who gets to decide what the suffix is.   Without any
changes to the server other than allowing comma's,  I could just let this be
up to the users and if the name is taken you have to try a different name.
I would also change the server to only allow comma as the second to the last
character in the name.   That is the simplest thing to do.

Another possibility is to require these names to be registered - in which
case you cannot use a comma style name unless it has been approved by some
administrative process.     This is slightly more work for everybody,  but
has the advantage that this does not get out of control.   With no control
it is likely we will have a proliferation of comma-bots.     On the other
hand,  I'm not so sure this is a bad thing.   Imagine that you want to get
your bot rated in a big hurry and want to run 8 copies of it on an 8 core
machine.    You could easily do such a thing with this system.

I hate to mention this,  but this probably will lead to scheduling issues.
If there are a bunch of clones playing each other, it is meaningless
rating-wise.   So they probably should not be allowed to play each other.
It may cause some clones to have to sit out rounds if there are too many of


On Tue, Nov 9, 2010 at 4:39 PM, Robert Finking <robertfinkng555 at o2.co.uk>wrote:

> Hi
> On 09/11/2010 12:26, Don Dailey wrote:
>> On Tue, Nov 9, 2010 at 12:10 AM, Michael Williams <
>> michaelwilliams75 at gmail.com <mailto:michaelwilliams75 at gmail.com>> wrote:
>>    > It's a nice approach - simple and effective - but needs
>>    safeguards I think. If two people are using the standard engine pack,
>>    > the second person who comes along will boot the first off the
>>    server.
>>    Wouldn't they be using different engine names and passwords?  If they
>>    use the engine pack out of the box without customizing the name and
>>    password then it's their fault if they get booted.
>> Yes,  the idea is not to share an account but for the server to somehow
>> recognize them as standard players.
>>  I think I missed a step in my explanation. I am trying to get back to the
> original suggestions on this topic  of using a single digit numeric suffix.
> This uses the mechanism already built into the client - thanks Don =) -
> which allows you to specify multiple alternative logins in the same config
> file. Each engine picks a suffix at random. There are three advantages to
> this:
>   * it satisfies those who wanted a single digit suffix
>   * it solves the problem with Mogo needing restarting
>   * suffixes get selected automatically - this means the end users
>     don't need to grab a suffix which is then solely used by then
> Of course this relies on their being a standard shared password. If however
> you would prefer to stick with the one-suffix-per-user, I agree that the
> "2nd login causes boot" is a simple and effective solution, especially when
> combined with the other ideas!
> So, shall I move back to the beta2 suffix (set by the user in the
> suffixes.txt file) so that we can go with the suggested approach?
> Kind regards
> Raffles
>>    _______________________________________________
>>    Computer-go mailing list
>>    Computer-go at dvandva.org <mailto:Computer-go at dvandva.org>
>>    http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
>> _______________________________________________
>> Computer-go mailing list
>> Computer-go at dvandva.org
>> http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
> _______________________________________________
> Computer-go mailing list
> Computer-go at dvandva.org
> http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://computer-go.org/pipermail/computer-go/attachments/20101109/c814f93f/attachment.html>

More information about the Computer-go mailing list