![]() ![]() ![]() The "mainhand" slot is mapped to the "mainHand" bone of the hearthlings skeleton in stonehearth/data/constants.json. This means that the sword will be equipped in the "mainhand" slot. Notice the values for the following properties: Then, in the "stonehearth:equipment_piece" component, we have the same properties than for armor. It doesn't have a ghost JSON file in the entity_forms component, like the armor pieces, because it's not meant to be placeable. The weapon will only have a default model variant, which is the 'equipped' QB model. The other JSON file will have the usual properties for the net worth and catalog entries in "entity_data". The JSON file for the iconic doesn't have anything special. The orientation will make it face forward in the game, so that hearthlings will swing it in the correct direction: The point where the hearthlings will grab it should be at (0,0,0) on your modeling program, no matter the model size. Notice that there are 2 models, one is for the iconic/default version, and the other one will be shown when the weapon is equipped. We rename the files and folders, let's call it magic_sword, for example. We'll start by copying stonehearth/entities/weapons/short_sword to our mod. Same steps than for adding gear and armor, with some minor differences. Examples of weapons can be found inside stonehearth/entities/weapons.
0 Comments
Leave a Reply. |