Tower Defense Game
- Ryan Nicholson
- Jan 11
- 3 min read
(Will be transfered to myself soon)
Codecks: https://rectat.codecks.io/decks
Section 1 - Development
Section 2 - Collaboration
Section 3 - Reflection
Section 1 - Development
October, 13, 2025:
I added a detection system to the turret so it can now find enemies using a tag. When an enemy is in range, the turret will rotate to face them.
This makes the turret feel more alive and reactive, and it sets things up for proper combat features later on.

October, 25, 2025:
I fixed an issue where the turret’s aim was weird and it wouldn’t look in the correct direction.
Now the turret properly tracks targets and faces the right way when detecting and shooting at enemies.
October, 25, 2025:
I made the turrets actually shoot and deal damage. To help show what’s happening, I created and added two Niagara VFX blueprints, one for when the turret is firing, and another to show where the shots are going.
This makes combat feel clearer and more satisfying, instead of just having invisible damage happening.
Section 2 - Collaboration
Project Ideas
This project started with me sharing my game idea on our university’s module page. Students were tasked with posting their own ideas and commenting on the ones they liked and wanted to work on. Unfortunately, this didn’t have the intended effect, as most students either didn’t submit ideas or didn’t look at the page.
My friends, who I already knew, spoke to me in person about the idea, and we all decided to take it on and develop it further. First, we created our GDD, which we all worked on together to gain a better understanding of exactly what we wanted our game to be.
Codecks
I created a Codecks page, which is very similar to Trello but is more gamified and, in my opinion, better, as we can mark items as high priority or high effort. I also like the card system, as it allows people working in the same role, such as programmers and artists, to clearly show what they are working on, preventing two people from working on the same task.
Another feature I like about Codecks is the Discord integration. It is vital for keeping everything updated, as it allows us to use Discord commands to update the Codecks decks. This means that while discussing what is needed, we can easily and quickly add it to the checklist.

Discord
Discord is an excellent way to stay in contact with one another. It allows us to neatly organise important discussions, provides a space to announce key project information, and helps us keep up with each other’s work. It also lets us see when someone is online, and with the Codecks integration, it can be used to keep our decks up to date.

Playtesting

One of the main issues was a bug where the build menu would appear after walking past a built tower, which was confusing and frustrating for players. This issue was fixed, and we also introduced an upgrade system following these changes.
In terms of assets, we we
ren’t able to add much more to the game because our asset team members hadn’t produced any new assets for us.
Even with the playtesting feedback, the game still needed a lot more time and input from all team members to reach its full potential.

Section 1 - Reflection
Unfortunately, even with all of this, our project fell short. This was due to errors made by myself and other members of the group. I personally didn’t dedicate enough time to this project. I had been experiencing grief in my family during the project, but even with that, I believe I should have kept more up to date with my workload and helped my colleagues with theirs.
I believe the idea was cool and could have ended up as a strong project to show off on my portfolio. I also believe the Codecks could have been extremely helpful for our team, but unfortunately I ended up being the only one using them, even after requesting that my teammates do so as well.
After this project, I realised that I needed to really put my head down and complete my workload, regardless of my personal life and regardless of what my team members are or are not doing.
Another problem we ran into was that I do not think our group was compatible. We got along very well, but our overall workflow negatively affected each other’s end product. I think that certain members of my team did not produce enough work to justify working with them again, and I believe this not only reflects negatively on me but also damages my workflow.
As the saying goes, “Surround yourself with people who take their work seriously, but not themselves, those who work hard and play hard.”— Colin Powell



Comments