Worm

• 

  Jerry

• 

  Slime

• 

  Intro

Inspiration

When they announced the theme for this year, my mind went almost instantly to this idea. It seemed more possible to me because I have forgotten all about front-end developing and felt comfortable doing more backend coding.

What it does

It is a game with 9 stages, but they are not long. This experience can be finished in a minute. It is a text adventure game where you make choices, fight an enemy, or try to find a secret. It is meant to be entertaining and a learning experience for me and others if they wish to make projects on their own even as a beginner.

How we built it

It was built in C++ with only libraries from the standard libraries.

Challenges we ran into

An hour before the soft deadline, as I was finishing the last screen and transition into the elevator. When I ran to test it, it did not transition correctly and started duplicating code that I was outputting. My code had no errors, so it wasn't obvious what was wrong. I looked at the statements in charge of transition, and they were looking fine, so I deleted it and rewrote it, which solved the duplicating code but not the transition. It took me around 20 minutes til I realized that one of my statement conditions was the issue. The statement was checking a value and if it was true then it would pause the program. However, it would pause the program before it even printed the screen because it would fulfill the condition then pauses and not fulfill the condition, print the screen, then pause. I ended up adding +1 to the value I was checking and that smoothed it out.

Accomplishments that we're proud of

I managed to build the UI with just output statements, and this is my very first large project that I built and while it is a bit rough, I am happy that I was able to make my first big project.

What we learned

What I learned is that what the developer sees and what the user sees can be very different. Not in the aspect of how they see the screen and the developer sees the code but how even when the developer sees the screen in code, it looks different from when its running. I also was learning what was more time efficient for debugging as I used to run the whole program to see if it was working right but then later on as it grew bigger decided to start the program from the newest addition I added so I could check if that part worked correctly and not go through the roundabout of going through the whole program.

What's next for Game

For the design aspect, I really wanted to try adding the boss for the ending, but I was trying to fill out the other stages with gimmicks to give variety. I wanted to try an instance where the player would be talking with a npc and select from pre-selected dialogue choices that could steer the conversation into different directions. For the code, I wanted to explain more of what my program did so that it would make it easy to understand my code because when I was looking at it. It felt cluttered.

Built With

• c++