this post was submitted on 14 Mar 2024
15 points (100.0% liked)

Godot

6007 readers
20 users here now

Welcome to the programming.dev Godot community!

This is a place where you can discuss about anything relating to the Godot game engine. Feel free to ask questions, post tutorials, show off your godot game, etc.

Make sure to follow the Godot CoC while chatting

We have a matrix room that can be used for chatting with other members of the community here

Links

Other Communities

Rules

We have a four strike system in this community where you get warned the first time you break a rule, then given a week ban, then given a year ban, then a permanent ban. Certain actions may bypass this and go straight to permanent ban if severe enough and done with malicious intent

Wormhole

!roguelikedev@programming.dev

Credits

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
Feyter@programming.dev
15
On-Kill/On-Hit effects: Signal train vs reference passing (lemmy.world)
submitted 9 months ago by Jozzo@lemmy.world to c/godot@programming.dev
6 comments fedilink hide all child comments
 

Wanted some opinions on ways to set up triggering "on-kill" effects. In short: The player can have abilities that trigger effects whenever they shoot and kill an enemy. I'm also looking to extend abilities to enemies as well, so can't just hardcode a player reference.

Currently I'm doing it like this:

  • Enemy signals that it died -> the bullet receives this and signals that it killed Enemy -> the player's weapon receives this and signals that it's bullet killed Enemy -> the player receives this and triggers it's on-kill abilities.

It simultaneously feels like a good way to go about it but also a long mess. The other option I've considered is:

  • Each bullet has a reference to it's owner (eg. player). When an enemy dies to a bullet, it looks to the bullet's owner reference and tells it to trigger it's on-kill effects.

This way is a lot simpler to write, but is error prone eg. In cases where the bullet's owner is killed while their attack is mid-air.

Thank you all!

you are viewing a single comment's thread
view the rest of the comments
[–] melmi@lemmy.blahaj.zone 8 points 9 months ago (1 children)

I tend to prefer the latter, but I totally get that feeling where signals seem like they "should" be better. I just find in practice that references are a little easier to work with in some cases.

You can easily solve the owner dying issue by just using is_instance_valid() before attempting to call anything on the owner reference.

That said, you can probably simplify your signal code if you connected the bullet killed_enemy signal directly to the player's on-hit handler. It seems like the weapon on-kill handler is redundant? But I don't know the details of your implementation, I just know that there's often ways to simplify chains like this.

I find that signals are great in some use cases, and less good in other use cases.

[–] Jozzo@lemmy.world 3 points 9 months ago

The longer I'm using the signal chain the more I'm wanting to rework it to just be a reference lol. Good point with checking if the instance is valid, if any other errors come up I could just patch around them in a similar fashion.

That said, you can probably simplify your signal code if you connected the bullet killed_enemy signal directly to the player’s on-hit handler. It seems like the weapon on-kill handler is redundant?

Ah I see what you mean, killed_enemy(enemy-object) signals directly to the player which can then pass that enemy to it's abilities if needed. You're correct that the weapon signal is mostly redundant, it was just the easiest node to connect to the bullet's signals, as it's responsible for spawning them.

I think I'll change the whole system to just use a reference. Thanks for your input!