Dev-Blog

The Beginning In the first week, we formed our development group. The team consists of 10 people, each with the following roles: Team Members & Roles Kuba - Project Director / Generalist Caoimhe - Story Writing Shay (Me) - Programming / Game Design Leo - Programming / Game Design / UI/UX Pedro - Programming / Generalist Misha - Programming / Sound Design Adam - Generalist / Art Work Cian - Generalist / Art Work Piraka - Art Work Lucretia - Sound Design Collaboration & Tools We are using Figma Whiteboard to collaborate and share ideas, and GitHub for version control. ...

The Beginning The second week focused on fleshing out our game ideas, with my specific responsibility being project structure and version control. Based on my past experiences in other development fields and some guidance from the Godot documentation, I settled on the following structure: . ├── assets │ ├── audio │ │ ├── effects │ │ └── music │ ├── fonts │ ├── sprites │ │ ├── characters │ │ ├── items │ │ └── tiles │ └── ui ├── config │ ├── data │ └── settings ├── docs ├── export │ ├── builds │ └── logs ├── scenes │ ├── characters │ ├── effects │ ├── items │ ├── levels │ ├── main │ └── ui ├── scripts │ ├── characters │ ├── global │ ├── items │ ├── levels │ ├── ui │ └── utils │ └── async └── tests └── commits I also set up a GitHub workflow that automatically creates a backup branch, always one commit behind the main branch. I’ve also enabled branch protection, requiring all commits to go through the dev branch first. Merging into production now requires approval from two other team members. ...

This week was mostly about reviewing ideas and deciding which ones were feasible and easy to implement. A big part of our discussions focused on game progression and how we’ll handle level design. Level Implementation Plan For now, we’re sticking with premade levels contained within a single scene. This keeps things simple and lets us focus on refining gameplay and balancing progression. If we have enough time later, we’ll look into adding procedural generation to mix things up. ...

Moving to GDScript This week, we made a big decision to switch from C# to GDScript. The main reason? The lack of resources and support for C# in Godot was slowing us down. While C# has its benefits, we realized that sticking with it would mean spending way too much time troubleshooting instead of actually developing the game. GDScript, on the other hand, has a ton of community support, better documentation, and is just more in sync with how Godot is designed to work. ...

Art Direction Meeting Week 5 was on the quieter side overall. We had jone team meeting this week, which was mostly focused on the art direction for the project. We spent some time talking through the visual style we’re aiming for, as well as how to keep things cohesive across different assets. A few early ideas are starting to take shape, and it’s good to see the creative vision starting to come together. ...

Art work! week 6 consisted of implimenting the art to replace our placeholder assets. i also worked on again refining the code provided by pedro and misha to be more clear and consise.

midterms took up a majority of the time so we didnt get much done.

Ranged Weapon Fixes Week 8 was pretty productive. I spent most of it working with Pedro and Misha on fixing the ranged weapon implementation. There were a bunch of little issues that needed ironing out, but we managed to get everything working a lot more smoothly by the end of the week. Group Presentation We also had our group presentation, which I think went really well. We each put in work on it and covered our parts, and it came together nicely. ...

UI Refinement Week 9 was focused on refining the user interface and adding some core gameplay features. I spent the week on the UI originally made by leo — improving layout, consistency, and making sure everything feels clean and functional. Health Bar System I also added a health bar system to track and display the player’s health, and it took me way longer than expected due to how we designed our health system. eventually i got it to work, and now it updates real time to display the current health of the player. ...

Quality of Life Settings Week 10 involved implimenting quality of life settings, we implemented a basic settings menu, currently it includes sound control, with plans to expand it later. It’s simple for now, but it’s a good starting point for future tweaks. Home Screen We also added a home screen to serve as the game’s main entry point. It gives the project a more complete and polished feel right from launch. ...

Week 11 consisted of polishing and finishing up the game, we have stopped expanding scope and implimenting new features, we are in the process of adding all the sprites and sounds to the game as some of them are still placeholders. we are also in the process of finalizing the implimentation of map generation, i have gone through the code base to look for potential improvements and the overall quality is good. i have fixed some bugs (mainly movement related). i also expanded the current level to test pathfinding some more. ...

OUR GAME: https://github.com/CSG001-Project/UntitledGame SOURCE CODE: https://github.com/CSG001-Project/UntitledGame Trailer: https://youtu.be/X7zBNPeTrxs This blog post outlines my overall experience developing this game. While I’m happy with what we created and proud of the final product, I’ve realized that game development isn’t really for me. I found that I much prefer general software development building tools or applications for specific tasks over relying heavily on creativity, a game engine, and the implimentation. I prefer clear requirements and use cases, rather than designing worlds and mechanics from scratch that dont have a strong bases. ...