1. Overview and Debug Window

2. Use in Blueprint

3. Use in C++

4. Replicated message related interfaces (3.2)

• For the event system, it is a good way to decouple class references. The design of this plugin is more similar to the subscription publisher pattern design.

Question 1: So when should I use it?

I think the event system should be applied between modules, not within the same module. For this, I will use the contents of several of the systems I am developing as examples.

Damage system. For the same reason as the property system, inside it, we should not use the event system, but a submodule. But for the interaction between the damage system and the attribute system, we can use the event system to handle it. For example, if I hit the enemy and then cause damage, we can send a notification to the attribute system to tell him that I caused damage and need to execute it. Blood volume is deducted, or blocking deducts stamina (or other) and so on.

Event System Update Log:

V3.4 update log:

• Expand the listener logic, change the pin Self to Listener, and make it a pin that can be connected to any object;
• Update the plugin document link.