In the Hangman game, the new using syntax won't dispose of the object until the end of the current scope. So, the using statements need to be wrapped in a nested scope so they are only open during the initial load.

In the Tanks game, If the enemies move up against the walls and shoot, the bullet goes through the walls. I probably forgot to check if a bullet hits a wall when it spawns.

Helicopter is one of the older games and I never coded it properly to reducing the amount of flickering that happens. It should not flicker like it currently does.

Currently the process of porting console to blazor webassembly is a manual process. For the most part you just copy-paste the console code into the Website project and add public readonly BlazorConsole Console = new(); and await in front of the Console member invocations. This should be easy to make a code generator for.

If there are any changes to the console games, it requires the same change be applied to the ports. However, if the ports were generated, we could just make any changes to the original console games and the generator would carry over any changes to the ports automatically.

A source generator would be good for this topic. :)

MazeGenerator would be a really cool example...

I think that this could be used to create highway skeletons which can therein be physically lamented from the manifestation.

Simple case; I want to have a wooden version of my maze in 3d form with all sides connection to each other, I design a maze generator with the astute bias and utilize such seed to ensure the vectors conjugate about points which traverse the sides, this in short would probably just be rotations of a single generated matrix such that its end points may be allows to traverse around the side dimensions (maybe in also).

I would generate my maze, produce a WKT / Store it in a DB, send the WKT for conversion to GCODE and print it out.

Other case; I want to design a highway or city, I need to create the maze of the city such that the maze of the highway fits inside it, perhaps I want to also include utilities etc.

I would then lament the WKT / Store it in a DB and project such on a map for viewing (potentially in MVT / GeoJson /TopoJson) allowing me to view my city at scale in the real world.

Thank you for your library sir from its contents and your demeanor I can tell you are satoshi (聡)!

P.s. using libraries like NTS/Itinero it would be possible to have it traverse your mazes and find the shortest solutions from any given point to another (including the exit or the non traversable spot in an island of such)

See also https://en.wikipedia.org/wiki/Labyrinth

One type of thing I muse is a type of Maze which is a fractal, it is created in a likeness and then zoomed upon for arbitrary derivatives thus never having to ge-generate the maze again only refine its details...

Some of the games in the Website project require rapid pressing of the buttons, however double tapping screens often causes zoom in/out. So the zooming caused by double tapping needs to be prevented. This is especially a problem for the Bound game.

Since this repository is meant to help C# beginners setting foot in the programming world, I think it would be good to show some best practices and enforce them for contributors.

Currently, the .editorconfig file in the root directory is not even part of the solution. I'm not sure Visual Studio (or other IDEs) pick up on its rules as it stands.

I'm suggesting adding all .NET- and C#-specific rules and enforcing them in a way which is closest to the .NET standard. This way, new coders will learn good convention the moment they set foot into this repository. I'm happy to do this myself (I already have a complete .editorconfig file lying around).

https://zacharypatten.github.io/dotnet-console-games/Wordle

The font is set to monospace but is not monospace on android Chrome and Edge browsers. Not sure if this is something that should be fixed in our code, or something that really should be fixed in android's browsers.

The 76ffc9f commit was necessary because there is a bug dotnet/runtime#86379 when publishing with PublishTrimmed. Once that bug is resolved in a newer version of .NET 7+ then 76ffc9f can be removed.

The Gravity game has 15 levels at the moment. It would be nice to add more.

Some possible ideas:

• Levels with multiple player blobs. You would have to get each blob to the goal or perhaps separate/multiple goals.
• Levels that are not stationary. Perhaps the goal moves around. Maybe spikes appear/disappear or move around.
• Keys that make walls/doors open allowing access to the goal.

I forgot to add the down arrow button on the blazor port of Yatzee. That needs to be added for when you are selecting which row in the scorecard to use.

The Bound game has 12 levels at the moment. It would be nice to add more.

