Hi, I've checked the template for creating and running custom campaign, including the my_item_delivery_configurator.as and my_vehicle_delivery_configurator.as. In both files I edited this line with my own weapon (replacing L85A2 and M79 respectively):



Unfortunately the weapons remain unlocked and available in the armoury, which made sense due to the .resources file I predefined in nato.xml faction file:



I instead tried by actually creating a l85a2.weapon and m79.weapon with everything inside scripted as my mod's sdar.weapon and mx_ugl.weapon respectively. Now both weapons do not appear in the armoury until briefcase is delivered. While this works with unlocks using briefcases and shows up in the armoury buyables, they (obviously) are not used by my faction due to the .resources mentioned above.

Here's my question: is there some sort of mysterious script I'm missing that will only unlock .weapon files with the names l85a2, famasg1,sg552, etc. etc.? Also on a related topic, where is the script that modifies weapons unlock for laptop deliveries (i.e. APR, Mk23 SOCOM)? Because I don't want to have these weapons in a mod set in 2035.

Thank you and kind regards,
KetchupWarthog

You're probably looking for this vanilla/scripts/gamemodes/invasion/stage_invasion.as, methods getCommonFactionResources and getFriendlyFactionResources.

I think there's some weirdness going on here that could be handled in the *.resources files in vanilla instead. Also would make sense that these lists could be controlled with the stuff in the configurators. Would seem that this issue is limited to resources you generally want to be available for the default soldier group for all/some factions but have them disabled for the faction the player chooses for himself.

You have a few options how to get to change what happens in those methods in your mod. The first option is to simply copy stage_invasion.as to your mod and directly change these methods to fit your needs. Issues might arise if we make changes in vanilla's stage_invasion.as as the changes won't automatically apply to your mod.

The second option is to derive your own stage class from Stage, e.g. class MyStage : Stage and override those two particular methods with implementations you require and make your stage configurator create MyStages instead of Stages etc. I won't go into details how to do that here, as I might have even misunderstood the problem


MyItemDeliveryConfigurator derives from a class ItemDeliveryConfiguratorInvasion which is vanilla\scripts\gamemodes\invasion\item_delivery_configurator_invasion.as, you can see something it's doing in there. Laptop unlocks appear to use

You can have a similar method in your item delivery configurator class to override the vanilla behavior.

I looked around a little bit more. getFriendlyFactionResources indeed clears those particular weapons from friendly faction initially, it has been setup this way as Invasion, Dominance and quickmatches share most of the .resources files and it was decided that it's easy to disable some of these multimode resources by doing it in Invasion from the script.

If you're only focusing on one mode i.e. campaign, like you should, in most cases you should disable the unlockable weapons in common.resources by not listing them. Then when you unlock a weapon listed in your configurators, it will appear in your faction's resources and your bots will also start using the weapon and it'll show up in armory. (e.g. vanilla desert eagle)

If you want to have a weapon that is used by the enemies but not friendlies until unlocked (vanilla m79), you should list it in common.resources but use getFriendlyFactionResources to disable it for friendlies. That way it'll work regardless of which faction the player plays in.

If you want to have a weapon that is used by your bots from the start but which has to be specifically unlocked by the player to see it in armory, you need to setup the faction soldier groups so that there won't be any bots in the default soldier group (which is used by all players). You'd do it by setting spawn_score to 0 in the default group. Then you'd setup the default soldier group so that it doesn't include the unlockable weapons, and list the weapons in the resources for the soldier groups meant for bots.

Thank you for the quick reply, much appreciated

I went for copying and editing the stage_invasion.as file into my mod, that way only the overlay will be affected.



This method works combined with the modified stage_invasion.as works. I modified the latter like this:


In my testing playing as greenforces (who owns the MX UGL in normal matches, while SDAR is common for all) they will spawn neither weapon until unlocked, and when I play against them they will spawn with SDAR, which is as expected. Since I've only worked on one faction I haven't tested playing as greys and have them spawn with my soldiers, but they definitely show up in the armoury.

Please don't lock this topic just yet, I may run into future problems with those scripting changes. Hopefully if I get full 100% functionality I'll create a template file for others. And is there a way I can test the functionality of the heavily-scripted final mission I and II without having to run through the entire campaign? -.-

Just a question, does the ordering of weapons in invasion_all_weapons.xml affect the game? I had a crash on the Final Mission II (understandable due to the heavy scripting) and the changelog read smthg about apc2_hmg not found. Because I have to run through the ENTIRE campaign again with my mod, I won't be able to recreate or have the gamelog available. But I certainly swear modifying invasion_all_weapons.xml will cause some changes to the game

U can use /0_win to skip maps or /warp xx to go to certain map