订阅以下载
Bagigi's Restrict Markers

This is a fork and major rework of the Restrict Markers mod by JibStyle, by the Bagigi Arma 3 Community[units.arma3.com].

It is available on GitHub[github.com], changes from the original mod are in the "bagigi" branch[github.com].


The main goal of the original mod, as well as this Fork's improvements, is to make the Arma 3 Map more realistic by preventing "magic" sharing of markers across long distances.
Instead, markers are only placed on the creator's map and those of nearby players. They can later be re-shared with other players via ACE Interactions.

These limitations lead to more realistic gameplay and radio use, as communications referencing a "marked position" are only useful if those markers were shared among units previously, requiring better planning and definition of Waypoints, Reference Points and Landing Zones, or simply communicating positions by coordinates, instead of being able to rely on instantly shared markers and Squad "Actuals".

Other features include:

• CBA Settings that allow tweaking of maximum share distances and more;
  
• ACE Map Self-Interactions or Interactions on players can be used to re-share your markers with nearby units;
  
• ACE Interactions on Players to copy their markers without consent, can be disabled for foreign factions via a CBA Setting;
  
• ACE Map Self-Interaction to toggle "automatic marker sharing", for when you only want to draw on your own map and not let anyone copy from it (as long as you are not unconscious or handcuffed);

The mod does NOT restrict the markers created by scripts or the Zeus interface.
IF scripts use the _USER_DEFINED #<PlayerID>/<MarkerID>/<ChannelID>[community.bistudio.com] naming system for their markers (in order to keep them player-editable), they will still be restricted by this mod.
To prevent this, simply add a suffix to the name of the marker you are creating, like "_USER_DEFINED #<PlayerID>/<MarkerID>/<ChannelID> MyScript".

BFT mods such as cTab are also untouched, making their availability more important for quick tactical coordination.

A Dedicated Server will receive any marker that is created, any movement or the deletion of said marker will only be propagated to the server if made/received by the original creator.
This makes the mod compatible with "marker to missionProfile"-saving frameworks, like those of the Hearts&Minds mission[github.com].

As for OCAP2[github.com] recordings by the server, at the moment there is an issue where any marker is duplicated on the recording for every player who receives it. A fix has already been proposed[github.com], you can check it out and build an updated "recorder.pbo" to use on your server.

• Editor Object Attributes, CBA Settings and/or script variables that determine whether specific players/roles can send/receive markers without restrictions;
  
• Simulate "DataLink" of vehicles or players (with certain items) that allows them to share markers more freely;