Now after all the complicated mechanics in a lot of the earlier version lets go back to a regular 10 by 10 board with 17 mines hidden. This should be a rather simple version nothing that could make this a challenge.

However, you may have noticed that there isn't only a grid here, but there are connections between the tiles. These connections (edges) between the tiles (nodes) indicate how the numbers work. Instead of each node counting the mines on the 8 nodes around it, it counts the mines below the nodes it is connected with.

If you are playing with a mouse, hovering it over a node will highlight its edges. You can only click on nodes, clicking on edges or on the background won't do anything. If you play on a mobile device, the last note you have interacted with gets highlighted. Besides that this version works just like any other Minesveeper.

Welcome back!

If you haven't noticed yet, this is what Graphsveeper is actually about. The previous version was there to introduce the mechanic of playing on nodes that are connected by edges. However now the nodes are no longer neatly organized, but are randomly placed. So now you will have to play on a random much more chaotic graph.

Due to this not scaling up very well, there are only 80 nodes here. Making this the smallest Minesveeper so far, if you are not counting custom versions where you can create smaller boards.

Now why would I create something like this?
When you play Minesweeper (the regular one, not any complicated extra mechanics) you will eventually get to the point where playing the game becomes more about recognizing certain patterns. A bunch of them were shown on day 2 of the advent calendar last year. So I like to do stuff that will stop you from playing the game without having to think much about what you are doing for the most parts.
Like adding a sheep so that you can no longer dig up every tile that isn't a mine the moment you find it.
The Zen Garden was an attempt to create a situation where not every tile gives you the same type of information.

And now there is Graphsveeper, where the nodes and edges are random each time. This can also result in the difficulty largely varying between different attempts.

Welcome to third Graphsveeper,
this time the graph was some more nodes than on the previous version and the nodes generate in a way where they are split up in a top and bottom half with a gap in the middle. Edges through that gap are a bit more chaotic than between the dense nodes on either side.

Would there have been a better thing to do for this version?
Probably
Was this the only setting I tried for this version?
No
I actually tried a few different settings for this. But it turns out that it is quite hard to create settings that work well with this. Because situations where you have to guess, get quite common in a lot of settings. Maybe I'll revisit Graphsveeper if I at some point make a generator to create games that can be solved without guessing. Otherwise, if you want to try some specific settings, you can just download this.

The ZIP-files contains the files for these three days and also a template for just a single day. This is located in the directory reupload. So if you want to create a modified version of graphsveeper you can do it in this template and upload it however you want as long as a reference to the original is kept.

For the template the generator that specifies the amount of nodes and mines is defined at the top of graphsveeper.js, the three generators used for version 33 to 35 are defined in the three files dayGen_[number]_[letters].js. Each generator consists of the following parameters:

Two other things that might be important:

You might have to do some changes in settings.js if you want to have more than 126 nodes, I recommend to not set the value to some much higher value then needed. Increasing this value at all will cause Graphsveeper to break on Chrome, however on Firefox this will only fail at 2048 or higher. And make sure to adjust the size of the board accordingly since otherwise the nodes might not be able to generate.

Also, the textures do not get loaded from the image TilesRound_8x8.png, but instead from b64.js which contains the image converted to Base64. This is to prevent an issue with WebGL.

So what next?
As of now I have plans for what I want to do up to around Version 42, next should be a group of 5. Otherwise, I am also working on a smaller puzzle game which I will release once I have a few more levels for it. Probably still this year.

So I hope to see you again for whatever is next.
And thanks for playing!