Limit Weapons or Rearming Possibility by historical references

[DaKerboul]

Brief Description:

Example : Prevent F-15C from rearming with AIM-120C in multiplayer when period selected is 1980s,

How does it work:

Having two switches :

• Historical Weaponry : Only allows weapons in home bases and FOBs and Carriers existing in the selected period to be usable, the rest would be disabled
• Allow Rearming (don't know if it's a mission side or server side option) on bases

And/Or having a Weapon Ban List in the same logic as Unit Ban List, example if you don't want players to go out with the Nukes on the MiG-21.

Why can't it be done in the ME quickly:

Need to set manually each armament to disabled depending on the historical theme wanted by the user, and taking a whole lot of time to modify properly.

[DaKerboul]

I've tried to come up with easy solutions, but they all lead to extremely tedious manual processing, requiring highly complex aircraft-by-aircraft arms limitation management.

In the current situation, I can generate a Desert-Storm-esque mission, but at any moment the players on the mission can take on completely unrealistic loadouts in relation to the period.

Even more so if only dynamic slots are used to facilitate module diversity.

[john681611]

Yeah... ED doesn't maintain good operational data on what units were operating in what year. They don't bother with what country either.
We maintain a dataset here: https://github.com/DCS-BR-Tools/dcs-data-miner/tree/main/customDataSets
When it comes to aircraft weapons, I hear and understand the complaint but as you noticed there isn't much I can do about it without:

1. Data on what weapon was operational when (bonus by who)
2. Enough load-outs assigned to aircraft that they have a chance of having a load-out at all that would pass restrictions

[DaKerboul]

I know DCS Liberation does something like that, but I don't know how much.

[DaKerboul]

In that case, is there any way to force players to keep their original loadout?

[john681611]

The best thing to do is to set up the airbase to only have aircraft and weapons that existed in your given era.

Btw our DB of weapons has 2963 items. No one is manually doing that....
Don't even think about mods either.

[DaKerboul]

hmm, that's a pretty big concern (at least for me), I was planning to develop a pipeline on top of the current tool that proposes missions each day with a different period, which means that I technically don't have the time each day to manually modify each of the missions (knowing that people's requests are made on the fly and the parameters (historical period, missions) are voted on by the players)...

[DaKerboul]

For the moment, apart from asking players to “play the game” and telling them to use materials that they feel are consistent with the period, I think it's going to be complicated for me.

[DaKerboul]

On the other hand, there's a good chance that this famous list of restrictions can be found in DCS Liberation (as well as the mechanics for performing the restriction).

[DaKerboul]

https://github.com/dcs-liberation/dcs_liberation/tree/develop/resources/weapons

[DaKerboul]

Or https://github.com/dcs-retribution/dcs-retribution/tree/dev/resources/weapons to be more updated

[DaKerboul]

Or adding this script to every mission : https://github.com/ZuluThreeZero/restrict-by-year/blob/wip/restrictByYear.lua

as an option just like CSAR/CTLD

[john681611]

Ok, It kinda solves the first issue but not the 2nd.

[john681611]

I think I know the retribution dev. If I can get permission to use their data I'll add it in. But how we do limitations could be difficult. We have to limit airbases as well as player and AI loadouts. If we can't find a suitable one we will have to fall back to just anything for AI. The script isn't viable because it just does warehouses.