This has been a requested addition for a while now, so here it is!
CustomModelData Support CustomModelData is now supported by OmniTool. You can enable this by updating to the newest version of the config (make sure you take a backup first), toggling "tool.useCustomModelData", and then editing the section under "tool.customModelData", where you can add different customModelData tags for each tier of tool: wood, stone, etc... Anything else having to do with CustomModelData, ie resource packs, needs to be done how you would normally do that. You can also see the CustomModelData tag for the item if you enable the "debug-mode" field in the config, and executing "/nbtdebug". You can use this to verify that each of your tools are being imported properly in your custom resource pack. If you decide to change your CustomModelData after initially setting it, all existing OmniTools will update to the new data the next time they are updated, whether that be by breaking a block, or hitting a player/entity.
Reload Command It has been brought to my attention that reloading the plugin server-side would be a beneficial feature as well, so you can now reload the plugin by executing "/omni reload". In this case, "omni" would be replaced by whatever your "commands.tool.base-command" is set as. Please note, commands will not update when you reload the server, only cosmetics, like CustomModelData, names, lores, and toggles.
Additional Bug Fixes You can now name your OmniTools a default name by editing the "tool.name" field in the config.
You can now use hex values in the lore for OmniCrystals, this was a bug that I overlooked when first implementing crystals in the recode for update 2.0.0.
If any bugs are encountered with the plugin, or you have any suggestions, please reach out over Spigot DM's or Discord (@subnet.mask)