-
Notifications
You must be signed in to change notification settings - Fork 369
Description
Please confirm the following.
- I checked the existing issues for duplicate feature requests
- I have checked that this feature request is not on our roadmap
What parts of Modrinth is your feature request related too?
No response
Is your suggested feature related to a problem? Please describe.
This proposal focuses on introducing an age-based content classification system for Modrinth,
designed to protect minors and improve default content discovery without removing or censoring
any projects. It is intentionally decoupled from political, legal, or regional enforcement concerns,
and instead addresses a platform-level design gap related to user safety and age-appropriate access.
Age-Based Content Classification in the Minecraft Mod Ecosystem
1. Introduction
Minecraft is officially rated 7+ / 10+, and a large portion of its player base consists of minors.
However, major mod distribution platforms currently lack a formal age-based content classification system, which creates a structural risk in content discovery and distribution.
This is not a moderation failure of individual mods, but a platform-level design gap.
2. The Core Problem
On platforms like Modrinth, the following content types coexist without separation:
family-friendly mods
technical and optimization mods
horror and extreme violence mods
sexualized or fetish-adjacent mods
Without age-based filtering:
minors can access inappropriate content without intent
recommendation systems surface all mods equally
search and trending systems amplify discovery
moderation reports are ineffective in “gray area” cases
3. Concrete Examples (Non-Accusatory)
Mods such as:
Giantess Toki and More
Wildfire Female Gender Mod
do not necessarily violate platform rules, but are clearly unsuitable for minors.
This proposal does not call for removal or censorship, but for proper classification and access control.
4. Discovery Is the Real Risk
The primary issue is not intentional access, but algorithmic discovery:
external recommendations (YouTube, social media)
mod launchers aggregating multiple sources
trending and “recommended” sections
Users often encounter this content passively, not by searching for adult material.
5. Proven Industry Solution: Roblox Model
Roblox faced the same challenge and implemented age-based experience groups:
All Ages
9+
13+
17+
Key point:
Content was not removed — discovery and access were gated.
This model is already legally and socially validated.
6. Proposed Technical Model for Modrinth
6.1 Mandatory Age Declaration
Accounts must declare date of birth (DOB)
Age group is calculated automatically
Accounts without DOB:
restricted to All Ages content
or blocked from downloads entirely
6.2 Content Classification
Mod authors assign one category:
All Ages
13+
16+
18+
18+ content includes:
sexualized content
fetish-oriented themes
content clearly unsuitable for minors
6.3 Platform Behavior
For 18+ content:
hidden by default
excluded from:
Trending
Recommendations
Homepage
accessible only if:
account is 18+
explicit opt-in filter is enabled
content warning is displayed
7. “But Users Can Bypass via Third-Party Launchers”
This is true — and irrelevant to platform responsibility.
No platform can prevent:
piracy
API bypass
third-party redistribution
What matters is reasonable protection:
preventing accidental exposure
limiting default discovery
demonstrating due diligence
This is the standard applied to:
Roblox
Steam
App Store / Play Store
YouTube
8. Why This Is Urgent
Without an age-based system:
moderation remains ambiguous
reports cannot resolve gray-area content
parental trust erodes
legal and corporate pressure increases
future enforcement may be abrupt and harmful
Proactive classification avoids reactive censorship.
9. Conclusion
Age-based classification is not censorship.
It is content separation, user safety, and platform responsibility.
Implementing this system:
protects minors
protects creators
protects Modrinth
preserves freedom while adding structure
This is a necessary evolution of the mod distribution ecosystem.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response