Sth last, cause i'm not using GMCM (prefer the manual way), at the config file its set as "SpriteDataKey": "voltaek.ColoredHoneyLabels_default_honey_full_label",. What's the command for full label with lid? "SpriteDataKey": "voltaek.ColoredHoneyLabels_default_honey_full_label_with_lid",?
For v2.0.0 the 5 built-in options for the Honey Sprite option ('SpriteDataKey' in the config.json) are: voltaek.ColoredHoneyLabels_default_honey_full_label voltaek.ColoredHoneyLabels_default_honey_mini_label voltaek.ColoredHoneyLabels_default_honey_full_label_with_lid voltaek.ColoredHoneyLabels_default_honey_mini_label_with_lid voltaek.ColoredHoneyLabels_default_honey_lid_only
The reason I say in the Description that it's highly recommended to use GMCM for the options (or at least for the Honey Sprite option) is because these values are inherently long and complex since they have to be both descriptive and more importantly unique among my mod and any other mod that integrates into it.
Adding to that, even if I can fairly easily list these values from my mod, other mod authors aren't going to want to have these values listed out in their descriptions for the same reasons. And telling users to manually dig through the files of another mod that has added integration with mine so they can find the dictionary key used with `EditData` to add their entry into my mod's dictionary data asset is asking far too much of someone that just wants some fun colored honey sprites and doesn't already know how Stardew modding works.
So it's better for everyone if users just use GMCM to at least see the the list of options with "nice" display names and to change the config values. They can obviously back up their config.json file so they at least know the value of the honey sprite option they chose if they want to manually restore their config later.
Yap i get it, it wasn't hard to guess it anyway. It's just that I'm used to manually edit things in any game i've played with mods
Btw, does it play good with Better Honey Mead? Its config option includes both mead & honey sprites (asked the author if he can seperate the two, waiting for a reply, if any) & at its mod description has the compatibility warning: "If you use a custom texture pack, this mod will still override the default and colored sprites for both honey and mead. If you want to use the custom textures, you will need to put together a Content Pack containing the custom sprites and a content file similar to this:......"
I believe it had worked fine alongside Better Honey Mead in my testing. It would be best if you disabled that mod's colored sprites in its config to give the best chance of avoiding conflicts, though.
14 comments
Great job, tnx
Full Label + Lid is awesome!
Great job once more!
voltaek.ColoredHoneyLabels_default_honey_full_label
voltaek.ColoredHoneyLabels_default_honey_mini_label
voltaek.ColoredHoneyLabels_default_honey_full_label_with_lid
voltaek.ColoredHoneyLabels_default_honey_mini_label_with_lid
voltaek.ColoredHoneyLabels_default_honey_lid_only
The reason I say in the Description that it's highly recommended to use GMCM for the options (or at least for the Honey Sprite option) is because these values are inherently long and complex since they have to be both descriptive and more importantly unique among my mod and any other mod that integrates into it.
Adding to that, even if I can fairly easily list these values from my mod, other mod authors aren't going to want to have these values listed out in their descriptions for the same reasons. And telling users to manually dig through the files of another mod that has added integration with mine so they can find the dictionary key used with `EditData` to add their entry into my mod's dictionary data asset is asking far too much of someone that just wants some fun colored honey sprites and doesn't already know how Stardew modding works.
So it's better for everyone if users just use GMCM to at least see the the list of options with "nice" display names and to change the config values. They can obviously back up their config.json file so they at least know the value of the honey sprite option they chose if they want to manually restore their config later.
Hope that makes sense.
Btw, does it play good with Better Honey Mead? Its config option includes both mead & honey sprites (asked the author if he can seperate the two, waiting for a reply, if any) & at its mod description has the compatibility warning: "If you use a custom texture pack, this mod will still override the default and colored sprites for both honey and mead. If you want to use the custom textures, you will need to put together a Content Pack containing the custom sprites and a content file similar to this:......"
Well, its on him from now on, ty
Or is it a default one?
Im just asking
The color of the honey label is inherited from the flower that flavored it, so blue label for Blue Jazz Honey, pink label for Fairy Rose Honey, etc.
Im just asking