Allow to pass a function parameter to enemy:set_attack_consequence() #1062

christopho · 2017-07-12T09:16:50Z

This would be easier than defining "custom" + the enemy:on_custom_attack_received() event.

christopho added this to the v1.6 milestone Jul 12, 2017

christopho mentioned this issue May 18, 2018

Sword loading state is stopped if on_custom_attack_received is used #1176

Closed

christopho added a commit that referenced this issue May 18, 2018

Add test for enemy:set_attack_consequence() callback parameter (#1062)

ad890e1

christopho closed this as completed in 6d590e2 May 18, 2018

Diarandor mentioned this issue May 22, 2018

enemy:on_custom_attack_received(attack, enemy_sprite) does not allow to call enemy:hurt() #1181

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Allow to pass a function parameter to enemy:set_attack_consequence() #1062

Allow to pass a function parameter to enemy:set_attack_consequence() #1062

christopho commented Jul 12, 2017

Allow to pass a function parameter to enemy:set_attack_consequence() #1062

Allow to pass a function parameter to enemy:set_attack_consequence() #1062

Comments

christopho commented Jul 12, 2017