No, tags aren’t needed here. Let me walk you through the process.
Let’s say you have an NPC. Add to the NPC class a variable of type “dialogue”. Like so: link.
Place this NPC into your level, select the NPC and set its dialogue: link.
Then you access this variable in your “interaction system”, whatever it may be. You can see a primitive interaction system in the demo that is linked on the product page. It just detects a mouse click, raycasts from the cursor position into the world and picks up whatever it hits first. Then it tries to convert it to an NPC, and if it’s an NPC, then it retrieves the value of its “dialogue”, and then launches this particular dialogue.
Here’s how it looks (we’re in the Player Controller blueprint): link.
This is an example for a top-down game. You may have a different type of game, with a first person perspective, for example. In that case, sending a raycast is a bit more difficult and you have to set-up collisions properly so that the raycast would hit the NPC and not go through. If you have a visual novel, the set up would be very different, too. Each type of game requires its own set-up, which is why I’m letting the creator do their own interaction system.
Let me know if the example I provided helped or not. I’ve seen your review, I understand you’re frustrated. It takes time to learn UE4, usually by watching tutorials first. It’s not very productive (or even good for your sanity) to jump into development and then get stuck on the first problem you encounter and remain stuck there for days or weeks. You would’ve benefited more from watching lessons on Udemy much more. They would’ve given you the foundation, upon which you can build by tackling small problems on your own. Writing an interaction system involves only a couple of nodes, but you can’t bruteforce your way through the problem. Anything more complicated than raycasting from your mouse cursor requires solid knowledge and understanding of UE4’s collision system, and the basics of UE4. I don’t want to critique your approach, but I would recommend to learn the engine before trying to solve problems in it. After having a certain amount of basic knowledge, you can continue learning by doing. But at first, you only need to learn by watching structured video lessons. Trying to learn UE4 by just launching it, poking around and looking for nodes that sound vaguely relevant is like grabbing a yoke on a plane mid-flight and learning how to fly that way.