EagleGamer15
Member
I have to be missing something obvious, because I can't believe a package with so much versatility has this oversight. Why is blocking (not the animation ability, but the act of raising a shield/defense) tied to the aim ability? Doesn't that mean that it is impossible to have a character that can, at any point with a single equip loadout, either aim or block?
Example: Say I want to make a Captain America type of character that has a shield he can throw. How would I make it so he can be either aiming a throw or blocking, but is not doing both at the same time? I would really like to not have to re-code both Shield.cs and MeleeWeapon.cs.
For that matter, why is the Block ability just a glorified Damage Visualization?
Sorry, just frustrated trying to figure out something I'm sure is obvious.
Example: Say I want to make a Captain America type of character that has a shield he can throw. How would I make it so he can be either aiming a throw or blocking, but is not doing both at the same time? I would really like to not have to re-code both Shield.cs and MeleeWeapon.cs.
For that matter, why is the Block ability just a glorified Damage Visualization?
Sorry, just frustrated trying to figure out something I'm sure is obvious.