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
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?
Website
Is your suggested feature related to a problem? Please describe.
No response
Describe the solution you'd like
Add a schematics section to the Modrinth App and website, as an addition to the categories such as Mods, Datapacks, and Modpacks. Here people could publish schematics, as a .nbt file or a .litematic. You could add the feature to browse and view schematics in the Modrinth App, and an ability to download / upload them straight to / from your instance's schematic folder.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
I really like this idea (mainly because I was going to say it) and some thing that could get added is a schematic version swapper, because schematics aren't 100% multi version compatible. I'm also sure a lot of people will benefit from this seeing as how there are 50 TMC servers and 5 trusted sites for existing schematics, and this can get overwhelming and difficult to get what you need.
Please confirm the following.
What parts of Modrinth is your feature request related too?
Website
Is your suggested feature related to a problem? Please describe.
No response
Describe the solution you'd like
Add a schematics section to the Modrinth App and website, as an addition to the categories such as Mods, Datapacks, and Modpacks. Here people could publish schematics, as a .nbt file or a .litematic. You could add the feature to browse and view schematics in the Modrinth App, and an ability to download / upload them straight to / from your instance's schematic folder.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: