procedural_generation_godot VS gruid-rltuto

I took a step back and finished Kidscancode tutorial on Dungeon Procedural Generation on Godot - I think /u/usami33 might be on a similar path (there are links for the youtube videos on the readme of this repo https://github.com/johnnybigoode/procedural_generation_godot)

In the end, I'm a bit behind on the schedule with gruid-rltuto, because I did not have much time lately, but I plan on finish the remaining 2-3 parts in the following weeks, as soon as I have some time.

Well, I had little time for coding last week, so less progress than expected for gruid-rltuto : I only finished Part 10 just now. Saving and loading was actually quite easy because of standard library gob package, which allowed for automatic serialization of all the game data.

Parts 6 and 7 of gruid-rltuto for Go are done. There were some little refactorings, but no big deals with these two parts. When creating the interface, I went with a more traditional look (keeping the 80x24 dimensions), because of personal preference, but it's easy to change this. I did implement monster examination like in the Python tutorial, using the mouse, leaving implementation of a keyboard examination mode to the reader :-)

Parts 4 and 5 of the gruid-rltuto in Go are ready! There's nothing really special to tell about them: I followed the Python tutorial closely enough, except for superficial things (like graphical representation of terrain, fov and entities) and language-related stuff (OO in Python is quite different than in Go). The FOV algorithm I used is symmetric shadow casting as implemented in gruid.

This weeks' parts 2 and 3 are ready in the gruid-rltuto version of the tutorial in Go.

BTW, you may already be aware of it, but I'm doing a roguelike tutorial, though using SDL2 as default driver, but you might still find it useful to get started on non driver-specific stuff.

If anyone is interested in doing the tutorial in Go, you may want to have a look at the gruid-rltuto repository: I'm making the tutorial in Go following the overall structure of the tcod tutorial.