Hi. I’m Elm and I’m learning to code with Unity. 

Some people consider making games with Unity to be a daunting task, especially when lacking experience in a game engine or coding. I’m not particularly phased by this notion. Everyone who does great things now, had to learn at some point. None of us were born knowing code. When you think of it like that, it seems pretty straightforward.

This daily journal is a breakdown of how we look at creating projects in Unity and familiarising ourselves with that environment.

Through this blog I will probably not explain the very basics, but I hope to cover most of them. The topics I will discuss assume your familiar with some asset authoring tools or 3D software such as 3DsMax, Maya and understand the purpose and function of game engines such as Unreal. It will not cover aspects of 3D game art creation. Simply because this is what I already know. Although, occasionally I may mention things as a sort of refresher. 

Despite working in Industry, Unity is a complete fresh start for me. 

My usual go to of familiarising myself with anything is to read the entire documentation at least once so I know the depth of what I’m dealing with on a surface level. Many people do not like to learn or work this way, and they’re probably right to.

So why am I doing this?

Well, first of all. If you stumbled upon this, then you might already know I’m working on a project I call Primrose, but I also have another project nicknamed Companion. 

With these in mind, I will be talking about Unity basics and development that is relevant to these projects - both 2D narrative heavy games. 

I might make other mini games along the way, as a method of experimentation. No matter what, I’ll document it here and post daily. It helps me remember.