The further we get into the development of Hermit, the more we realize how important bug reports are. I updated our bug reporting tool to include log messages and other useful information, and automatically report errors if the user allows it. Let’s see how it’s done.

I’ve been struggling with scroll rects in Unity for quite some time now, and thought I would give it some time and try to understand how they work. I need them to do two things: dynamically adapt to growing content, and scroll with navigation inputs, i.e. arrows or joystick, when going over content in the scroll rect. Here is a breakdown of how I made it work.

One of the main goals we had in mind when designing Chro_M@tic R@cing was to involve the player in the creation of art. By enabling the visitors to virtually take possession of the exhibited sidecars, they become part of the creation process and can actively contribute to the generation of funny little pieces, which are then printed and posted to Twitter. This process took quite a bit of effort, and I am going to try to explain it here (sorry, it’s going to be technical again😅).

Managing bugs and getting bug reports for a game is really important in order to improve the player’s quality of gameplay. To manage the bugs I wanted to use Github’s nice issue tracker, and I wanted testers to be able to submit bugs directly from within the game. Instead of doing this just for me, I implemented a package. Let’s see how I did all of this.

Shells are at the core of Hermit’s gameplay, and how satisfying they are to use and how nice it feels to have different versions of them will determine how the player perceives the game. Today I want to address one of our earliest shell already present in the prototype, the Rocket shell.