Page MenuHomeFeedback Tracker

"Set Task Destination" module inconsistencies
Closed, ResolvedPublic


Syncing the module to the main "Set Task" module causes the way-point to appear sometimes, but not always for me. {F17887}


Legacy ID
Steps To Reproduce

Set up multiple task module with a destination linked to it, then link it to the player. Some of the destination modules won't work properly in game.

Additional Information

I don't believe I am doing anything wrong because I have checked many times - the fact that the waypoints sometime show up is evident of this.

Event Timeline

SovietRaptor edited Additional Information. (Show Details)
SovietRaptor set Category to Editor.
SovietRaptor set Reproducibility to Sometimes.
SovietRaptor set Severity to Tweak.
SovietRaptor set Resolution to Fixed.
SovietRaptor set Legacy ID to 1419073561.May 7 2016, 12:20 PM

Glad I saw this.....I've been racking my brain over here wondering what the hell I'm doing wrong. Glad to see I'm not the only one. My first task it will show just's the subsequent one's that do not work.

Tubby added a subscriber: Tubby.May 7 2016, 12:20 PM
Tubby added a comment.Mar 13 2013, 6:44 AM

"My first task it will show just's the subsequent one's that do not work."


I am also unable to get the task destination to show up after the first.

Upon further testing I was able to get subsequent task destinations to show after the first. They need to be linked to the previous task's trigger as well as the new create task.

you have to use multiple triggers. If the second task is created by a trigger and the same trigger is also setting the destination you will have this problem as 1 trigger has 2 actions. The trigger does not know wich one to execute first so it will randomly pick one. If the set destination was picked first and after that the create task the task is create over the destination and thus will be removed. You have to copy your trigger 2 times and set a delay on the 2nd trigger of 1 second. So the task is created first and afterwards the second trigger will set the destination for that task in the correct order.


Doesn't that feel like a ghetto rigged solution? It would seem to me that any intel modules synced to a "create task" module should be good to go. So if I sync two "destination" module to a "create task" module it shouldn't be any issue. It's tied to that task only when It's created. Either way, someone was assigned to it. Hopefully we can get an easier solution. I don't like having to use markers all the time. Appreciate the tips though man!

i fully agree, triggers get confused when too much things are synced to them...
i.e. task destination, task states, create task itself, etc etc...

i find it mind bogging that i have to use 300 triggers in one mission
people have said to me on the forums to use scripting to make the tasks work... why the fuck should i learn to script when these task modules claim to do this for us...

i think its the destination module itself (doesnt need to be synced to anything else other than create task!!) and the triggers that set off the set task states.
i previewed a mission of mine yesterday and it all worked when i wanted to play again it didnt... i made it that the tasks auto assign when created (also buggy)
and 1 out of 4 destinations showed up... b r o k e n

I have to chime in and add to claims that the behavior of the "Set Task Destination" does not work in a logical or deterministic manner.

"taskdestinationworks.jpg" illustrates a setup that worked well for me: the player is synchronized with a task (1) to investigate behind the nearby shack. The task is activated automatically (2) and it's location displayed (5).

Now, if I then add an additional task module, even if I don't sync it to anything, this setup breaks. The task destination no longer appears when the mission starts.

Now try auto assigning the 2nd task as well with the task destination on task 2 ;)

It fucks up completely

The issue was that "Set destination" module was called before "Create" one, and its effect was replaced. The modules are now executed in the correct order - first "Create", then "Set" variants (e.g., destination, description, ...).

Additionally, it's possible to set destination and state right in the "Create" module.

This issue is still not fixed. Can not set set destination Task and still cannot assign task.

+1 with blackxcom.... still does not work all the time (destination) and (assigned - when trigger activates)

can this be set to not resolved again XD

That's incredible, it still doesn't work!!! -.-

If you use the "destination" inside of the "create task" itself it works every time for me now. So maybe for now just don't even bother with the "destination" module.

Only draw back to this is that sometimes I like my "create/state" modules to be near the start for players and in sort of an order. If you have to place the "create" task module at your destination you can't do that at all.

Ah ok, you have to put the create module on the destination! Because otherwise, it didn't work with a marker, creating a task during the game with the module setdestination didn't work, and finally, the function settaskdestination doesn't work either :S
Thank you

I will try some tests, but it looks all good on my account.

ill test with triggers and the rest and see

Marking resolved according to last comments.

Mass closing resolved issues not updated since November.