I just noticed that the Curseforge App thinks your version of idTip is the old obsolete one. If you search in the App for idtip it shows both versions of the addon, but no matter what I did, even fully manually deleting idTip from Interface/WTF and installing it directly from the App, would get it to realize that I have your version installed.

The best solution is for the original dev to give you full rights on curseforge, but if they're unresponsive then IMO the next best solution is for you to re-name or re-upload your version under a new Addon name. Even if you have to create an entire new Addon page to change the name I still think it's worth it in the long run; assuming you plan to continue updating it throughout DragonTown IMO you are the rightful owner of this new version.

My new name suggestion is "TooltipIDs". It's self-descriptive enough to show up in a search.

I'm not really noticing any issues on my end.. I'd have to reach out to curse and see what they advise, but as far as I can tell there don't seem to be any issues currently, the curse client is just buggy in general..

On my CF app, it's all good too, except that on every load it lists your idTip as "Modified". However a right-click+Update solves this - until the next load. I already tried to delete manually both the addon and its WTF settings to eliminate this bug but on the next load it just listed idTip as "Modified" again.

I can update it for the latest version manually so I'm ok with it.

Very weird, I'll open a ticket with overwolf and see if they recommend any changes on my end.

Just to confirm, also occurring with CF app for me as well. It's still updating correctly, and no issues. But it does appear as Modified.

I'm fairly certain addon managers (at least WowUp does) tap into the toc file(s) and use the same ids that the build script from the BigWigs team uses.

At least that's the only thing I've done for my unit frames and those get correctly picked up by both WowUp and CurseForge.

Despite that I still think the correct thing would be to rename the addon entirely, just to be on the safe side. Otherwise, we'll have a big mess if the old one gets updated at some point.

edit:
I just tested it by adding the CF id in the toc, but apparently that wasn't enough. I'm not sure why, but WowUp still doesn't pick it up after a rescan. Testing CF isn't of much use because well ... now I did modify the files.

I'd be grateful to share logs client but I don't know where can I find them.

@Zorcan2112 @ZINK-ZINK @Voxxel I've heard back from the Curse/Overwolf team and they aren't able to reproduce these issues either, they asked if there's any curse logs that can be provided, if you'd like to help you can send them to me and I'll forward them on.

If you'd like to email them directly to curse you can reference the ticket number 145209

https://support.curseforge.com/en/support/tickets/new

You can email them to [email protected]

Thanks, hopefully we can narrow this down or at least eliminate some options before trying to brute force updates to attempt resolving.

I am going to rename the addon directory however, since it does sound like something that could quite easily cause issues.

@ItsJustMeChris Pasting a pic of what I see on my end currently, iirc the same day I opened this ticket it changed from only showing the original idTip to showing your "modified community fork".

I'll fill out that curseforge ticket with the reference number, but I glanced through the curse-Log-zip and it includes some info personal enough to make me wary (like my WoW GUID, my drive directories+filenames, IP address etc) so I don't want to send those logs anywhere, especially Overwolf.

I'm all for supporting addon devs, but I do not trust Overwolf whatsoever; I only use their site and addon app because they have a monopoly and I use hundreds of addons.

If there's any other way I can help I'd be happy to though.

I'd be grateful to share logs client but I don't know where can I find them.

This pic is how to create the Log, but be wary of Overwolf imo. You do you though, I could well just be overly paranoid.

I'm not able to recreate it in any degree, and neither was Curse themselves. They said the only thing that can really help is to contact them directly with curse client logs.

Just to chime in that this is a thing that still happens to me.

Overwolf can be confused by addons with similar names, try add tags "## X-Curse-Project-ID:" and "## X-Website:" in you TOC files, it may help.
Like:

## X-Website: https://www.curseforge.com/wow/addons/idtip-community-fork
## X-Curse-Project-ID: 689652

same issue here, hence my hunting this down on github

shows up as modified then stops presenting as needing an update until i check the version history and can update from there.

I'm starting to see this bug sometimes with other addons.. Right clicking and pressing update seems to make it not an issue for me.. with these new observations I'm going to close this issue because I don't think it's isolated to just this addon and is a general curse issue..