Thanks for sharing. It's really interesting to see how you're fairing after 6 months and I hope you're able to make it work!

Hello can you make a video about the environment like rain, sun, snow?

I would be interested in a video on the sound manager.

same, i love coding on scratch

Im not sure if you have made a video like this already but it would definitely help me if you did your roadmap to learning godot. The resources, videos, which order and things like that which could help me and others learn what we need to learn in godot

This was an excellent video. I've been a professional developer for over 30 years, though never a game dev (yet!). This stuff really resonated with me. I have a library of useful code that I include in most of my projects, honed from my experience. And the advice to just try something and learn from it is spot on. Dev is something you learn by doing, so when it doubt, write some code and learn from it. Also - Hexagod looks l like fun, but I only see a Windows version of the demo. Do you have plans for Mac support?

Tons of AI image generation models are trained ethically just like that music model. Just has a bad reputation due to open source models

Not sure if that's already to complex, but there could very rarely spawn a city with which you can trade. Also the citys could provide quests. You can even combine that with enemies. Enemies are going for citys and you have to defend them with your villagers. This would create some tricky situations e.g. there's a city pretty far from you, but gives you some passive bonuses, will you defend that city from enemies? Or will you be the city raider and raid the city?

An interesting watch. Gave me some encouragement for my own plans. Good luck and look forward to seeing you make it.

Hi! Thanks for the awesome contents. I was wondering if and how you collect data during the testing phase of your games? And if you could make a video on this topic.

Are you inventing Civilization from scratch?

i would love an in depth ENUM tutorial

What about natural disasters instead? I worry that combat will angle this into an RTS game. But you follow your gut!

Awesome video, I am new to godot and didnt know about autoloads!

I like the idea that He Is Coming brought to the table and used a periodic force to push against. Random boss every so often that you know what it is and have a way to prepare for it.

Could you have some cards that act as a barrage of arrows or magic spells, that you could drag over enemies when you feel overwhelmed? If it was something rare, or expensive to make, it could be kinda fun to have that direct control with your UI setup

It's coming along really well! I played it early on and enjoyed it so far, but since there wasn't much to do after getting the basics down, I'm simply waiting for more to be added. I'm also trying to develop a game myself (thank you for your tutorial videos) and I relate that it's hard, but I really like the direction you're going and admire the progress you've made -- it has a lot of potential and a nice art style, so keep at it!

Admittedly I only played it once, but I can see why you want something to add pressure to the game. Currently I won with ease by simply having the first villager do basically everything until I had a ton of food. Then having enough Favor for the packs that had tiles that gave me victory points was trivial. Maybe I got lucky but the demons never dealt enough damage to be scary nor have a need for a second villager to take over. If you expand it, the pressure could help me prove to be more time efficient and getting that second villager online sooner even if it's risky resource wise. The item/role thing also seems like a step in the right direction. I see a lot of potential for longer games, especially if you add in different victory conditions (think scenarios). The game also runs really smoothly, which is nice for the simplistic style. I do feel like the UI kind of blends together though, I'm not a UX guy so I'm not sure what to say to that. Took me a bit longer than I care to admit that the length of the day was at the bottom in the middle. The only one I can say for sure is that it wasn't clear to me what the Ritual card was giving me, I did eventually realize it was Favor but I thought it was six tiles at first. The hex that gives Favor has the same icon, so maybe that's on me. I also feel like Tile placement didn't matter that much, which is kind of uninteresting. Also as a side note: your help menu for instructions has a typo that says were building a Villager out of VILLAGERS, instead of a Village. Funny image of the villagers coming together to form one mega villager though. I'll be keeping an eye on this one and your channel. Hopefully this feedback is helpful, I know I can be a bit wordy.

P.s. UI/UX is like saying Engine/Driving. I know some companies have used this in their job postings, but UX is a psychological approach to designing software that utilizes Human Computer Interaction, UI is just the thing that a UX person is typically editing to improve that experience. There's a lot of things that we can do to improve the UX of something that are unrelated to UI.

I like the idea of an end boss that spawns after a certain amount of time, and you have to use all your villagers/weapons to defeat it. It gives you a goal that you're constantly working towards.

How did you code the Debug Tool? Is it just a UI thing with control nodes in Godot? When I did UI for testing in C++ I used Imgui, but asking what is the typical thing to do in Godot.

Bro. this game needs a lot of learning to have an advantage in the game, can you simplify it coz iyohh 🤯😫

