As the class comes to a close, i'm writing this post to discuss the future of this project and its implications. Originally this project was made for my father's teaching class, but the unrealistic goal of making the full game he requested, is something that makes me lose interest in continuing this project after the class. The goal of this class was met however, I wanted to work on simple modules that were essential to the mechanics of this proposed game, for practice and future use. I will be using this blog for future personal projects. Such future projects I personally feel interested in is making a dark soul's-esque module. Hopefully such a thing will come into fruition.
0 Comments
For this weeks milestone it was actually a lot more simple than I thought. I originally assumed that using a mouse to click things would involve raycasting but there is actually just a literally function called OnMouseDown(). However after that I had to figure out how to change the selection after you click another object. I decided to make a tag for each unit and have that tag be compared whenever the unit moves so only one unit moves.
The next steps are up for debate. I could work on a unit selector UI or I could work on placing the units. Either way both will have to be done. (Video Documentation is pending due to technical issues) After a little debugging I found out what was causing the calculation on battle damage to be one sided. The script was missing its timing of transferring values since it was doing everything within one frame, so I had to stagger it with a co routine.
I also added some UI that shows the stats of the current unit and the turn player. Next step is to have two units on each team and select them with the mouse. Video_Documentation |