You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The database should include information on the download count for each mod and/or file. This should be displayed when running mod.list.
The download count for a mod is a useful proxy for its quality. A mod with a download count of 10 is probably un-tested rubbish; 1,000 is probably a mod in alpha; 100,000 is probably a well-polished mod that is safe for general use.
The mod's overall download count is biased by the age of the mod - mods that have been around for a long time (i.e. JourneyMap) have download counts in the range 10,000,000 - 100,000,000. The download count of individual files is a more accurate representation of the current popularity of a mod. Therefore it's useful to have both.
I imagine that the database crawler can be easily modified to capture this information from CurseForge. I'm happy to do the feature implementation, once the data is available in the mcdex DB.
I imagine that the output in mod.list would be fuzzed to an abstract score out of 5.
i.e.:
mcdex mod.list map
JourneyMap | Popularity: 5 | Real-time mapping in-game or your browser as you explore. | https://minecraft.curseforge.com/projects/journeymap
Mapwriter 2 | Popularity: 2 | An open source mini-map! | https://minecraft.curseforge.com/projects/mapwriter-2
Xaero's Minimap | Popularity: 3 |Displays world terrain, players, mobs, entities in the corner of your screen. | https://minecraft.curseforge.com/projects/xaeros-minimap
Where the score out of 5 is logarithmic.
Up to 1,000
Up to 10,000
Up to 100,000
Up to 1,000,000
1,000,000+
The text was updated successfully, but these errors were encountered:
The database should include information on the download count for each mod and/or file. This should be displayed when running
mod.list
.The download count for a mod is a useful proxy for its quality. A mod with a download count of 10 is probably un-tested rubbish; 1,000 is probably a mod in alpha; 100,000 is probably a well-polished mod that is safe for general use.
The mod's overall download count is biased by the age of the mod - mods that have been around for a long time (i.e. JourneyMap) have download counts in the range 10,000,000 - 100,000,000. The download count of individual files is a more accurate representation of the current popularity of a mod. Therefore it's useful to have both.
I imagine that the database crawler can be easily modified to capture this information from CurseForge. I'm happy to do the feature implementation, once the data is available in the
mcdex
DB.I imagine that the output in
mod.list
would be fuzzed to an abstract score out of 5.i.e.:
Where the score out of 5 is logarithmic.
The text was updated successfully, but these errors were encountered: