Correcting excessive attachment to skinid

Hello! I am writing here to make a small request. In its current version, the plugin is heavily dependent on the presence of a skinid for an item, which is essentially a flawed idea. A custom item is a combination of a short name, skin ID, and item name. Relying solely on the skin ID invariably leads to problems. For example, I use CID for custom items as a single control centre for all items. The key for it is the short name, and the skin ID for custom items is generally 0.

It would be great if you could add a more detailed configuration for custom items, linking to the full description of the ‘item definition’ instead of using only skinid. If this is not feasible, then at least add a checkbox, similar to ‘CID’, which separately takes the custom shortname of items for CID.

In general, the ideal option would be if you could register custom items for CID from your plugin, as at least one of the options. Then you wouldn't need to have some kind of plugin layer that registers items for the library, and you would control the items directly from your plugin.

Thank you in advance!

The skinid-based system will not be changed. Thank you for the suggestion

Okay... What do you suggest doing with this legacy logic? Perhaps you could simply call the method for obtaining the actual item skin and link your outdated logic to it?

Or, you could decide not to do anything related to changing the plugin and provide the product ‘as is’?