The Third Go Battle Royale

I think the most I can do is to add point counters :grin: I’ll try.
If I fail, how about just counting points in the thread?

3 Likes

Point counters would make sense :slight_smile:

But yeah I think we can probably manage to add manual point counters along the way anyway :slight_smile:

1 Like

Hey everyone, I will out out of town from Wednesday to Sunday.

2 Likes

So are we waiting for more players? Or are we about to start

I vote we start

I withdraw my participation from the game.

How do we generate the random starting position?

I can do it when I get back in town

1 Like

Sorry for the inconvenience.

I wrote some code to generate random starting positions for the game, here is its first output:

image

Here is how it works:

Generate random row and column values for a potential move.
If the move hits any of these criteria:
a. It will be on the first line
b. It will be on top of an existing stone
c. It will be adjacent (straight line check only) to another stone
Throw away the entire board and start over.
Keep generating until we have 3 stones for each player.

Do we like the output?

4 Likes

Looks fine, but shouldn’t we assign colours first?

2 Likes

Then we’ll random it now :smile:

1 Like

I will add code to randomly assign the players to colors, just wanted to make sure everyone liked the output and did not want to change anything first.

1 Like

I added code to randomly assign users to the colors, here is the output:

image

I think I would like to add a criteria to make sure no two stones are diagonally adjacent to one another as well.

Edit:
I added the code to disallow diagonals, here is the output:
image

Which one would we like to start with?

2 Likes

Interesting idea to put it to a vote…

I can generate a new board after we make a decision so nobody is deciding based on the actual board. I am asking about methodology right now.

3 Likes

Oh okay, I was confused about that. I like the no-diagonals variant :slight_smile:

1 Like

I’m fine with either method :slight_smile:

I think either way is ok, but how about disallowing stones on the third line?

My code is flexible, so I can add anything you like, but we have to be careful about adding too much criteria so my code can find a solution in a reasonable number of tries.

When I added the criteria of no stones on the third line and kept the no diagonals rule, I let my code run through 350,000 iterations and it did not find a solution before I stopped it.

When I allowed diagonally adjacent moves, my code generated this output in 116,103 iterations:
image

I am going to let the code run with the no diagonals again to see if it generates an output.

2 Likes