So the focus has been currently on the Ray class as it makes it a hell of a lot easier to test and understand where stuff is failing but this is just a means to an end
We need a Ball class which probably will share a lot of code with the Ray class in terms of intersection. The idea of this is to don't copy paste any code (or as little as possible)
Ultimately the Ray class can become obsolete (unless we want to keep it around for stuff like fancy trajectory prediction which what is it currently)
So the focus has been currently on the Ray class as it makes it a hell of a lot easier to test and understand where stuff is failing but this is just a means to an end
We need a Ball class which probably will share a lot of code with the Ray class in terms of intersection. The idea of this is to don't copy paste any code (or as little as possible)
Ultimately the Ray class can become obsolete (unless we want to keep it around for stuff like fancy trajectory prediction which what is it currently)