I want to have a behavior that makes the target walk randomly around for 5 seconds.
I made a buff behavior with the modifications set to uncommandable. I set the periodic effect to a Create persistant with:
Periodic Offsets set to 8 different offsets
Checked the flag Random Offset.
Set the Period Durations to 0.
Location to Target Unit
I set the periodic effect to an issue order effect, with:
Ability set to Move
Unit to (None) Target
Target to (None) Target Point
Other than that, the issue order is set to defualt settings.
But for some reason, it does not work at all? The unit get's the buff, but it just keeps attacking like nothing happened? It does not start moving to any of the offsets. I am most likely having some targets set up wrong, but which?
Try removing the Uncommandable flag, I don't know whether that also blocks Issue Order effects.
Using multiple effects with the same period sounds like a bad idea, at the very least it's unnecessary as only the last processed tick would get through unless the Issue Order is set to add to the order queue ("shift-click")
For the Issue Order effect, try using SourceUnit as the Unit and Persistent-TargetPoint as the Target, if that fails try all permutations of Target and Source with and without specifying an effect.
There's also a built-in Wander behavior, maybe you can work off that.
Hmmm, well I tried to just issue a stop command (before the persistant) and using a stop, where I found out that the right unit is the target of the apply behavior effect.
I then tried to create a trigger that would post some text, to see if it even launched the issue order, effect. And it does not!
The persistant effect is launched, but it does not launch the issue order command?..
The effect looks like this, at the moment. What am I doing wrong?
Have you tried the Source scope? Have you tried replacing the Move order with Stop with your current setup?
Try adding a Set effect with target type Point as the Periodic Effect, then add the Issue Order to the Set and adjust the scope accordingly. Maybe using offsets automatically forces the target location into the Point type, and since Issue Order can only affect units it fails. If this fails you can also try the PointOrUnit target type or using a second Persistent instead of the Set.
Another debugging idea would be to temporarily set the scope to Caster, as that is easy to identify.
I tried setting the periodic effect to a set effect set to unit. I set the effect to the issue order effect, but it still doesnt fire the issue order effect..
It seems that it's the conversion process from the create persistant to issue order, that fails. Is there a way to fix this?
Or is there another way to order a unit to move towards a random location within 0.5 range of itself? If not with data, then I need to use triggers I guess.
I want to have a behavior that makes the target walk randomly around for 5 seconds.
I made a buff behavior with the modifications set to uncommandable. I set the periodic effect to a Create persistant with:
I set the periodic effect to an issue order effect, with:
But for some reason, it does not work at all? The unit get's the buff, but it just keeps attacking like nothing happened? It does not start moving to any of the offsets. I am most likely having some targets set up wrong, but which?
Try removing the Uncommandable flag, I don't know whether that also blocks Issue Order effects.
Using multiple effects with the same period sounds like a bad idea, at the very least it's unnecessary as only the last processed tick would get through unless the Issue Order is set to add to the order queue ("shift-click")
For the Issue Order effect, try using SourceUnit as the Unit and Persistent-TargetPoint as the Target, if that fails try all permutations of Target and Source with and without specifying an effect.
There's also a built-in Wander behavior, maybe you can work off that.
Hmmm, well I tried to just issue a stop command (before the persistant) and using a stop, where I found out that the right unit is the target of the apply behavior effect.
I then tried to create a trigger that would post some text, to see if it even launched the issue order, effect. And it does not!
The persistant effect is launched, but it does not launch the issue order command?..
The effect looks like this, at the moment. What am I doing wrong?
Have you tried the Source scope? Have you tried replacing the Move order with Stop with your current setup?
Try adding a Set effect with target type Point as the Periodic Effect, then add the Issue Order to the Set and adjust the scope accordingly. Maybe using offsets automatically forces the target location into the Point type, and since Issue Order can only affect units it fails. If this fails you can also try the PointOrUnit target type or using a second Persistent instead of the Set.
Another debugging idea would be to temporarily set the scope to Caster, as that is easy to identify.
I tried setting the periodic effect to a set effect set to unit. I set the effect to the issue order effect, but it still doesnt fire the issue order effect..
It seems that it's the conversion process from the create persistant to issue order, that fails. Is there a way to fix this?
Or is there another way to order a unit to move towards a random location within 0.5 range of itself? If not with data, then I need to use triggers I guess.
well if you just want random walking around try adding a wander behavior to the unit.
@KingRadical: Go
I'd be damned - it works - I am 100% sure I tried it before. I must've changed some settings that made it work.
Thanks for making me try that again, lol :b