shuko

Blast from the past. Reuploaded https://drive.google.com/drive/folders/1XXrSZbu7nCaW2UkOVsaVbKmX0ZmfFUtg?usp=sharing Feel free to use anyway you like, or dont. 🙂

Blast from the past. Reuploaded https://drive.google.com/drive/folders/1XXrSZbu7nCaW2UkOVsaVbKmX0ZmfFUtg?usp=sharing Feel free to use anyway you like, or dont. 🙂

Blast from the past. Reuploaded https://drive.google.com/drive/folders/1XXrSZbu7nCaW2UkOVsaVbKmX0ZmfFUtg?usp=sharing Feel free to use anyway you like, or dont. 🙂

Blast from the past. Reuploaded https://drive.google.com/drive/folders/1XXrSZbu7nCaW2UkOVsaVbKmX0ZmfFUtg?usp=sharing Feel free to use anyway you like, or dont. 🙂

Don't use the command player in dedi.

Interesting, I'm glad you figured it out and got it working.

I actually reinstalled Arma just to check this out. ;) Here's the test mission with those markers: https://www.dropbox.com/s/spdysewl5t0lydn/SHK_pos.Stratis.zip?dl=0

It seems you guys are trying to use the marker based search with the position/anchor based parameters. The 2nd parameter in anchor based search is the wanted distance from the origin/anchor, while on the marker based search the 2nd parameter is the water position. In other words, marker search wants a number 0, 1 or 2 and you are giving it an array (with the min/max distance).

You can do whatever you want with the script. I doubt I will do anything more with it.

This is a script I made a long ago to randomly pick positions: https://forums.bistudio.com/topic/153382-shk-pos/ You can specify the direction/angle and distance etc.

The script does not have an offset option in those cases. Basically, all the positions that are on the water's edge are usually positions which were originally in water and just moved to nearest land. One workaround is to be more careful/specific with the input parameters/input marker to manually avoid water.

You're the first person in over five years to ask for task delete. ;) I never even bothered with it, since all the missions I do/did were simple missions without respawn etc., so marking a task as cancelled was good enough. :)

They are not compatible with each other. It seems like BIS uses "BIS_fnc_taskVar_" tag in front of it's task names/variables. In a shot in the dark, you could give it a go by creating Taskmaster tasks with the name "BIS_fnc_taskVar_Task1" and then try BIS_delete task "Task1". I haven't tried it, and I'll give it 0.1% probability to work. ;)

You can do whatever you want with it.

The new commands are preferred. However, BIS_fnc_MP should work just fine, and it's changed/will be changed to use the new commands.