Mokka

Sure you can add me on Steam! I have sent the link thingy to you as a PM

;_; I have returned I will send you something to help you tomorrow, once I have some more sleep in my system

You could go a step further, depending on the complexity of your project, and completely separate scripting components between server and client. This would basically mean putting all relevant files that are meant for the server only into an addon, which only the server loads in on startup. The mission file (i.e. the missionName.Altis) folder would then only contain scripts that are running on the client. If you want to go down that path, just let me know. I'll guide you through the setup if you wish

Hope this is not too late for you, but have a look at the BIKI entry on the Arma 3 Task Framework: https://community.bistudio.com/wiki/Arma_3_Task_Framework The article contains almost everything you need in regards to relevant functions and commands for setting up tasks an handling them As for server-siding functions, here are a few BIKI entries that can help you: https://community.bistudio.com/wiki/Locality_in_Multiplayer https://community.bistudio.com/wiki/isServer https://community.bistudio.com/wiki/isDedicated https://community.bistudio.com/wiki/hasInterface And the following little overview: if (isDedicated) then { //run on dedicated server only }; if (isServer) then { //run on dedicated server or player host }; if (hasInterface) then { //run on all player clients incl. player host }; if (!isDedicated) then { //run on all player clients incl. player host and headless clients }; if (!isServer) then { //run on all player clients incl. headless clients but not player host }; if (!hasInterface) then { //run on headless clients and dedicated server }; if (!hasInterface && !isDedicated) then { //run on headless clients only };