No, and even if I did, I really doubt there's anywhere more than 5% of users who ever bother to read notes/changelog and even less would read on-site comments. For the reference, two companion addons promiently featured at the top of docs have 10k downloads combined over their entire lifetime - that should give good estimate on how many people would react to any such request.
There's 7k downloads in a hour already. Previous alpha got 257k total which is clearly in line with other release versions, not alphas. As you can see from all files list, other alphas hardly ever rise to 10k through their entire lifetime, so I don't know what's exactly is going on.
Other sites I've seen generally offer online HTML-form to fill for such data, but Curse just sends you to PDF. Can you please explain in more details what I'm supposed to do with it? Print out, fill with pen, scan and send as image? Or is there more convenient way to fill it electronically?
I've released an alpha tonight - dd7e31478690-alpha, and as you can see from https://wow.curseforge.com/projects/garrison-mission-manager/files, it got more than 40k downloads in less than a day. As you can also see from the list, no other alpha have such high numbers (with rare exception where one or two alphas stayed as latest posted file for months). Is there something strange going on?
Makrdown spec says that now other markdown commands are processed inside code block, but this displays "showtooltip" line as header and breaks code block early.
I used to tag all my addons like vN - v1, v2, v3, etc... All intermediate commits used to be packaged as alpha and all tags as releases. For some reason last time I tried that it didn't work anymore. I've just tagged https://repos.curseforge.com/wow/oocdo with "v4" and according to https://wow.curseforge.com/projects/oocdo/files file got packaged with "v4-alpha" and have alpha icon. Did something change and do I need to tag files differently now?
0
Any news on this? Almost 6 months passed and I still can't attach .lua without resorting to renaming it to .txt.
0
No, and even if I did, I really doubt there's anywhere more than 5% of users who ever bother to read notes/changelog and even less would read on-site comments. For the reference, two companion addons promiently featured at the top of docs have 10k downloads combined over their entire lifetime - that should give good estimate on how many people would react to any such request.
0
There's 7k downloads in a hour already. Previous alpha got 257k total which is clearly in line with other release versions, not alphas. As you can see from all files list, other alphas hardly ever rise to 10k through their entire lifetime, so I don't know what's exactly is going on.
0
Just posted yet another alpha: d67566c91cf2-alpha. And it seems like it too got served as release with 1,6k downloads in first 30 minutes.
0
Other sites I've seen generally offer online HTML-form to fill for such data, but Curse just sends you to PDF. Can you please explain in more details what I'm supposed to do with it? Print out, fill with pen, scan and send as image? Or is there more convenient way to fill it electronically?
0
I've released an alpha tonight - dd7e31478690-alpha, and as you can see from https://wow.curseforge.com/projects/garrison-mission-manager/files, it got more than 40k downloads in less than a day. As you can also see from the list, no other alpha have such high numbers (with rare exception where one or two alphas stayed as latest posted file for months). Is there something strange going on?
0
Just to check, will you guys be fixing it to be more conforming to specs?
0
Yes, this helps as workaround for # on first line only. But it is still not how markdown supposed to work.
0
I've tried to add a macro example in project description like:
(Ugh, that's 3 backtick on both lines below - editor doesn't let me write them for some reason)
``````
#showtooltip something
/run whatever else
```
Makrdown spec says that now other markdown commands are processed inside code block, but this displays "showtooltip" line as header and breaks code block early.
One more problem, line breaks show correctly in code blocks on CurseForge, but disappear on Curse. Compare any multiline examples in https://wow.curseforge.com/projects/oocdo and https://mods.curse.com/addons/wow/oocdo.
0
Oh, I can edit both name and status? That's nice. This will do for now, thanks.
0
Do I need to do anything for file to be repackaged correctly later or will it be picked up automatically?
0
I used to tag all my addons like vN - v1, v2, v3, etc... All intermediate commits used to be packaged as alpha and all tags as releases. For some reason last time I tried that it didn't work anymore. I've just tagged https://repos.curseforge.com/wow/oocdo with "v4" and according to https://wow.curseforge.com/projects/oocdo/files file got packaged with "v4-alpha" and have alpha icon. Did something change and do I need to tag files differently now?
0
Successfully pushed both GMM and ldb-wowtoken too. Thanks for fixing it!
I'm interested what problem was considering it used to work for a short time with new repo addresses.
0
I can't push my other addon ldb-wow-token too.
0
7 commits, 3 files modified, no new files.