Quick question is this the best way to cast between two BPies ...

[EtienneAndlau]

@ClavosTech

Zak Parrish does a tutorial that’s considered a ‘standard on Blueprint comms’. Most devs watch that (its a Livestream iirc)… Definitely Get-All-Actors can be slow, so you don’t want to place it in a Loop or run it on Tick etc. But the further you go with your project the more you’ll learn which classes need to communication. Approaches:

Easiest: Direct-Comms: Have one class spawn another so it automatically gets a reference to it. Or (in single-player) have gamemode spawn classes so it can set all the references inside the classes directly. Or store (house) these ‘shared communication variables’ in gamemode. Then you just need to cast to gamemode (not use get-all-actors etc). BP Global-Functional-Libraries can also simplify much of this work.

Intermediate: Create your own Get-All-Actors etc. Add classes to an array (of actors) as they’re spawned into the game. This array can reside inside multiple classes or just gamemode. You can also ‘cache’ Get-All-Actors by assigning the result to an array once at game start-up… Or just very occasionally, so its not called too often (this is useful if you’re constantly creating / destroying actors you need references too etc).

Advanced: Interfaces / Event Dispatchers: Zak covers these in depth and they take time to explain so better not get into it here. But Interfaces particularly are a workaround for casting, as you can call methods directly on actors without casting at all. There’s a Get-All-Actors of Interface node to get references to these actors, which is less heavy a call. Event Dispatchers are for creating event driven gameplay and for ‘hooking into’ events for objects created dynamically at game-time (often used by classes or components to send messages / events to one another etc etc).

Great thank you very much !!!