|
|
## Description
|
|
## Description
|
|
|
Sets the specified CustomModelData on the item the caster is holding
|
|
Sets the specified Model/[CustomModelData](/skills/mechanics/SetItemCustomModelData) on the item the caster is holding.
|
|
|
|
|
|
|
|
|
|
|
|
|
## Attributes
|
|
## Attributes
|
|
|
| Attribute | Aliases | Description | Default |
|
|
| Attribute | Aliases | Description | Default |
|
|
|
|----------------|-------------|---------------------------------------------------------|---------|
|
|
|----------------|-------------|---------------------------------------------------------|---------|
|
|
|
| model | m | The new CustomModelData | 0 |
|
|
| model | m | The new Model | 0 |
|
|
|
| slot | equipslot, s | The [slot](/../../../MythicMobs/-/wikis/Skills/EquipSlot) to target | |
|
|
| slot | equipslot, s | The [slot](/../../../MythicMobs/-/wikis/Skills/EquipSlot) to target | |
|
|
|
|
|
|
|
|
|
### Model Attribute
|
|
|
|
The mechanic will try to set a CustomModelData if the value of the `model` attribute is an integer or if the server version does not support the new Models syntax, or a Model otherwise
|
|
|
|
|
|
|
|
That is in place in order to not break retro-compatibility, but it's best practice to only use this mechanic for setting proper Models going forward. If you want to set a CustomModelData, you should use [SetItemCustomModelData](/skills/mechanics/SetItemCustomModelData)
|
|
|
|
|
|
|
|
|
|
|
|
## Examples
|
|
## Examples
|
|
|
```yaml
|
|
```yaml
|
|
|
Skills:
|
|
Skills:
|
|
|
- setitemmodel{m=3} @self ~onUse
|
|
- setitemmodel{m=10} @self ~onUse
|
|
|
|
```
|
|
|
|
```yaml
|
|
|
|
Skills:
|
|
|
|
- setitemmodel{m=namespace:modelname} @self ~onUse
|
|
|
```
|
|
```
|
|
|
|
|
|
|
|
## Aliases
|
|
## Aliases
|
| ... | | ... | |