[Change] Use variables for map marker config#310
Merged
Conversation
This does technically cause a performance hit to missions that disable squad/FT markers, but it's no more than the normal performance cost of having them, so it should be fine.
Collaborator
|
Looks nice, thank you. I'll test it soon |
Replaced with f_var_showSquadMarkers in mapMarkers config
Collaborator
|
Just tested - this works well. It is locally changeable which is really useful but that needs to be explained, especially to new MMs. I've splatted a bunch of documentation into it in this example but it may be too verbose. Feel free to chop and cut: /*
Map marker configuration
All settings below can be changed while the mission is running (except for MicroDAGR integration).
These settings are individually changeable for each player. This is useful if some players should have markers and some should not.
To change these settings for everyone, make sure that the change is 'global'. Some examples are below:
Example: disable squad markers for everyone (can be run mid-mission):
missionNamespace setVariable ["f_var_showSquadMarkers", false, true];
Example: disable squad markers for only the OPFOR side (can put this into the 'customStartup_server.sqf' file):
[missionNamespace, ["f_var_showSquadMarkers", false]] remoteExecCall ["setVariable", east, "ChangeOpforMarkers"];
*/
// To disable squad markers on the map, set the variable on the line below to false
// Note: This variable can be changed while the mission is running
f_var_showSquadMarkers = true;
// To disable fireteam member markers on the map, set the variable on the line below to false
// Note: This variable can be changed while the mission is running
f_var_showFTMarkers = true;
// To hide AI squads on the map, set the variable on the line below to false
// Note: This variable can be changed while the mission is running
f_var_showNPCSquads = true;
// To disable squadmarker MicroDAGR integration, set the below variable to false.
// Note: MicroDAGR markers act like a normal GPS - they respect the configuration of the three settings above.
// Note: This variable cannot be changed while the mission is running
f_var_enableMicroDAGRSquadMarkers = true;
|
Bubbus
approved these changes
Feb 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request Description
When merged this pull request will:
Release Notes
Map marker configuration now uses variables instead of #define. Mission makers can change these variables mid-mission to toggle squad or fireteam member markers dynamically.
IMPORTANT
[Descriptor] - Add|Fix|Improve|Change|Make|Remove {changes}.