Game Development experience


What I learned so far...

  • Use Resource folder in Unity

Developing games with a lot of sprites and audio will consume a lot of RAM. So we must be able to unload all unecessary file when it is unactive. In Unitywe can only do this when the files are in a Resource folder. So it should have been used more often in this project and must be use in all future projects.

  • Create different scripts to work with mechanics and to be used for game desgin

This would really help in a long run. I should have used Scripts just to use variables and functions that will be affected by the player and the progress of the game. And created others scripts to develop the mechanics, controlling the UI and do the calculations. As the necessity of communication appears, then should I create a Script responsible to work with this information. Do not communicate directly. That way it becomes really hard to find what is happening in the code.

  • Set Canvas to a intermediate screen size

Before doing anything in a Canvas in Unity I should set the reference resolution. Using the largest one or the defaul twill result in low quality and bad responsible UI.

  • Create copies of the project

The Unity might bug anytime and lose all reference and conections made in the editor, such as [SerializableField] and values. If that occurs, you should close the project without save and reopen.

  • Test things that I still learning in others projects

Trying to connect with Google Services is a hard thing to do. It's even worse when we need to build the project to test if it is working. It is a lot faster to build an almost empty project. And if I decide to abandon the idea I will not have a lot of packages to remove from the project.

Leave a comment

Log in with itch.io to leave a comment.