Undo the hardcoding of the outpost deathmatch mission

[profole]

In current stable the xml for the outpost deathmatch mission is

  <CombatMission
    identifier="outpostdeathmatch"
    type="OutpostCombat"
    multiplayeronly="true"
    commonness="100"
    reward="2000"
    pointsperkill="10"
    allowrespawning="true"
    wincondition="KillCount"
    loadsubmarines="false"
    AllowOutpostNPCs="False"
    ForceOutpostGenerationParameters="colonypvp"
    AllowOutpostSelectionFromTag="PvPOutpost"
    ForceRespawnMode="MidRound">
    <LocationType identifier="city" />
    <Icon texture="Content/UI/MissionIcons2.png" sourcerect="0,768,256,256" color="243,146,55"/>
    <message text="missionmessage0.outpostdeathmatch"/>
    <message text="missionmessage1.outpostdeathmatch"/>
    <TriggerEvent state="0" delay="10" eventtag="deathmatchweapondrop" />
    <OverrideMusic state="0" type="pvp" />
  </CombatMission>

Which was changed to the following one in unstable

  <CombatMission
    identifier="outpostdeathmatch"
    type="OutpostCombat"
    multiplayeronly="true"
    commonness="100"
    reward="2000"
    pointsperkill="10"
    allowrespawning="true"
    wincondition="KillCount"
    loadsubmarines="false"
    AllowOutpostNPCs="False"
    ForceOutpostGenerationParameters="colonypvp"
    AllowOutpostSelectionFromTag="PvPOutpost"
    ForceRespawnMode="MidRound">
    <LocationType identifier="city" />
    <Icon texture="Content/UI/MissionIcons2.png" sourcerect="0,768,256,256" color="243,146,55"/>
    <message text="missionmessage0.outpostdeathmatch"/>
    <message text="missionmessage1.outpostdeathmatch"/>
    <OverrideMusic state="0" type="pvp" />
  </CombatMission>

Notably, the <TriggerEvent state="0" delay="10" eventtag="deathmatchweapondrop" /> line was removed and its most likely hardcoded into the mission/chosen map now.
I assume this is done to get around making xml stuff to check which map is being played (since the old one couldnt do that without making a new missiontype and we now need that since ruin map needs to spawn different things), but this just cant be it.

My mod "Better Outpost Deathmatch Framework" for example, used the old system to add a new custom event triggered by a custom missiontype to allow people to still play PvP vanilla while having my mod enabled.

Considering that the goal is to de-hardcode more stuff for xml modding, this shouldnt be done.
I suggest adding a new xml attribute for TriggerEvent to check against the selected map (something like "OutpostTag" or "MapTag") instead.