What Went Right

1. Smooth Mechanic Implementation

One thing that went right was the overall implementation of the core mechanics. Each system I created worked seamlessly with the next, from player movement to interaction systems. This smooth implementation meant fewer debugging sessions and allowed for more creative freedom during the later stages of development. I spent a good amount of time planning these mechanics before diving in, which helped in making sure they worked together from the start.

2. Efficient Problem Solving

I ran into several issues during the project—mainly with physics interactions and how certain objects moved or responded to player input. Instead of these becoming roadblocks, I was able to break down each issue and systematically troubleshoot them. For example, when the monster movement wasn’t behaving as expected, I managed to refine the logic, so the enemies moved predictably and satisfyingly. This ability to solve problems quickly saved a lot of time and frustration.

3. Sound Design Integration

One of the coolest aspects of _Tounamental_ was the integration of sound with mechanics. I added sound triggers for when the monsters spawned and when they killed the player. It might seem like a small detail, but the addition of these sounds gave the game more immersion and a stronger sense of impact, making each moment feel more alive.

4. Efficient Use of Tools

I made good use of Unreal Engine’s tools, especially the Blueprints for more complex mechanics. I avoided overcomplicating the code and relied on the engine’s built-in systems, which made my workflow a lot faster. This allowed me to focus on refining the player’s experience rather than constantly battling with technical challenges.

5. Flexibility for Future Changes

I designed the mechanics in a modular way, which means it will be easy to expand or modify them in the future. If I want to add more monsters or change the way they spawn, I’ve set up the systems in a way that makes those changes straightforward. This forward-thinking approach will pay off if the project evolves further.

Postmortem

Monster Tile was a project where I focused entirely on creating and implementing various game mechanics. The project’s main objective was to design functional, dynamic mechanics to offer players a smooth and engaging gameplay experience. The mechanics ranged from core gameplay actions to more advanced interactions, each carefully crafted to meet design goals and offer creative freedom.

What Went Wrong

1. Monster Movement Limitations

Although the monster movement worked for the basic concept, it was limited to just moving in a straight line. This made the AI feel a bit predictable and didn’t offer many variety in terms of gameplay challenges. If I could do it again, I’d spend more time working on a more advanced movement system, allowing monsters to turn, follow paths, or even react to the player’s position dynamically.

2. Repetitive Mechanic Use

Another thing that didn’t work as well was how repetitive some of the mechanics became. After several playthroughs, it became clear that the monster spawning and instakill mechanics, while functional, didn’t offer much variety to the player. I should have designed more diverse interactions, such as different monster behaviors or more complex objectives, to keep the gameplay engaging over time.

3. Lack of Visual Feedback

One area I overlooked was providing enough visual feedback for the player. For example, when a monster spawns, there’s a sound cue, but visually, there’s not much to indicate the event. Adding particle effects or changing lighting could have made the mechanic feel more impactful. This is something I would improve in future iterations.

4. Difficulty in Balancing Spawn Rates

Getting the timing right for the monster spawner proved challenging. I either set the spawn rate too high, which overwhelmed the player, or too low, which made the game feel too easy. This balancing act took more time than expected, and in retrospect, I should have implemented a dynamic system where the spawn rate could adjust based on the player’s progress or performance.

5. Over-reliance on Instakill Mechanic

The instakill mechanic, while dramatic, became a crutch in the design. It was initially exciting but didn’t offer much room for player skill or strategy. I’d change this by adding different health systems or multiple ways for players to avoid or counteract the monsters, creating more depth and variety in gameplay.

Monster Tile was an excellent learning experience in developing mechanics from scratch. While there were a lot of wins, such as smooth mechanic implementation and efficient problem-solving, there were also areas for growth, particularly in adding more depth and variety to the gameplay. Moving forward, I plan to expand on the movement systems and add more visual and gameplay feedback to make future iterations even more engaging.