leonardo_c Posted November 14, 2019 Posted November 14, 2019 Long story short. Very usually I limit/restrict to place my missions in a specific decade (70s, 80s, 90s, etc). This means going to the airbases and fiddling with each weapon you want to limit/restrict. So far, so good. What is the problem then? The problem is that at every single open beta update you will have to re-apply these settings because they get broken with the update. There will be some items with null/empty descriptions, there will be some others marked as available that you won't be able to re-arm on the re-arm/refuel menu. How to fix this? It seems rather obvious, there are some APIs like Unit:GetAmmo() that returns a LUA table, the same API works also with player units. The trick is that this API returns a string value which is different from the ones we see in the mission editor/re-arming screen. The returned values are actually the low-level implementation of the weapon. E.g. AIM_9X, RB_24j, BK90_MJ1 At this point it could be relatively straightforward to code a script that validates the player loadout against a list of allowed/restricted weapons. Is there any script already available out there that solves this problem? I could code something but if it's already out I'd rather avoid re-inventing the wheel.:thumbup: My DCS Campaigns - DOWNLOAD
Recommended Posts