Warfare GCO Compatibility

Classification profiles for Therzie's Warfare 1.9.4 and Goo's Combat Overhaul (GCO) 2.1.2. This package makes Warfare weapons use the intended GCO weapon-category settings. It is YAML only: no DLL, replacement assets, damage values, recipes, or separate balance preset.

Before enabling GCO YAML: GCO may already have 22 bundled Sword*.yml / Spear*.yml files in BepInEx/config/GooCombatOverhaul/YAML/Weapons/. They change hit-ray ranges when YAML is enabled. Back up that folder and, if you want to keep your previous effective balance, move those 22 files to a backup outside YAML/Weapons/ before turning YAML on. Keep your own profiles that you want active. Leave defaults-installed-v1.txt and defaults-installed-swordgold-v1.txt in place. Do this in each affected game profile and on your server.

Why this exists

GCO normally identifies a weapon category from its item and animation metadata. Some Warfare prefabs use animation metadata that makes GCO choose an unintended category. Consequently, a bastard sword can inherit Sledge settings, a sledge or throwing axe can inherit TwoHandedAxe settings, and changes to those GCO categories affect the wrong items. This is a classification issue; the Warfare items themselves do not need their combat stats replaced.

This package gives GCO 21 exact-prefab categoryOverride profiles:

Every profile changes only GCO's category lookup. Damage, stamina, speed, blocking and other values continue to come from your existing GCO configuration for that category. Throwing axes remain throwing weapons in Warfare; this mapping does not change their equipment rules or projectile physics. GCO's [Throwables] settings are for bomb-style projectiles and do not provide dedicated throwing-axe controls.

The other 88 registered weapons and eight shields use GCO's existing detection. In particular, DualSwordScimitar_TW and DualScytheBloodthirst_TW retain their original GCO AutoDetect category, DualAxes.

Install and activate

1. Install Warfare 1.9.4 and GCO 2.1.2 with their dependencies. Install this package on both the server and each client. With a manager that routes the package config/ folder into BepInEx/config/, the 21 files belong under BepInEx/config/GooCombatOverhaul/YAML/Weapons/. For a manual install, copy only the package's 21 .yml files there.
2. Back up your existing GCO YAML/Weapons/ folder. An existing GCO installation can contain 22 default sword/spear YAML profiles even when YAML has been disabled. Enabling YAML activates those profiles too. To keep the prior behavior for vanilla swords and spears, move the 22 Sword*.yml / Spear*.yml default files out of that folder after backing them up. Do not blindly move custom profiles you intend to use; do not delete the two defaults-installed-*.txt marker files. You do not need to delete your GCO .cfg.
3. In BepInEx/config/goo.valheim.gooscombatoverhaul.cfg, set Use yaml configs = true under [YAML Configs] on the server and on clients used for offline play. In the supplied existing configuration it was false, so none of these profiles were active. GCO 2.1.2 can enable YAML by default on a fresh install, but an existing saved setting remains yours. With Sync config = true, the server controls multiplayer configuration.
4. Fully restart Valheim and the dedicated server. Ensure the profile used to launch the game is the one you edited.

If upgrading from this pack's 0.1.0, remove its old DualSwordScimitar_TW.yml and DualScytheBloodthirst_TW.yml from the GCO Weapons folder: mod managers may leave old config files after an update. Those two profiles are absent from this archive.

Check in game

GCO 2.1.2 provides these console commands:

gco_yaml_reload
gco_yaml_validate all
gco_yaml_show held
gco_yaml_diagnose held

Hold a Warfare bastard sword, sledge or throwing axe and inspect its category. gco_yaml_diagnose held writes details to BepInEx/LogOutput.log. A weapon that already uses AutoDetect need not have a YAML profile. If no profiles load, check Use yaml configs and the active game's/server's config path. If a duplicate exact-prefab profile is reported, remove the older duplicate and reload.

Compatibility and scope

• Audited against the actual Warfare 1.9.4 item prefabs and GCO 2.1.2 YAML schema 5: 109 registered weapons (21 overrides, 88 AutoDetect) and eight shields. DualSwordScimitar_TW1 exists in the asset bundle but is not registered as a playable weapon.
• This package covers Warfare itself. Armory, Warfare: Fire and Ice, and Wizardry are separate mods and are not included.
• GCO's shield grouping already detects Warfare shields correctly. Battlehammers and GreatClub retain their detected Sledge category. Warpikes and ScytheVampiric_TW also retain GCO AutoDetect.
• CrossbowChitin_TW is the asset prefab, while Warfare's registration uses CrossBowChitin_TW; this pack does not change that registration. Check in game if it does not appear.
• The YAML structure and prefab mapping were checked statically against those releases. An in-game test has not yet been performed. Please report a specific prefab and the output of gco_yaml_diagnose held if a category is wrong.

See the separate SourceBuildKit archive for the full prefab audit and profile generator. The compatibility ZIP contains only the files needed for installation and the Hexium listing.