Task ID is also being used for creating global variables that hold different task parameters and are broadcasted on the network. Task ID is a string that differs tasks between each other and so task id is a required parameter for all setter functions and most of the getter functions. Good Techniques Keeping task ID short (MP) With this approach, all task operations are being handled on server - task creation and updates are initialized from server and thanks to the task framework the task data are automatically transferred to appropriate clients and the local execution is triggered there, so the tasks states are fully synchronized over the network. It is strongly suggested that all task operations are initialized from same place, preferably a server. Keeping those tasks fully synchronized while using only the engine based script commands could be very tedious in more complex MP scenarios.Īnd that’s why the task framework was created in the first place - to provide comfortable but still powerful tool for synchronized task creation and management in MP scenarios.
Arma 3 servers not showing up update#
In case you need to update the task, let say change the target destination or the task state, you would need to do the change on every group member machine. Similar issue if you want to give a task to whole group of players, you would need to create it separately on every machine. If you create it on a local client, server would not know about the task existence at all. It means that if task is created using the script command createSimpleTask it is created only on the machine where it was called. In MP environment things get complicated. In SP environment everything is very easy as task data and execution are all handled on one place and there is no needs for synchronization. Handling Tasks in MP Environmentīeing said, task framework can be used in both SP and MP environments. Check the function headers in the function viewer from inside of the game for detailed information about function syntax and parameters. In normal circumstances the setter and getter functions are all is needed to create and manage tasks. Can be called directly, however using the setter functions is recommended.įunction that locally creates or updates task data. Returns engine task associated with the task idĬreates and updates task data and automatically calls BIS_fnc_setTaskLocal. Returns variable under which task is stored in the game (based on task id) Special getter functions that are used by the task framework Return all tasks that given unit has (in any state) Returns true if task exists (was created and not deleted) Returns task title, description and marker texts Returns true if task is "SUCCEEDED", "FAILED" or "CANCELED" Removes task from given target, if no one has the task, task is removed from the frameworkįunctions for retrieving information about tasks Sets task title, description and marker texts The whole task framework consists of multiple functions that can be split into several categories according to their functionality and purpose:įunctions for creating and updating tasks their data It’s main goal is to provide solid interface for creating, updating and managing tasks in both environments and fully automatize synchronization in MP environment. Task framework is a complex scripted system for handling tasks in both singleplayer and multiplayer environment.
0 kommentar(er)
