Was busy but going back to working on the project

I was planning to work on the translation between numbers and unity movement but decided to do click to move first

Click to move

Links of what I’m using:

1. https://sleepingdaemon.medium.com/unity3d-learn-how-to-point-and-click-to-move-11c5ec609b80
2. https://github.com/Unity-Technologies/NavMeshComponents
3. https://discussions.unity.com/t/installing-navmesh-components/864736

Thoughts:

1. Input.GetMouseButtonDown() is legacy code and it’s suggested to use Input System
   1. That’s because Input System handles mapping different keys better. Rebinding, accessibility, etc are much better with Input System
   2. I decided to use the old system cause for now I’m keeping it simple, but it’s definitely something I’d want to change in the future
      1. After all, imagine someone wants to use 1234567890 for spells instead of qwerasd! I won’t judge.
2. This went very very smoothly. I am surprised.
   1. I suppose it is the advantage of using third party libraries

Since I finished that sooner than expected, it’s time to… hm… figure out what I need to do

1. Set up lava section and make the floor way bigger. Way way bigger. In fact, how do I make the default background and floor lava?
   1. I wonder if round arenas are possible
2. Set up the data-to-physics translation system
3. Either limit camera to a specific area, or space to jump back to character/action