cw4:custom_units
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| cw4:custom_units [2022/09/05 10:05] – Fix typo Up-Level | cw4:custom_units [2025/02/14 14:57] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| [[cw4: | [[cw4: | ||
| - | ===== Overview ===== | + | ====== Overview |
| - | The basic steps in creating a custom unit needs two things | + | The basic steps in creating a custom unit needs the following: |
| - | - A Model (the thing you see on the map) | + | - A [[cw4: |
| - | - A Script (You don't see this, but it makes the model do certain things) | + | - A [[4rpl: |
| + | - [[cw4: | ||
| - | These two things are packaged in a CPACK. Each CPACK can have one or more units and scripts. Note that each model can also have multiple sub-units. A model also needs a " | + | The first two things are packaged in a CPACK. Each CPACK can have one or more units and scripts. Note that each model can also have multiple sub-units. A model also needs a " |
| - | ===== Documenting Custom Units ===== | + | Documentation is provided via the wiki. |
| + | |||
| + | ====== Documenting Custom Units ====== | ||
| :!: <color # | :!: <color # | ||
| - | An [[wiki help|extensive | + | An extensive |
| + | |||
| + | ====== Models ====== | ||
| + | |||
| + | ===== Modeling tools ===== | ||
| + | Anyone could use [[https:// | ||
| + | |||
| + | Following is a list of some free and perhaps easier tools to use. | ||
| + | |||
| + | ==== Microsoft 3D Builder ==== | ||
| + | 3D Builder is about as simple as it gets, can load some geometry and simplify it. | ||
| + | |||
| + | https:// | ||
| + | |||
| + | ==== Tinkercad ==== | ||
| + | Tinkercad is a good way to make units. | ||
| + | |||
| + | https:// | ||
| + | ==== MagicaVoxel ==== | ||
| - | ===== Getting Started ===== | ||
| - | * [[http:// | + | |
| * It's free, and doesn' | * It's free, and doesn' | ||
| - | * When you export, export as an " | + | * When you export, export as an " |
| * .vox files created by MagicaVoxel can be directly imported an in many instances result in a much smaller model with fewer vertexes - this is good for performance. <wrap info> The .vox file that can be imported is the **exported** version, not the save. It is confusing that Magica Voxel does not differentiate between the two .vox file types</ | * .vox files created by MagicaVoxel can be directly imported an in many instances result in a much smaller model with fewer vertexes - this is good for performance. <wrap info> The .vox file that can be imported is the **exported** version, not the save. It is confusing that Magica Voxel does not differentiate between the two .vox file types</ | ||
| - | | + | ==== Qubicle ==== |
| + | Another good voxel tool is [[http:// | ||
| - | * The full version isn't free. It was used for the prototype units in CW4. | + | The full version isn't free. It was used for the prototype units in CW4. |
| - | * Anyone could also use [[https:// | + | ==== AssetForge ==== |
| - | | + | A paid tool that is fully supported in the game (some units have been made with this tool) is [[http:// |
| - | ==== Importing Units/ | + | ===== Importing Units/ |
| Models exported from many external tools (Magica Voxel, Blender, etc.) can usually be imported into the game editor. **The guiding principle here is that units should be simple**((After import, the game will report on the number of vertices that the model contains.)) - Animation and many of the more advanced features are not suported. Since the game utilizes a 3rd-party package ([[https:// | Models exported from many external tools (Magica Voxel, Blender, etc.) can usually be imported into the game editor. **The guiding principle here is that units should be simple**((After import, the game will report on the number of vertices that the model contains.)) - Animation and many of the more advanced features are not suported. Since the game utilizes a 3rd-party package ([[https:// | ||
| Line 44: | Line 65: | ||
| [[http:// | [[http:// | ||
| - | ==== What ==== | + | ===== What ===== |
| The game needs both the .obj for the actual model and the texture file (usually a .png file, so make sure you have both available for import into the C-Pack editor. | The game needs both the .obj for the actual model and the texture file (usually a .png file, so make sure you have both available for import into the C-Pack editor. | ||
| Line 50: | Line 71: | ||
| The CPACK editor can also directly import the .vox files created by MagicaVoxel and this usually results in a more efficient model. If you import the .vox file, the model and texture will both be imported into the CPACK editor. | The CPACK editor can also directly import the .vox files created by MagicaVoxel and this usually results in a more efficient model. If you import the .vox file, the model and texture will both be imported into the CPACK editor. | ||
| - | ==== Considerations ==== | + | ===== Considerations |
| From a Discord conversation where @knucracker provided some insight into the import process (for a model exported from Blender) | From a Discord conversation where @knucracker provided some insight into the import process (for a model exported from Blender) | ||
| Line 61: | Line 82: | ||
| //The game uses a 3rd party model import package that attempts to create an object hierarchy from what is in the model file. The game then tries to extract meshes from that object hierarchy. | //The game uses a 3rd party model import package that attempts to create an object hierarchy from what is in the model file. The game then tries to extract meshes from that object hierarchy. | ||
| - | ==== Links to Image Repositories ==== | + | ===== Links to Image Repositories |
| Please don't use images that you do not have the rights to use, that are the property of others, have licensing fees or require attributions. Links to repositories that are not family-safe are not welcome. The sole right of decision-making rests with Knuckle Cracker. | Please don't use images that you do not have the rights to use, that are the property of others, have licensing fees or require attributions. Links to repositories that are not family-safe are not welcome. The sole right of decision-making rests with Knuckle Cracker. | ||
| Line 79: | Line 100: | ||
| - | ==== Ownership rights ==== | + | ===== Ownership rights |
| Anything you upload to knucklecracker.com website or the affiliated game servers transfers a royalty-free license to knuckle Cracker LLC. for future use in any form. You retain the copyright information, | Anything you upload to knucklecracker.com website or the affiliated game servers transfers a royalty-free license to knuckle Cracker LLC. for future use in any form. You retain the copyright information, | ||
| Line 95: | Line 116: | ||
| - | ===== Random notes ===== | + | ====== Random notes ====== |
| ---- | ---- | ||
cw4/custom_units.1662372348.txt.gz · Last modified: 2025/02/14 14:56 (external edit)
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
