I made my modular system using this video. How can I use Interfaces with it?
If your blueprint has lots of casting in it, then yes, interfaces can help.
Maybe show some blueprint, because I don’t think any is going to watch the vid 
Well I resolved most of them on my own. But I wanted to ask whether should I use get actor of class node and get all actor of class node? Is it going to slow down my game loading? If yes, then what shall be the alternative to it?
1 Like
Get all actors of class will only slow down your game if you have a lot ( > 100 ) of that class, and you keep doing it, like on tick
1 Like
And what about get actor of class node (without all)?
Also, I believe that if you make a big game, you might make a lot of those nodes. Can you please let me know any alternative way which avoids using these nodes?
Get all actors of class is ok also, but it really depends what class.
If you getting static mesh actors, then there’s something wrong, probably.
In fact, if you really need any kind of ‘get actors’ node on a regular basis, there’s probably a better way of doing it.
Direct actor references is a good way, if you only need one or two, etc. ( just an actor reference ).
Also, if we’re talking about interfaces, there’s no point in getting actors of a blueprint class, because then you’ve cancelled any reason to use an interface.
1 Like
PS: I know it’s a bit confusing. The critical take-away is this
-
If you only ever use references ( variables ) or type ACTOR ( for other actors ), you will always be ok.
-
The only way to do this ( and not use casting ), is to use interfaces.
1 Like
Oh okay thanks for your support:grin:
1 Like