In the Console Monsters project we need additional ascii art for monsters, maps, characters, items, etc. If possible, it would be nice if the ascii art would complement the current art style. Here are some examples of existing assets in the game (note that these may not render correctly on mobile browsers; viewing via desktop is recommended):

Characters...

 ╭═══╮ 
 │'_'│ 
╭╰───╯╮
│├───┤│
 │_|_│ 

 ╭───╮ 
 ├■_■┤ 
╭╰───╯╮
╰├───┤╯
 │_|_│ 

////\\\
//^_^\\
╭┴───┴╮
│├───┤│
 │_|_│ 

Map Tiles...

 ┬──┬─┐
╭┴──┴╮│
│Sign││
╰────╯│
      │

       
       
╦═════╦
╬═════╬
╩     ╩

  ╬╬╬  
 ╬╬╬╬╬ 
  ╬╬╬  
 _|_|_ 
 \___/ 

╔═════╗
║ ■■■ ║
║    o║
║     ║
╚═════╝

                       
 ║        @╮         ║ 
 ║    ╭═╨──∏──╨═╮    ║ 
 ╠══╗ ╰────╥────╯ ╔══╣ 
 ╨  ╨      ╨      ╨  ╨ 

Items...

       
 ╭───╮ 
 ╞═●═╡ 
 ╰───╯ 
       

Monsters...

╰╮             
╰╮╰╮      ╭───╮
╰╮╰╮╰╮    │^_^│
   ╰╮╰────╯  ╭╯
    ╰┬╮ ╭─┬╮ │ 
     ╰╰─╯ ╰╰─╯ 

 ╭───╮ 
 │^_^│ 
 │   │ 
 │   │ 
─┴───┴─

    ╭─────╮    
 (O)│ ‾o‾ │(O) 
╭─╨─╯╔═══╗╰─╨─╮
│ ╭╮╔╝   ╚╗╭╮ │
╰─╯╔╝     ╚╗╰─╯
   ╚╗     ╔╝   
  ╭╯╚╗   ╔╝╰╮  
  │ ╭╚═══╝╮ │  
  ╰─╯     ╰─╯  

           ╭────╮
           │ ^_^│
╭───╮ ╭───╮╰─╮╭─╯
││‾││_││‾││__││  
╰╯ ╰───╯ ╰────╯  

     \~\~\~|~/~/~/     
      \ ╭─────╮ /      
┌─┐ ┌──\│ o_o │/──┐ ┌─┐
  └─┘ ╭─╰─────╯─╮ └─┘  
      │ ╭─────╮ │      
      ╰─╯─╯ ╰─╰─╯      

 /\                  
/~~\  <‾__>╭───╮<__‾>
\   \      │^_^│     
 \___>╭────╯~~┬╯     
      │ ╭┬──╮ ││     
      ╰─╯╯  ╰─╯╯     

    ╭◦╮    
    /◦\    
╭─◦╯^_^╰◦─╮
╰◦╮◦ ◦ ◦╭◦╯
  /◦/‾\◦\  
 ╰◦╯   ╰◦╯ 

    ╭─┬──┬─╮
◦╮╭◦├ ╭─┴╮ ┤
╭┴┴─┼ ╰┬ ├ │
│^_^╰┬┼─┬╯ ┤
╰┬┬┬┬┴─┴─┴─╯

  ╭─────╮     
  │ ⱺ_ⱺ │     
╭─╰─┤ ├─╯─╮  
│ ╷╭┤ ├╮╷ │  
╰─╯││ ││╰─╯╭╮
 ╭╯╰┤ ├╯╰╮─╯│
 │ ╭┤ ├╮ ├──╯
 ╰─╯│ │╰─╯   
    │ │      
    ╯─╰      

   ╮╭    
  ╭/╰╮   
  │ⱺⱺ├<> 
  ╰╮/╯   
 <>┤│    
─^─┴┴^─^─

  ╭──╮╭──╮ 
 ╭┴─╭ⱺⱺ╮─┴╮
 ╰┬─╰─○╯─┬╯
  ╰┬┬╯╰──╯ 
   │├<>    
 <>┤│      
   ││      
