!Beware of bugs such as perhaps kicking enemies into walls or breakable blocks! Controls: -right and left arrow keys to move -down arrow key to crouch -z to jump -x to attack A two legged robot activates after a while after being transported onto an energy platform inside an abandoned facility. It doesn't know where it is, but what it does know is that it wants to get out of the facility. You control this robot and the goal is to bring it to an exit of the facility. Look for procedure chips that'll help the robot learn how to perform more moves to progress further. There's also other robots that may need to be fought for progression as well.
This is the first metroidvania I've ever made. I had planned to make one before but haven't in months. At some point though I imagined this game as a metroidvania I'd like to make. Now this game is out. I've had quite a few accomplishments from this, such as: -first platformer I made with a slide that actually continues when the player's under a platform -first game of mine that includes a charge attack -first game i made include somewhat more aggresive enemies(at least with fierce unit) as well as just more interresting enemies in general I'll be honest I got help from ChatGPT, but from multiple years ago. One time when I was on ChatGPT I thought about how some platformers have it so on some screens when the player goes to the bottom edge the game proceeds to another section below, but on other screens the player touching the bottom edge would make them lose. I asked ChatGPT about how this could be implemented and I learned it could be implemented by the game checking what the current level is to decide if the player will move on to another level or lose when touching the bottom edge. I thought of implementing this years later. I had fun working on this even despite some tedious things and actions I've done working on it that didn't make me the happiest. I'm surprised I enjoyed working on this for the most part as I've wanted to get into C programming and ow level programming in general after being exposed to just high level programming, yet I worked on this in a high level programming language, and game engine, and didn't get extremely bored. I'm pretty sure it's because this was the only game dev I've focused on this summer so far, and this game was more interesting than most games I've made before. I'm glad the game's done and now I plan to focus on actual C programming. I also planned for this game to be part of a game library I thought of making consisting of games that are the kinds of games I'd be interested in playing that I might actually be able play. Basically since there's several games I've seen that I thought looked cool but I may not able to play I decided to use the solution of making my own games. Now here's lore and background related to the game's story: The facility this game takes place in was occupied with people. They were building combat robots and to fight against a different group that were doing the same. Each robot was referred to as some kind of unit. Some specific the units stand. The Mix Unit was a robot that had features of most of the other units and was one of the bigger robots. Only one robot was built for the type because of resource constraints. The Warrior Unit was the biggest and most complex robot. Only one was built for the type as well, but it was planned for as it was meant to be the leading fighter of the robots if they were sent out to battle. The Legs Unit was a two legged robot and not much else was initially added to it. This, and it having only one robot for the type, were both caused because those in the facility found it more useless compared to other units. It was also given the name Di-Legs because it seemed to to those people, even despite their thoughts on the overall robot. The facility got abandoned by the people because they saw the other group would out power them. Though they trained the robots to fight they never specified which target they were meant to fight, so most of the robots would fight each other recklessly. Di-Legs didn't have this behavior because it never got into training. For damaged robots they might be carried by flying platforms that would bring them to energy platforms which would energize them again.
