Again this one is another customization day, where you get to make your own setting. If you are familiar with Minesveeper 61, this shouldn't be anything new. While there are some differences resulting from the different mechanics, the way this one work is mostly the same. But if you aren't familiar with 61, how do you get started making your own setting?

There are 3 menus for this day.
Play lets you try out the custom setting that you've made.
Edit gives you a bunch of options for how you can adjust the settings.
Json lets you edit the JSON Data for the setting you are making. This is a less user friendly way to edit the settings, but can in some situations be more powerful. When you want to make something that the regular editor doesn't have an explicit option for.

Once you are happy with your setting you can request a share link, this will upload the settings and give you a link directing to those settings, so other people can play them.
For more detailed instructions on how to use the editor as well as some tips how you can replicate mechanics from other days, not available as options you can check the Editor Guide.

And so we've reached the end of this miniseries.
I have so more ideas for other miniseries I might make in the future. As of now I do not wish to make any prommise on when those may happen. I don't even know in which order I want to tackle those ideas.

Like before here is the download for the code so you can modify this as you like. I have prepared to separate Downloads based on what files you want. First off is a smaller template you can use for coding your own setting and re-uploading it wherever you'd like. In addition if you want to check the files for this page with all of the days you can play here as well as many other files you can download the full package instead. This also comes with many off the textures as png files and various utility scripts I used while working on the advent calendar.

You may use these however you like for any non-commercial purpose as long as credit is given to this game.

Getting Started
For most cases I would recommend using the Reupload Template. Here you can unzip the files and open index.html with a browser of your choice and that's it you are now playing this custom setting locally. To modify it you can edit js/mySettings.js if you are familiar with the JSON representation for custom settings you will be at a significant advantage, if not it may be helpful to check how this works with Minesveeper 75 as well as checking the Editor Guide. So what's new? Before you could use "copyFrom" instructions to use special features from some days. However, now you can freely code your own functions here. To see how they work you can check the individual implementations of the days in the full version with all files. Here is a quick overview of which functions can easily be set in the custom settings.

Of course since you have access to the code of the game you can modify whatever default behavior you'd like.

Technical differences to the 2023 version:
In the past these functions took both the tile and its coordinates. Some now only take the tile, however each tile object now also contains its own coordinates. While this is fairly minor technical change, I am pointing this out as it may likely brack these functions if you just copy them over from the 2023 version directly without updating them accordingly.

The game also no longer uses rejection sampling to place mines and instead assigns a random number to each tile, sorts them and places mines beneath them in order or skips them if the placement is excluded. The distribution of these random numbers is chosen in a way that this system produces an equivalent behavior as the previous ones. While only considering every tile at most once, allowing an easy detection for the mine placement failing once all tiles have been considered, without having placed all mines.

Decrementing is not supported by this version.

Adding Your Own Textures
Some ideas might require you to create your own textures or modify existing textures. All game textures are included as png files with the full download. In most cases where you just want to add a new texture you can just add an extra line of code to load it. However, if you want to modify existing textures, you should know that those aren't loaded from the png files.
Instead they are encoded as Base64 (with some extra replacements for common character sequences) in js/b64.js. I would recommend to not manually add textures to this file and instead generate this file with the provided scripts. Simply modify images/textureList to include your new textures and use the python script images/MakeB64.py to generate a new version of js/b64.js. Encoding images as Base64 in a script files avoids having to load a large amount of individual files. It also allows accessing image data within the code for local testing. Where loading images from local png files would prevent accessing image data in some browsers.

Have Fun!
I'm curious to see what mechanics people will come up with using this.

When you play a custom setting by someone, which has not been specifically approved by me. You will receive a warning about unreviewed user submitted content. If you accept any potential risks that come with that you can disable this warning with this option.