Page MenuHomeFeedback Tracker

[Feature request] setMarkerType(+Local) variants to utilize missionCfg defined markers
Closed, DuplicatePublic

Description

It is technically possible to create inherited marker inside missionCfg, for example

class My_MissionConfig
{
    import mil_dot from CfgMarkers;

    class test_marker : mil_dot
    {
        name = "Test Marker";
        icon = "\A3\ui_f\data\map\markers\nato\respawn_plane_ca.paa";
        texture = "\A3\ui_f\data\map\markers\nato\respawn_plane_ca.paa";
    };
};

But setMarkerType and setMarkerTypeLocal can not be used with this new class, so we're left constrained to vanilla CfgMarkers or creating an addon with config.cpp which is highly inconvenient.

Proposed syntax: "MarkerOne" setMarkerTypeLocal ["test_marker",true];// true - first try getting class from mission config, default: false
Proposed usage: Mission with markers of your own design.

Please add. Thank you.

Details

Severity
Trivial
Resolution
Open
Reproducibility
N/A
Operating System
Windows 10 x64
Category
Scripting

Event Timeline

Asmo created this task.Jul 13 2022, 11:50 AM
Asmo updated the task description. (Show Details)Jul 13 2022, 12:15 PM
Asmo added a comment.EditedJul 13 2022, 1:25 PM

The difference with this ticket is that I do not suggest mixing this functionality into main syntax but to add an alternative one which should probably solve any compatibility issues.

This comment was removed by LouMontana.