Post by DarkTonic Dev on Nov 9, 2017 5:36:35 GMT
Yeah actually #1 is the easiest since the Triggered Spawner would be the easiest since the Inspector there lets you select Prefab Pools and all that. And you could limit the Custom Event to only send to Receivers on the same Game Object. However...there's currently a limitation that Custom Events can only be fired once per frame, so if you killed two or more of Killables with the same Death Custom Event, they wouldn't all fire (I will be changing this in the next update, but that's how it is now). We actually wanted to do the same sort of thing (Fire Custom event for just that Game Object but make sure they all fire).
#2, Listeners are pretty cool and unless making a subclass of Killable, whatever public fields you add to them will show up since the Inspectors are not "custom". So you could add as many fields as you like for X Prefab Pools to your Listener and override the Despawning method (or actually several of them would do the trick), and just not have a death prefab assigned in the Killable. Then it would be a few lines of code to spawn whatever you liked from how many Prefab Pools.
#3, sure, but maybe #2 is better slightly and if you end up adding more to the Listener later, you already have the skeleton code there. No extra scripts.
#2, Listeners are pretty cool and unless making a subclass of Killable, whatever public fields you add to them will show up since the Inspectors are not "custom". So you could add as many fields as you like for X Prefab Pools to your Listener and override the Despawning method (or actually several of them would do the trick), and just not have a death prefab assigned in the Killable. Then it would be a few lines of code to spawn whatever you liked from how many Prefab Pools.
#3, sure, but maybe #2 is better slightly and if you end up adding more to the Listener later, you already have the skeleton code there. No extra scripts.