06. Weapon Models per Style

The Models per Style system allows you to dynamically swap a weapon's visual 3D model depending on the player's current combat style (stance).

💡 What's New in v2.2: I have completely deprecated the old, complex "Item Socket" channel system. Model overrides are now declared directly and cleanly by mapping the Combat Style to the target Model Path, making development significantly faster!

---

📁 File Location & Naming

Place your configuration files inside your resource pack or mod assets at:
assets/<mod_id>/weapons_model_properties/*.json

---

📄 JSON Structure & Schema

{
  "weapons_models": [
    {
      "item": "namespaces:item_id",
      "style_config": [
        {
          "style": "STYLE",
          "model": "namespaces:model_path"
        }
      ]
    }
  ]
}

📋 Parameters & Field Definitions

Field	Type	Description
weapons_models	Array	Root array containing all your weapon model override objects.
item	String	The registry name of the target weapon (modid:item_name).
style_config	Array	List of combat styles and their assigned visual overrides.
style	String	The Epic Fight combat style identifier (e.g., one_hand, two_hand, ochs, etc.).
model	String	The resource location path to the target model file (modid:item/model_name).

⚔️ Combat Application

In this case, we have a sword from the Simply Sword mod, which, when changing from Two Hand to Ochs, changes its texture

{
  "weapons_models": [
    {
      "item": "simplyswords:brimstone_claymore",
      "style_config": [
        {
          "style": "ochs",
          "model": "simplyswords:item/brimstone_claymore_blue"
        }
      ]
    }
  ]
}

🎥 In-Game Showcase https://github.com/user-attachments/assets/c71ee2db-0217-4283-9ff6-552edebc74c6

⚠️ Important Notes You can add as many styles as you want inside the style_config array for a single item. If a player switches to a style that is not specified in your JSON, the weapon will fall back safely to its default vanilla/base Epic Fight model.