─^─┴┴^─^─  

◄‾_>╭─────╮<_‾►  
    │▪^_^▪│      
    │╷╭─╮╷│      
    ├╯╰─╯╰┤◄/\/\>
    ╰─╯‾╰─╯      

        ◦╮ ╭◦       
  /‾‾‾\ ╭┴─┴╮ /‾‾‾\ 
 / ( ( >│^_^│< ) ) \
 \/\/\/ ╰┬─┬╯ \/\/\/
         │ │        
         ╹ ╹        

   ╭─────╮
   │ ‾o‾ │
 ╭─╰─────╯─╮
 │o╷╭───╮╷o│
 ╰═╯│^_^│╰═╯
 ╭╯ ┼┬─┬┼ ╰╮
 │  ╰╯ ╰╯  ├──╮
 │o╭─────╮o├──╯
 ╰═╯     ╰═╯

         ╭─╮
         │^╰─╮
    ╭─╮  │ ╭─╯
╭╭──╯~╰──╯ │
╯│        ╭╯
 │╭┬────┬╮│
 │││    │││
 ╰╯╯    ╰╰╯

           ╰╮╰╮
  ╰╮╰╮╰╮     /^╰─╮
  ╰╮╰╮╰╮╰╮╰╮/ /‾‾
   ╰/‾‾‾‾‾‾  /
    │\ \──┬\ \
    ││//  ││//
    ┕┙˅   ┕┙˅

╔═╭─────╮═╗
╔═│╭───╮│═╗
╔═╰│^ ^│╯═╗
   ╰╥═╥╯
    ╰ ╯

        //
        ││<>
/‾‾‾\╭──╯╰──╮
\___/│ o  O │/‾‾‾\
     │╭════╮│\___/
     ╰╰════╯╯

 _╭─────╮_
//│ ^_^ │\\
//╰╥───╥╯\\
  ╰‾╯ ╰‾╯

   ╭───╮
   │^_^│
  ╭╰───╯─╮
  │╭╮╭╮╭╮│
  ││││││││
  ╰╰╰╯╰╯╯╯

The current version of the code including all ascii art is in the console-monsters branch. If you would like to help out, please join the discord server to discuss. :)

How can you make ascii art? Just open a text editor and start. :) A useful tool is the "Character Map" application in Windows. It can help you find characters you need:

However, please stick to the "Consolas" font. Different fonts support different characters, but we are limiting our characters to what is seen in the "Consolas" font. In the website we are actually using the "Source Code Pro" font, but that is because it is very similar to "Consolas".

There is a minor bug in the randomized maze generator in the game Maze where it is possible for an invalid path to not be connected to a connected path.

• remove "(work in progress)" from Bound page in Website header
• remove "(work in progress)" from Bound page in launch.json
• reorder Bound in launch.json to match readme order
• Role Playing Game says "You were attacked, but..." instead of "You attacked, but..."

Thanks In Advance

Contributions are welcome and appreciated! :) If you write a .NET console game and would be willing to contribute it just fork the repo, add your game, and open a pull request. Your game will be marked with *Community Contribution to credit you for your contribution.

Brainstorming

Here are some ideas for games that dotnet-console-games does not have yet:

• Rubix Cube
• Chess
• Solitaire
• Match 3 Puzzle
• Tower Defense _{like Plants Vs Zombies}
• I Love Hue
• Vicious Fishes
• Virtual Pet _{like Digimon}
• Scrabble
• Red Light Green Light
• Roguelike _{like Vampire Survivors}
• Top Down Action Adventure _{like The Legend of Zelda}
• Side Scrolling Run & Gun _{like Metal Slug}

New Game Contribution Checklist

Here is a checklist of files that need to be updated when a new game is added. The maintainer(s) of this repository can help you with these topics after you open a pull request. <GAMENAME> is the name of the game being added.

