Post by AppThing on Jun 16, 2014 15:18:10 GMT
Hi,
The Question:
Q. Is it normal that a child collider should trigger damage on a parent Killable? and if so, is there a way around this behaviour?
The Scenario:
I have two gameObjects in my test scene with the following hierarchy;
(Enemy)
- EnemyArcher <RigidBody, Sphere Collider (Rad: 0.5), NavMesh Agent & Killable Script, EnemyController Script>
-- Archer_01 (the animated, skinned asset)
-- RangedWeaponRange <Sphere Collider (Rad: 7, IsTrigger), Triggered Spawner, disabled Renderer>
-- MeleeWeaponRange <Sphere Collider (Rad: 0.75, IsTrigger), Triggered Spawner>
(Player)
- Player <ClickToMove, Capsule Collider (Rad: 0.6), Killable Script (Attack Points:1), NavMeshAgent>
-- PlayerWeapon <RigidBody, Box Collider, Killable (Attack Points:25)> ) - i.e. has no renderer
What is supposed to happen is that the Enemy "Follows" the player until the Ranged Weapon Collider Triggers, at which point he stops moving (moves to stay in range) and an "EnemyBow" gets spawned which in turn spawns arrows at the Player.
What actually happens is that when the Enemy RangedWeaponRange Collider hits the PlayerWeapon (which is about the same time as it hits the Player) then the EnemyArcher immediately takes 25 points of damage and is killed. :-(
Is it normal that a child collider should trigger damage on a parent Killable? and if so, is there a way around this behaviour?
many thanks.
The Question:
Q. Is it normal that a child collider should trigger damage on a parent Killable? and if so, is there a way around this behaviour?
The Scenario:
I have two gameObjects in my test scene with the following hierarchy;
(Enemy)
- EnemyArcher <RigidBody, Sphere Collider (Rad: 0.5), NavMesh Agent & Killable Script, EnemyController Script>
-- Archer_01 (the animated, skinned asset)
-- RangedWeaponRange <Sphere Collider (Rad: 7, IsTrigger), Triggered Spawner, disabled Renderer>
-- MeleeWeaponRange <Sphere Collider (Rad: 0.75, IsTrigger), Triggered Spawner>
(Player)
- Player <ClickToMove, Capsule Collider (Rad: 0.6), Killable Script (Attack Points:1), NavMeshAgent>
-- PlayerWeapon <RigidBody, Box Collider, Killable (Attack Points:25)> ) - i.e. has no renderer
What is supposed to happen is that the Enemy "Follows" the player until the Ranged Weapon Collider Triggers, at which point he stops moving (moves to stay in range) and an "EnemyBow" gets spawned which in turn spawns arrows at the Player.
What actually happens is that when the Enemy RangedWeaponRange Collider hits the PlayerWeapon (which is about the same time as it hits the Player) then the EnemyArcher immediately takes 25 points of damage and is killed. :-(
Is it normal that a child collider should trigger damage on a parent Killable? and if so, is there a way around this behaviour?
many thanks.
