Skip to content

Should modpacks be making more revenue than their dependencies? #6752

Description

@TheBlondBoy

Please confirm the following.

What parts of Modrinth is your feature request related too?

Modrinth.com website

Is your suggested feature related to a problem? Please describe.

Recently one of my resource packs has made it into a modpack. During the month that I had increased downloads for that project, my revenue did not seem to follow that increase. After asking support why my revenue seemingly hadn't changed, they told me about the monetization breakdown in the analytics panel where I saw that a vast majority of these new downloads for the project through the modpack were unmonetized. This makes sense given most of these new downloads also come from the Modrinth app, likely from users who aren't signed into it. The ultimate conclusion here is that downloads are generally worthless when it comes to revenue generation, and this can be backed up by the analytics panel showing similar curves for both views and revenue and not for downloads.

After doing a little research and watching a video from someone who owns a modpack talking about their revenue from it, I realized that modpacks actually get paid more than the projects in them. Modpacks gain revenue from both views and downloads while dependencies only inherit downloads! Because downloads have more restrictions on their monetization and modpacks are evidentially downloaded from the app a majority of the time, these projects might as well not get anything from being in said modpack; The revenue almost exclusively goes to the modpack developer.

To me, this seems really backwards. Why are views more valuable than downloads? How come modpacks, projects that are just collections of others' projects, get more money for less work? Could someone just create a modpack out of someone else's collection of projects and effectively steal the revenue from them?

Describe the solution you'd like

Semantically speaking, it makes no sense for projects to inherit the views from the modpacks they are in; after all, they're not being viewed. To put it bluntly, why not just do this the same way CurseForge does, where the modpacks and the projects in them are all paid per download, equally?

Describe alternatives you've considered

No response

Additional context

No response

Activity

  1. Ceebug commented on Oct 4, 2026

    @Ceebug
    Contributor

    Views is ad money downloads is not ad money

  2. ianaduarte commented on Oct 11, 2026

    @ianaduarte

    2. Views is ad money downloads is not ad money

    that's kinda the point of the issue isn't it?

  3. Ceebug commented on Oct 11, 2026

    @Ceebug
    Contributor
  4. TheBlondBoy commented on Oct 11, 2026

    @TheBlondBoy
    Author

    It's less make downloads worth more and more make views worth less. Or worthless, lol.

    The problem is that modpacks get revenue based off two statistics while the projects in them only get one. So if a modpack gets viewed and downloaded, the projects only get downloaded and thus get half the revenue the modpack does. In a perfect world, anyway, since downloads are more likely to be unmonetized which only exacerbates the issue. My proposal is to just take views out of the equation entirely which would involve just not monetizing views, though that is a pretty site-wide change and would probably warrant a separate discussion over the revenue system. (e.g, Why are views incentivized over downloads?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions