I came here to understand the difference between modules and plugins and I was not disappointed. That being said, you yourself, at 1:19 and 2:50 sneak the word "plugins" in there when talking about modules :) Thanks for the great video!😁
@@rogueentitydev It started in Lyra, but is now an Epic Plugin. Instead of binding to an Actor's broadcast(Observer pattern), you would bind to a message tag from the subsystem, so neither class has to know about each other(Pub-sub pattern). They just have to agree on a struct for the payload, and a gameplay tag as a channel of communication. It could keep you two modules independent. I've only played around with it a little, after seeing a post from Tom Looman or somebody. My framework isn't as big as your's, so I don't need it yet.
superb thank you.
Came here looking to understand how to structure openCV as a plugin.
Cheers
I came here to understand the difference between modules and plugins and I was not disappointed. That being said, you yourself, at 1:19 and 2:50 sneak the word "plugins" in there when talking about modules :) Thanks for the great video!😁
Doh! Thanks.
On plugin dependency at 5:25. Could using the gameplay message subsystem prevent the dependency? Pub-sub seems great for inter app coms.
I have not used/checked out the gameplay message subsystem so cant answer that, sounds like something to check out.
@@rogueentitydev It started in Lyra, but is now an Epic Plugin. Instead of binding to an Actor's broadcast(Observer pattern), you would bind to a message tag from the subsystem, so neither class has to know about each other(Pub-sub pattern). They just have to agree on a struct for the payload, and a gameplay tag as a channel of communication. It could keep you two modules independent. I've only played around with it a little, after seeing a post from Tom Looman or somebody. My framework isn't as big as your's, so I don't need it yet.
Thank you!