Long story short, I have a(n npc) character using AI MoveTo which is meant to extinguish a flame (a particle system emitter) attached to a pawn for ease of node logic (because I’m a dumb-dumb who only has the most basic concepts of programming down), and then proceed to MoveTo the player.
Somehow the logic for extinguishing the flame broke and as I was trying to fix it the Destroy Actor node SOMEHOW backfired and started destroying the event triggering character (???), likely due to my node system held together by duct tape. So I disconnected as many of the destroy nodes and even the overlap events that could feasibly be triggering the uncalled for destruction but it just keeps happening and I am at a loss.
When doing some digging in the Output Log for some sort of explanation I’m getting a “LogCharacterMovement: Warning: GetSimulationTimeStep() - Max iterations 8 hit” warning but every thing else seems somewhat spiffy. The silver lining is that I was able to clean up some code and warnings while desperately trying to track down the issue, but all debugging screens and tools that I can even sort of comprehend all seem to be returning everything as normal. My NPC just disappears with no explanation or reasoning from the editor.
EDIT: After migrating EVERYTHING to a new UE4 Editor file, I have confirmed that it’s either the nodes themselves that are the issue… or the corrupted data migrates with everything else. -_-’
On you AI blueprint, create a variable of the Actor obj reference type and set it to “Instance Editable” and “Expose on Spawn” (I’ve named my variable “ActiveTorch”):
For the sake of this simple explanation, my AI will start moving to the “ActiveTorch” whenever its spawned:
Back in your character blueprint, on the event dispatcher binding, come out of the red event pin and “Create Custom Event”, call it whatever you’d like. You should notice that it automatically will add the actor object reference:
Promote the pin to a variable:
Then, spawn your AI actor, feeding in the “Active Torch”:
