- Level
- Intermediate
- Before you start
- A multiplayer scenario, a small picture you made yourself, and a short WAV, AIFF or Ogg Vorbis recording you own. Editing existing assets does not require a tags folder.
- You will make
- An existing bitmap with a recognizable replacement and a sound permutation using your own recording.
Shortcuts use Ctrl; Cmd also works on macOS, and Alt is Option. Keep the pointer over the viewport for editing shortcuts. Save before switching projects.
Choose assets with an observable use
Save as courtyard_assets. Pick an object or surface you can find easily in play. In Tags, follow its render model's material to the shader and the shader's bitmap reference; Open in Assets opens the bitmap. This avoids replacing a similarly named image that the visible material does not actually use.
A replacement affects every use of that bitmap in this map. Use tag duplication and reference changes when the other uses should keep the original. For the first exercise, choose a simple 2D color texture, not a normal map, cube map or texture array.
Import a recognizable picture
- Inspect the existing imageIn Assets → Textures, select the bitmap and note its image number, dimensions, kind and format. A bitmap may contain several images.
- Make a simple replacementCreate a high-contrast checker or a color grid in your image editor. Use the existing image's dimensions for an easy comparison. Save it as a PNG outside the game's installation.
- Import it into the chosen imageIn Export and import, enter the picture's path and choose Import. The image is converted to the existing texture's size and format and gets a mip chain. Check the preview.
- Save and rebuild the playable resultSave the scenario and compile the map. Open the saved map to check the replacement in the game. An updated Assets preview is not proof that the currently running map has reloaded its texture.
- Inspect near and farWalk toward the surface and back away. Check orientation, transparency where used, and the appearance of the lower-resolution mip levels.
Replace one sound permutation
- Choose a sound you can triggerIn Assets → Sounds, select an easily recognizable sound and one of its Permutations. Use Play to identify it. Avoid a long looping ambience for this first check.
- Use your own short sourceMake a brief original recording, such as a spoken marker or a tone. Name its WAV, AIFF or Ogg file in the path field. Match the intended mono or stereo use.
- Replace only the selected permutationChoose Import into the permutation. The Kit converts audio to 16-bit at 48 kHz with the permutation's channel count, then reloads the map. Import into every permutation is a different, broader change.
- Listen to the imported versionSelect the changed permutation and use Play. In a playtest, perform the action that uses that sound. A sound with several randomized permutations may still play its other recordings.
- Keep the bank with the packageSave and compile. The generated sound bank is part of the mod; do not send only the map file and omit the bank.
Replacing and creating are different workflows
| Task | Use | What it requires |
|---|---|---|
| Replace an existing bitmap image | Assets, the selected image's Import control | A picture; the existing tag supplies its format and dimensions. |
| Create a bitmap of a new size or usage | Make again from pictures, or File → Import Tags | The correct Editing Kit tags folder; inspect Usage and the import report. |
| Create a model | File → Import Tags with a JMS, FBX, glTF or GLB file | The tags folder and a supported model source. OBJ is an export format only. |
| Make a HUD ammunition meter or symbol | File → Ballistic Meter or File → Symbol Fonts | One picture of a round, or of a symbol. See symbols and ammunition meters. |
| Replace existing audio | Assets, Import into the permutation | Your audio source. The package carries its bank. |
| Build a new sound from source | File → Import Tags | The tags folder and source audio; this is a whole-map workflow. |
Editing existing images and sounds can travel with a recipe, together with their added data. New tags and source imports through Import Tags generally require the whole map. Read the Compile panel's explanation rather than assuming the download is small.
Check the saved assets
- Reopen the scenario and confirm that the image replacement and sound edit return. Keep the entire project folder, including its imported media.
- Open the compiled package and observe the texture in its actual material. Trigger the sound in play, as well as in the Assets preview.
- If the sound seems unchanged, check the selected permutation and the tag that the gameplay event actually uses. If the texture is unchanged, check its material reference and reopen the saved map.
- If you exported an existing asset for personal editing, keep it local. Only distribute material you have the right to share; an export does not change its ownership.
Next step
Add a scripted event. Reference: textures, sounds, source imports.
