|
|
%!s(int64=2) %!d(string=hai) anos | |
|---|---|---|
| .. | ||
| assets | %!s(int64=2) %!d(string=hai) anos | |
| docs | %!s(int64=2) %!d(string=hai) anos | |
| helpers | %!s(int64=2) %!d(string=hai) anos | |
| img | %!s(int64=2) %!d(string=hai) anos | |
| scenes | %!s(int64=2) %!d(string=hai) anos | |
| views | %!s(int64=2) %!d(string=hai) anos | |
| LICENSE | %!s(int64=2) %!d(string=hai) anos | |
| README.md | %!s(int64=2) %!d(string=hai) anos | |
| application.fam | %!s(int64=2) %!d(string=hai) anos | |
| minesweeper.c | %!s(int64=2) %!d(string=hai) anos | |
| minesweeper.h | %!s(int64=2) %!d(string=hai) anos | |
Hello!
git clone https://github.com/squee72564/F0_Minesweeper_Fap.gitufbt launch to compile and launch the app on your Flipper ZeroThe way I set the board up leaves the corners as safe starting positions!
In addition to this, with the "Ensure Solvable" option set to true, the board will always be solvable from 0,0! Without Ensure Solvable enabled in the settings the mine placement for the board generation is randomized and there is no guarantee that the game with be solvable without any guesses.
The following is the application structure with a breakdown of each folder:
minesweeper_scene.c, minesweeper_scene.h, and minesweeper_scene_config.h files to automate creation of scene FP arrays and Scene enumeration types. View the .README in this folder for more information on adding new scenes.Right now the current structure of the application is heavily inspired from leedave's boilerplate repo.