10-31-2024, 02:50 AM
(This post was last modified: 10-31-2024, 02:56 AM by DerVVulfman.)
The issue is not Weapons, but Skills.... Game_Ranged_Skill has its own variation of the 'check_event_trigger_touch' method.
When I made Lycan, I moved this basic catch-all method into Range_Base
I guess I'm going to be moviing "Is_Range_Ballistic" into the Game_Range class so it can be used by both, and have a separate check_even_trigger_touch' for Game_Range_skill...
EDIT 1: Oh, for pity sake... the method for SKILL is virtually the same for WEAPON. Only difference is how it skips skill attacks or permits em in code. Same result, different way of writing it.
When I made Lycan, I moved this basic catch-all method into Range_Base
I guess I'm going to be moviing "Is_Range_Ballistic" into the Game_Range class so it can be used by both, and have a separate check_even_trigger_touch' for Game_Range_skill...
EDIT 1: Oh, for pity sake... the method for SKILL is virtually the same for WEAPON. Only difference is how it skips skill attacks or permits em in code. Same result, different way of writing it.