I appreciate your videos and how honest you are about the honestly shitty parts of gamedev (not here in particular but in general), it feels really good to be able to relate to someone with more experience

I just tried the demo, was pretty fun👍, found a bug when I placed a villager just before the day ended and he died even though I had more than enough food, I reckon delaying the death function till after you click "feed villagers" would fix this and also tighten the game loop since I didn't like that the villagers die instantly at the end of the day if you don't have enough food, it turn an "oh I guess I didn't have enough food.." to an "WHICH ONE OF YOU WILL STARVE!!".

Villager classes open up a whole extra layer of gameplay. How many other villager types were you thinking? I propose: trader villagers that connect to a randrom group of 'other village' tiles. Similar to combat, devote one trader for each other village tile for economic victory.

is it true that using scripts can be dangerous (like collecting data)? then maybe they should check and collect the verified safe ones in a single website

Pls provide a tutorial 😢

So this game is basically stacklands but you build the map. I love it

The first thing that popped into my head when you said that the food problem of the game is done after a few villagers, is to have either some random events in the game where maybe a tile is having harsh weather which cripples the gathering modifier, much like Stellaris do it. Or, since the player is the god (I think?) perhaps you are forced to use cards that are in fact negative for the game. Frostpunk style, where you have to choose between two bad options and part of the game is to prepare for those bad options. I haven’t played your game, so I’m not sure if you can have several villagers on the same slot to gather faster, but with penalties it might be a good idea to spread out harvesting on several tiles even if the max number of villagers on them isn’t reached. Just brainstorming here, perhaps you already have these kind of things in the game 😂

i mean if you are working as a solo dev on a project there is way less use for the branching in git makes sense, still could be useful but only in specific things and no need for all the time

I would suggest Pixelorama. It's a great option over aseprite

This was a great video. Usually gamedev content creators recommended the same programs over and over (aseprite, GIMP, Inkspace, Krita) but you threw in a lot of interesting stuff there. Zapsplat and soundraw could be very good tools for me.

It's not normally my type of game, but the concept is exciting, and I'm currently playing the demo, and I'm enjoying being inspired by the mechanics. The combat mechanics sound exciting and engaging. Definitely on the Steam Wish list, keep it up.

First thing I thought of was making it so that assigning 1 villager to a demon would "hold" it. Like it would put the 2 into a combat that neither could win, a stalemate. Then a 2nd villager would be required to kill 1 demon. Giving the player the choice to hold back the problem or to use more resources to deal with it. It could also create natural defensive lines. Just my thoughts.

I can see why this is a complex problem, but I think combat adds a lot to the game!

So do think combat will combat ruin Hexagod? Please help me out by playing the demo (combat patch should be live by the end of today): store.steampowered.com/app/3059390/Hexagod/

Your disrespect for GitHub decorum and etiquette is highly respectable, have a round of applause

*The cat tho*

Your "stuff" is my "misc". Nice video :)

Ill play your games if you play mine 😘 Jk lol, just found your channel! Definitely earned a sub 🙏

this is sooooo interesting, thank you for the video

So can you make games with the Godot Web version because I only have an iPad Pro with Apple Pencil 2ndGen and the typecase and an iPhone, I model in Blockbench and Sprite in Pixquare. Godot’s web version looks to be the current version

That GitHub segment is utterly painful to watch. If you intend to do game development professionally, never do that "stuff" thing. Here are some of the key benefits of using a clean, readable and clear commit messages: - Improved Clarity: Descriptive commit messages make it easier for you to understand the purpose of each change, reducing confusion OVER TIME. - Better Collaboration: Maybe since your the only one working on those project, you don't mind not sharing what has changed. But it's a good practice in addition to all the other benefits I'm listing here. - Easier Debugging: When debugging, clear commit messages allow you to pinpoint when a bug was introduced, making it easier to trace back and fix problems. It is not necessarily strictly a question of being able to revert. I can help you identify when a bug was introduced and why (not just because stuff). - Enhanced Documentation: Your commit history acts as a form of documentation for your project, detailing the evolution of features and bug fixes over time. Eventually you will want to publish changelogs to your released steam games. Commits can help you with that. - Simplified Maintenance: Projects with clean histories are easier to maintain over time, as future developers (including yourself) can understand the history of changes without needing to decipher vague messages. - Better Issue Tracking: When you reference issue numbers in commit messages, it creates a direct link between code changes and the problems they address, enhancing traceability.

Small note, Aseprite is free if u compile it yourself. Give it a try!