1. Projects/<GAMENAME> game source code here
   • Projects/<GAMENAME>/README.md don't forget a readme
2. README.md add a row in the table
3. dotnet-console-games-and-website.sln add project to solution
4. dotnet-console-games.slnf add project to solution filters
5. .vscode/tasks.json add a build task for the project
6. .vscode/launch.json add a launch entry for the game
7. .github/workflows/<GAMENAME>.yml add a GitHub Action
8. Projects/Website/... (multiple files) add the game to the website _{(currently a manual process but see #23)}

Name goes through outline edge

The navigation bar is being cut off under certain conditions:

An easy way to replicate is to zoom in on the web page.

The nav bar needs to be fixed so that it never cuts off and all links are always visible.

Some of the readme links in the website are incorrect. Oops... I'll fix them as soon as I can.

Blinking of NPC's
Grass/Tree's (Nature) moving
Etc...

The banner image on the readme and website home page could use some improvement. If anyone is willing to make a nicer one I would appreciate it. It would be especially cool if it was animated and showcased more of the games.

Current Banner File: https://github.com/ZacharyPatten/dotnet-console-games/blob/main/.github/resources/banner1.png

https://github.com/ZacharyPatten/dotnet-console-games/blob/e998d81effeba1f1fc85bba1920fb23f1494aba1/README.md?plain=1#L1

Currently the Minesweeper game has a bug so you can't win. It checks to see if all the tiles are visible, and if yes, it declares victory. However that includes mines, and revealing mines is the lose condition. So... The win condition needs to be changed to count the number of visible tiles, and if that count equals width * height - mineCount the player wins.

https://zacharypatten.github.io/dotnet-console-games/Draw

The game buttons in the Website project are currently just slapped on without much thought. This makes the games pretty hard and annoying to play on mobile or any platform where the user can't use a keyboard. It would be nice to improve the button layout for every game to make it more sensible.

For example, in the Draw game from the screenshot above, the end key restarts the game with new random generation, but the end key is next to the right arrow key, making it easy to accidentally bump the end key when trying to draw to the right. Something like this might be better for the Draw game:

I'm open to ideas. Each game has different buttons, so there they will all require slightly different button layouts, but it would be nice to keep the button layouts as consistent as possible between the games.

Not all the games are compatible out-of-the-box on Linux (they compile but some Console methods are not supported). Need to test and adjust accordingly or document incompatibilities in the individual README files.

The default maze generation algorithm includes a using directive DebugRandomMazeGeneration that allows people to watch the building of the maze step-by-step with a Console.ReadLine() after each node exploration. It would be nice to add this using directive to the Prims algorithm too. @HurricanKai

If your code makes heavy use of the Console class (which I suspect will be most games here, if not all), you can make method calls a little leaner by including:

using static System.Console;

This would reduce code like this:

Console.WriteLine("Dice Game");
Console.WriteLine();
Console.WriteLine("In this game you and a computer Rival will play 10 rounds");
Console.WriteLine("where you will each roll a 6-sided dice, and the player");
Console.WriteLine("with the highest dice value will win the round. The player");
Console.WriteLine("who wins the most rounds wins the game. Good luck!");
Console.WriteLine();
Console.Write("Press any key to start...");
Console.ReadKey(true);
Console.WriteLine();
Console.WriteLine();

To:

WriteLine("Dice Game");
WriteLine();
WriteLine("In this game you and a computer Rival will play 10 rounds");
WriteLine("where you will each roll a 6-sided dice, and the player");
WriteLine("with the highest dice value will win the round. The player");
WriteLine("who wins the most rounds wins the game. Good luck!");
WriteLine();
Write("Press any key to start...");
ReadKey(true);
WriteLine();
WriteLine();

https://zacharypatten.github.io/dotnet-console-games/Role%20Playing%20Game

The console needs to scale based on width so that it is not cut off on mobile and small width views. This issue exists for all the games, not just the one linked above.