MBot Posted November 6, 2018 Posted November 6, 2018 A long time ago I made a mental note to use pushTask() only, as setTask() doesn't work (acts like resetTask). That is apparently still the case. Is that even an acknowledged issue? I just came across an interesting problem with Enroute Tasks applied via script. Apparent the scripting engine treats them like regular tasks, in that the action needs to be completed before the next action will be executed. Since Enroute Tasks are not meant to be "completed", this prevents all subsequent waypoint actions from being executed as long as the Enroute Task is active. This only happens with Enroute Tasks applied via script, within the ME it works.
funkyfranky Posted November 6, 2018 Posted November 6, 2018 I will be listening in to any competent reply on this topic very carefully. A warrior's mission is to foster the success of others. i9-12900K | RTX 4090 | 128 GB Ram 3200 MHz DDR-4 | Quest 3 RAT - On the Range - Rescue Helo - Recovery Tanker - Warehouse - Airboss
MBot Posted November 6, 2018 Author Posted November 6, 2018 Also is the lastWaypoint stopCondition working when using it for a scripted task? I can't get it to take effect.
Grimes Posted November 7, 2018 Posted November 7, 2018 Will have to test the behavior out. I've habitually used setTask when creating a new mission task and pushTask for anything on the fly and I want to keep the old task data. The right man in the wrong place makes all the difference in the world. Current Projects: Grayflag Server, Scripting Wiki Useful Links: Mission Scripting Tools MIST-(GitHub) MIST-(Thread) SLMOD, Wiki wishlist, Mission Editing Wiki!, Mission Building Forum
MBot Posted November 25, 2018 Author Posted November 25, 2018 (edited) There is something off with tasking. setTask() kills the group's default mission, causing it land at the nearest base, and popTask() crashes the game. Also is it not foreseen to be able to add tasks at the end of the queue? Edited November 25, 2018 by MBot 1
Recommended Posts