• Hi Guest!

    We are extremely excited to announce the release of our first Beta1.1 and the first release of our Public AddonKit!
    To participate in the Beta, a subscription to the Entertainer or Creator Tier is required. For access to the Public AddonKit you must be a Creator tier member. Once subscribed, download instructions can be found here.

    Click here for information and guides regarding the VaM2 beta. Join our Discord server for more announcements and community discussion about VaM2.
  • Hi Guest!

    VaM2 Resource Categories have now been added to the Hub! For information on posting VaM2 resources and details about VaM2 related changes to our Community Forums, please see our official announcement here.

VaM 1.x how come some paid looks have the same number of views and downloads?

Threads regarding the original VaM 1.x
Joined
Jun 17, 2025
Messages
28
Reactions
31
Is this a bug or how is this possible? When sorting paid looks on downloads the 3 top results all have the same number of views/downloads and have extreme numbers at that.
1756132095534.png
 
The Vam hub doesn't track actual downloads from an external site. It can't. I believe it's counting clicks on "Go to Pay Site" rather than actual downloads. Those numbers are meaningless for paid resources.
 
The Vam hub doesn't track actual downloads from an external site. It can't. I believe it's counting clicks on "Go to Pay Site" rather than actual downloads. Those numbers are meaningless for paid resources.
So every single one who clicked those models also clicked "go to pay site", that doesn't make any sense
 
Is this a bug or how is this possible? When sorting paid looks on downloads the 3 top results all have the same number of views/downloads and have extreme numbers at that.
View attachment 519217

It is because when the Hub detects a download count (hub + vam + dependencies) that is higher than the view count (view count is just page views on the hub), then it will update the view count to match the download count. The reasoning is: How could someone download the content without viewing the resource? If we adjusted this, many resources' view counts could drop significantly, so we chose not to change it.
 
It is because when the Hub detects a download count (hub + vam + dependencies) that is higher than the view count (view count is just page views on the hub), then it will update the view count to match the download count. The reasoning is: How could someone download the content without viewing the resource? If we adjusted this, many resources' view counts could drop significantly, so we chose not to change it.
Ahh okay that makes some kind of sense, ty for the info!
 
Back
Top Bottom