How-To : Create New Deck Specializations

User avatar
Sireyn
Master Sergeant
Posts: 177
Joined: Sat 5 Jan 2013 06:57
Contact:

How-To : Create New Deck Specializations

Postby Sireyn » Tue 3 Oct 2017 10:06

Updated guide on creating new deck specializations in the Modding Suite. This assumes a basic knowledge of the Modding Suite and folder structure of Wargame, but don't hesitate to ask if you need more specific instructions.

When creating a new deck using your new specialization or CAT, you may crash when switching back and forth between filters. Avoid this by canceling "Create A Deck" and start again. This happens because the game is trying to apply your new CAT or specialization to a nation that does not use it.

New Deck Type Specializations
Spoiler : :
Step 1: Create new Localization Hash
a) Navigate to ...\Wargame Red Dragon\Data\WARGAME\PC
b) Open \510061340\510064564\ZZ_Win
c) Open the interface_outgame associated with your language
d) Create a new entry with the name you want
e) Open \430000564\430000574\ZZ_Win
f) Open the interface_ingame associated with your language
g) Create a new entry with an identical name
Keep the created localization hash code on hand


Everything else is in the gfx\everything within the usual NDF_Win
(...\Wargame Red Dragon\Data\WARGAME\PC\510064564\NDF_Win.dat)


Step 2: Create new Deck Rule, or select an existing one
a) Open 355: TDeckRulesModifier
b) Add a new entry with the rules you prefer
(if you can't get your modifiers to work, I believe it's because WMS is creating entries as "List" instead of "MapList". Use of WGPatcher may solve this, or just select an existing rule set)

Step 3: Add Deck Rule to the Rules Manager
a) Open 356: TShowRoomDeckRuleManager
b) Double click on ModifiersForUnitType
c) Add new entry with your localization hash and the deck rule you just created

Step 4: Add Localization Hash to Main List of Hashes
a) Open 352: TDeckAttributes
b) Double click on UnitTypeList
c) Add a new entry with your localization hash
d) Open 362:TShowRoomDeckSerializer
e) Double click on UnitTypes
f) Add new entry with your localization hash

Step 5: Add as Valid Deck to Main List of Combinations
a) Open 357: DeckConstraints
b) Create a new entry (center column) for every additional combination you want to be available
You should just need to add 3 variants for a single nation or coalition (CAT A, B, and C)

Step 6: Add Your Now Valid Decks to the Valid Combinations
a) Open 356: TShowRoomDeckRuleManager
b) Double click on ValidCombinations
c) Add an entry for each variant from step 5

Step 7: Add Specialization to Units
a) Open 81: TUniteAuSolDescriptor
b) Add the localization hash to every unit you want to be included in your deck type
On the unit's TUniteAuSol page, this is in UnitTypeTokens and Modules\TypeUnit\DefaultFilters\Map 3

Image
Image

New CAT Era's
Spoiler : :
Step 1: Create new Localization Hash
a) Navigate to ...\Wargame Red Dragon\Data\WARGAME\PC
b) Open \510061340\5100645646\ZZ_Win
c) Open the interface_outgame associated with your language
d) Create a new entry with the name you want
e) Open \430000564\430000574\ZZ_Win
f) Open the interface_ingame associated with your language
g) Create a new entry with an identical name
Keep the created localization hash code on hand


Everything else is in the gfx\everything within the usual NDF_Win
(...\Wargame Red Dragon\Data\WARGAME\PC\510064564\NDF_Win.dat)


Step 2: Create new Deck Rule, or select an existing one
a) Open 355: TDeckRulesModifier
b) Add a new entry with the rules you prefer (center column)
(if you can't get your modifiers to work, I believe it's because WMS is creating entries as "List" instead of "MapList". Use of WGPatcher may solve this, or just select an existing rule set)

Step 3: Add Deck Rule to the Rules Manager
a) Open 356: TShowRoomDeckRuleManager
b) Double click on ModifiersForUnitCategory
c) Add a new entry with your localization hash and the deck rule you want

Step 4: Add Localization Hash to Main List of Hashes
a) Open 352: TDeckAttributes
b) Double click on UnitCategoryList
c) Add a new entry with your localization hash
d) Double click on MapUnitCategoryToDate
e) Add a new entry with your localization hash. (A later date would include all earlier dates during deck creation. The order doesn't matter.)
f) Open 362: TShowRoomDeckSerializer
g) Double click on Categories
h) Add new entry with your localization hash

Step 5: Add as Valid Deck to Main List of Combinations
a) Open 357: DeckConstraints
b) Create a new entry for every additional combination you want, using your new localization hash
Each nation/coalition and deck type has variations for CAT's

Step 6: Add Your Now Valid Decks to the Valid Combinations
a) Open 356: TShowRoomDeckRuleManager
b) Double click on ValidCombinations
c) Add an entry for each variant from step 5

Step 7: Add Specialization to Units
a) Open 81: TUniteAuSolDescriptor
b) Add the localization hash to every unit you want to be associated with your new CAT
On the unit's TUniteAuSol page, this is in Modules\TypeUnit\DefaultFilters\Map 2

Image
Image
Last edited by Sireyn on Fri 21 Sep 2018 17:51, edited 1 time in total.

Lexi
Private
Posts: 4
Joined: Thu 20 Sep 2018 21:24
Contact:

Re: How-To : Create New Deck Specializations

Postby Lexi » Fri 21 Sep 2018 06:58

Might I suggest you post the full addresses? Just it confused me, and maybe confirm that the NDZX is the one in the folder above the first step?

What the second drop box is supposed to be saying in step 3 could also be clearer. Just um, saying cos, I'm honestly not sure. Sorry, I am kinda dumb. :P

Also this needs sicked in the guide thread.

User avatar
Sireyn
Master Sergeant
Posts: 177
Joined: Sat 5 Jan 2013 06:57
Contact:

Re: How-To : Create New Deck Specializations

Postby Sireyn » Fri 21 Sep 2018 16:44

The game certainly isn't intuitive to mod, so it can be unintuitive to explain. After hundreds of hours in the modding suite, sometimes I forget certain details.

Step 3 is the same idea for each set of instructions. Here in the Modding Questions thread, I have posted pictures explaining this step. The only difference is that you are using the ModifiersForUnitCategory instead of ModifiersForUnitType.

I've edited the instruction for, hopefully, better clarity.

Who is online

Users browsing this forum: No registered users and 1 guest