> For the complete documentation index, see [llms.txt](https://missnohit.gitbook.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://missnohit.gitbook.io/home/documentation/blueprint-nodes.md). # Blueprint Nodes ### Initialize Tracers Serves the purpose of providing the Tracer Source object to a Tracer. For AnimNotify and Physical Asset Tracers, users must supply the Skeletal Mesh as the Tracer Source. In the case of Mnh Shape Component Tracer, users are required to supply either "Mnh Box," "Mnh Sphere," or "Mnh Capsule" as the Tracer Source. This ensures proper configuration of Tracer Source objects for respective Tracer types. Initialize Tracer’s node is expected to be called at BeginPlay. For dynamically added Trace Sources, like weapons, it is essential to re-execute the "Initialize Tracers" node. This ensures that the system is updated with the new Trace Sources ### Start Tracers Commands the Tracers to initiate Hit Detection Traces. This node can activate multiple Tracers simultaneously, which is why it can accept more than one Tracer Tag. The "Reset Hit Cache" function, as the name suggests, clears the Hit Cache utilized for hit filtering.
### Start Tracers Event Works in similar fashion to Start Tracers node but comes with built-in execution pins that fire on hit detection. Upon successful detection, the system automatically triggers the "On Hit" execution pin, providing output data such as "Tracer Tag," "Hit Result," and "Delta Time." The output from the Tracer Control Node can be utilized to prevent the event from firing again, offering control over the Tracer execution flow.
### Stop Event Halts execution of “On Hit” events when called on “Tracer Control Node” output.
### Start All Tracers Event Functions identically to “Start Tracers Event” but automatically activates all available Tracers. This approach eliminates the need to specify individual Tracer Tags ### On Tracer Hit Detected Operates similarly to "Start Tracers Event" nodes, with the distinction that they exclusively listen for Hit Detections without initiating the Hit checking process.
### Stop Tracers & Stop All Tracers The counterparts to the "Start" methods, these commands instruct the Tracers to cease checking for hits. ### Reset Hit Cache Empties the Hit Cache, which is a storage mechanism used to keep track of previously hit Actors during the hit detection process. This operation effectively clears the stored hit information, allowing the system to start fresh in terms of hit tracking and filtering. An example of how these nodes interact with each other; This sequence outlines a scenario where hit detection is initiated, triggering an event to spawn a Niagara emitter upon detection, and then stops checking for hits after a 5-second delay. Anim Notify State - Mnh Activate Tracer: Not to be confused with Anim Notify Tracers, it commands Tracers on the owner actor to start and stop based on the designated timeline, providing a way to manage Tracer behavior within the animation. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://missnohit.gitbook.io/home/documentation/blueprint-nodes.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.