3D Shooting Game Release
I decided to use the UnityPlay showcase as my release destination. 3D Shooting Game Build#2.1 URP + Post Processing - Unity Play Since you mentioned identifying three topics, let's just summarize each of the three main elements required for a game: script, graphics, and BGM. 1. About the script What I did wrong I thought I should have a base for writing clean code in the early design stage, the first week or two of the project. The course said that speed and form should be prioritized over appearance, but there was a limit to how much you could do. The scripts were so closely interconnected that I was stuck in the second half of the course and felt suffocated. For example, the gameplay, UI, and sound were all tied together. When setting the timescale to zero on game over and animating the UI, everything was referencing the manager's scriptable object. Perhaps I should create a GameOver event with some kind of EVENT and have each one subscribe to it? I think it would have been better to create a GameOver event with some kind of EVENT and have each one subscribe and multicast. Speaking of things that went well Thanks to the component-oriented nature of Unity, I'm satisfied that I was able to do a good job with the detailed movement parts. Enemy AI with states, Turret controller to move the gimbal and barrel to track the player perfectly, etc. What I learned from these experiences Detailed parts can be implemented well if you take the time to research them online. However, no matter how good the materials are, if the blueprint is bad, the parts will not fit together properly. The hard work of making a bad design and failing made me realize that if I could use delegates, I wouldn't be in this situation. I was able to realize this. 2. Graphics What I did wrong When I was modeling with blender, I got so absorbed that I created models that I didn't use and wasted too much time on details. For example, I spent a lot of time adjusting the parameters of the particle system in Unity until I got the movement I was imagining, and then I didn't use it. Points that went well When I was changing the numbers of the particle system, I remembered that I had made an application to control particles from a script in practice, so I hastily made a script to move the velocity of particles directly from the velocity of the player, and I was satisfied with the result. What I learned from the experience I think my modeling skills have grown in this short period of time. As for Unity, I learned that parameters that can be edited in the inspector can be set in detail directly from the script, and that I shouldn't be too particular about editing in the inspector. 3. BGM What I did wrong Initially, I was trying to create a completely original piece of work using my own DAW software. Luckily, I was able to borrow from a friend's library. I imported a whole bunch of free assets and the project size was getting bloated. What went well I recorded the ventilation fan in my bathroom and edited it in Audacity to make it look like a spaceship. What I learned from the experience In the test play, I was impressed when the BGM changed and the enemy boss appeared when transitioning from the main stage to the boss stage. I lacked knowledge about sound and neglected some aspects of it, but this alone made me realize that it is a very important element. Translated with www.DeepL.com/Translator (free version)
