Hero swap part 3: attachments, camera, and game data

Make a reference copy of the original

The compiled original keeps the exact values. Put a copy where CSDK 12 can open it.

1. In Source 2 Viewer, right-click the hero's .vmdl_c and choose Export as is.
2. Save it into CSDK 12's own game folder, at the same path: Reduced_CSDK_12/game/citadel/models/heroes_staging/viper/.
3. In the CSDK 12 Asset Browser, open that viper.vmdl_c.
4. Place it next to your work model, so you can read both.

Never let your own compiled model overwrite this copy. A replaced reference is a common cause of the centered camera. Your viper_work file name keeps them apart.

Pugzilla's short video Compiled Models In CSDK exports every hero this way. It takes 4 to 5 GB and slows CSDK 12 down, so one hero is enough here.

Copy attachment positions and angles

1. Open AttachmentList in both models.
2. Select standing_pivot in each model and compare Relative Origin and Relative Angles.
3. Copy the reference values wherever yours differ.
4. Repeat for crouching_pivot, near_00 to near_02, far_00 to far_02, and gunaim_00 to gunaim_02.
5. Check that the other attachments are all there too, such as aim, ability_cast, muzzle_fx, head_fx, healthbar, portrait_camera, and zipline.
6. Click Compile.

Never delete or move an attachment. If one is missing, copy it from the reference.

Add camera previews

Each camera attachment needs a preview with the right field of view (FOV).

1. In Source 2 Viewer, open the original .vmdl_c and go to the Data tab.
2. Find AttachmentCameraData. Note the FOV it lists for each camera attachment.
3. In ModelDoc, select standing_pivot through gunaim_02.
4. Right-click them and choose Add Attachment Preview.
5. Set the FOV to 90 and the screen size to 1920 by 1080.
6. Select the three gunaim_ attachments. Set their FOV to the hero's own value from the Data tab.
7. Click Compile.

The gun aim FOV differs per hero. The guides show 42 for Vyper, 50 for Billy, and 55 for Drifter. Use the number in your hero's Data tab.

Add the camera prefab

Fuji's guide adds ready-made camera data from CSDK 12. This step comes from one guide and may differ on the current build.

1. Open content/citadel/models/prefabs/camera_attachmentdata/ in your CSDK 12 folder.
2. Find camera_attachmentdata_<hero>.vmdl_prefab for your hero.
3. Add a prefab node to your model that points to this file.
4. Right-click the prefab node and choose Flatten Prefab.
5. Click Compile.

The folder is missing? Update CSDK 12. Older guides set this camera data in CS2 Workshop Tools instead.

Copy the game data

GameDataList holds Deadlock's own settings for the hero. Source 2 Viewer has written these blocks into decompiled models since version 17.0, so yours should be there already.

1. Open GameDataList in your model.
2. Compare each block with the original's Data tab in Source 2 Viewer.
3. Copy every value that differs.
4. Add any block that is missing. Use the text editor method below.
5. Click Compile.

Some heroes have extra blocks, for example for a pet or a second rig. Copy those too.

Copy a block with a text editor

Use this for any block that is missing or wrong. The health bar block is the usual one.

1. In Source 2 Viewer, decompile the original hero's .vmdl_c as .vmdl into a new, empty folder.
2. Open that file and your viper_work.vmdl in your text editor.
3. Search both files for the block name, such as CitadelUnitStatusSettings_t.
4. Replace your block with the original block. If yours is missing, paste the original next to the other game data blocks.
5. Save your file.
6. Go back to ModelDoc. It warns that the file changed outside the editor. Reload it.
7. Click Compile.

Check your work

1. Click Compile and fix any errors.
2. Count the attachments in your model and in the reference. The numbers should match.
3. Keep the reference copy. You need it again after game updates.

You cannot check the camera in game yet. Part 4 adds the animations, then you test the camera, aiming, health bar, and sounds.