skript-itemsadder 1.6

> [!CAUTION]
> This update contains a lot of breaking changes. PLEASE read the breaking changes below.
>
> First off, the biggest one, `custom` is no longer a required option in syntax. it is now optional.
> For example, `set {_s} to custom item "namespaced:id"` is no longer valid.
> I made this change because I felt that calling the item "custom" wasn't the best descriptor.
> So, you must either include `ia` or `itemsadder` in your syntax. e.g. `set {_i} to itemsadder item "namespaced:id"`
> 
> The `Get Action` and `Get Block Face` conditions have now been replaced with event values in the Custom Block Interact event.
>
> The `Block Clicked` condition has been deleted entirely, I felt that this condition was not really necessary.
> 
> The `Replace Block` and `Replace Furniture` effects are now embedded into the place itemsadder block/furniture syntax, therefore these effects have been deleted.
>
> The `Get Block Clicked` expression has been deleted, not sure why it was added in the first place.
> And thats it for the breaking changes! (sorry not sorry 😅  )

And now on with the real additions!

> [!IMPORTANT]
> Starting off with the biggest addition this update, the aliases system!
> Aliases are automatically generated when you start up your server.
> These aliases are able to be used in syntax like normal Skript items (sorta), e.g. `obsidian sword` 
> These cannot be used in the normal Skript syntax unfortunately.
> This means you will still have to use skript-itemsadder syntax when using these aliases.
> 
> So what does this mean for the existing string-based syntax? e.g. `give player itemsadder item "namespaced:id"`
> The string-based syntax is still there, aliases are just an optional little gimmick that makes the addon more fun to use.
> These aliases are stored in the `aliases.yml` file inside the plugin's folder.
> However, aliases cannot be edited.
>
> This is how you can use them:
> `give player itemsadder item obsidian sword`, this is similar to existing Skript syntax that you are all used to!
> `on break of itemsadder block reinforced obsidian:`, these may also be used for events.
> You may find all the syntax that aliases may be used for on SkriptHub/SkUnity by looking for the `customitemtype` type!

Bug Fixes:
- ItemsAdder Item expression no longer requires more then 1 item to be used,
- Stack Traces to do with sending information between skript-itemsadder and ItemsAdder have been fixed.

Additions:
- Damage effect effect (incredible name) - Plays the red damage effect on an ItemsAdder entity.
- Update HUD effect - update the player's currently enabled HUD. 
- You may now place a crop using the place block effect.
- Placing a block or furniture will now replace the block/furniture if there is a block/furniture in the same position.
- HUD exists condition - check if a HUD exists
- HUD is visible condition - check if a HUD is visible to a player.
- Is Fully Grown condition - check if an ItemsAdder crop is fully grown.
- Emote Event - called whenever someone starts emoting
- Crop Age expression - get or set the age of an ItemsAdder crop, or get the maximum age.
- ID expression - get the Namespaced:id of an ItemsAdder item/block/entity

Miscellanous:
- Added the Aliases auto generator
- Fixed the update checker, turn it on or off in config.yml
- Added a SkriptItemsAdder command, which can show you info, or reload the config.yml

This is version 1.4.1, a small bug fix update

FIXED:

• some conditions/expressions not being locked to an event

REMOVED:

• Tool Usages effect, caused me a lot of issues to try and fix, very sorry. It may return in the future.

KNOWN BUGS:

• the Replace Custom Furniture effect can be a bit finicky with furniture's that aren't 1x1x1, I have no idea how to fix this, as ItemsAdder's API isn't very concise.