Just curious bout doctrines...

[Guest]

Welcome, Guest. Please login or register.
Did you miss your activation email?

1 Hour 1 Day 1 Week 1 Month Forever

Login with username, password and session length

[Freek]

I'm just wondering what exactly goes into implementing a doctrine, eg what do you have to type to allow rifles zooks (heavy weapons).

I'd be interested in seeing all the SCAR code (or whatever) for that.

[Scyn]

First you make an upgrade in RGD format. eg: 'item_bazooka' which contains a list of things that upgrades normally require. In this case Our action for this upgrade would be to add an item. So we'd add to our actions, a slot_item\add. Now the slot item action must be linked to a particular weapon. This case the Bazooka.

weapon\allies\ballistic_weapon\infantry_anti_tank_weapon\m1_bazooka_atw.lua

A simple upgrade like this has no requirements as we're not modifying the weapon or unit. etc etc just adding an item. So our upgrade is done.

Afterwards we have to add the upgrade to the .luaconsts which is where the scar takes place. I can't really go into very much detail. but here's the jist of it. Obviously these won't fit in here correctly, but normally all these are on separate lines. This is what the code will look like.

BAZOOKA_SINGLE    = BP_GetUpgradeBlueprint("upgrade/_europeinruins/us/items/item_bazooka.lua"),

So here's our Upgrade we just made correctly linked to the RGD. Basically the program wants to know where to pull the information from and that's how we do it, through scar.

And this is how your battalion looks for every unit. Obviously not this exact way of course. Everytime you click something in the launcher it automatically fills in these slots with the information you asked it to process.
{
sgroup = makeSGroup("SGroup108"),
transport = 0,
bp = EIRSBP.US.RIFLEMEN,               
exp = 0,
popcap = 5,
upgrades = {EIRUPG.US.BAZOOKA_SINGLE}
},

There's actually a lot more steps that go into making a doctrine ability, but that's the basics for a simple weapon upgrade.