fig02

Results 104 comments of fig02

Sorry that image of the hookshot is a bit misleading cause of how the arrows are oriented/positioned. Heres a similar angle as the boomerang. They are at least both in...

They are pointing at complete opposite points between hookshot and boomerang, how is tip and base helping here

The weapon info system is used for more than melee weapons, so I think it should accommodate for that fact. Being generic when things are generic only really makes sense....

Just for completeness sake, here is arrow which match the hookshot in orientation. ![image](https://github.com/user-attachments/assets/aed0cde4-dd92-4c07-8d9c-9cf020bcbc40)

@krm01 do you still want to keep tip and base given the information above? You said `Honestly tip/base still works, and is just plain easier to reason about` But Im...

The orientation does matter. I would only be on board if it were like so ![image](https://github.com/user-attachments/assets/a38c1d2c-f6e0-459f-bd77-7b4c7492d591)

I think the other uses are being disregarded as small use cases/hacks when 3 different weapons is a significant amount. And I still dont follow how we can call it...

trying to lean toward compromise is a nice thought, but dont think it will really help with anything in this case The main debate here is over what these members...

Phrased another way, I have no problem with tip and base terminology being used in `func_800906D4`, the function that sets this stuff for melee weapons. Within this function, there is...

I think the macro is a great compromise.