Back to minecraft.net

A feedback area designed for scripting and mods suggestions and feedback. Please note bug reports and support issues will be removed.

← Scripting and Mods
160
Follow

[Modding API] Extensive modding support into the existing data pack framework

Shortened version:

A (promised) Minecraft modding API is a feature that has been extensively requested over the years and is still being requested. This is mainly because an official (or officially supported) API would solve some of the problems that exist with the currently standard API used for modding (Forge) that arise from the unofficial status of the API. The biggest of these problems that arise are the fact that the API (shortly) lags behind the current version of the game. Another problem that ties into the developmental problem, is that making an official API would make mods more backwards (or forwards) compatible with updates. There are of course many ways to go about implementing a modding API into Minecraft, but I will narrow it down to two routes: 1) Starting an official collaboration with Forge, 2) implementing (extensive) modding support into the existing data pack framework.

 

What

An official modding API supported or created by Mojang for Minecraft, either by working together with the Forge team, or implementing extensive modding support into the existing data pack framework.

 

Why

A (promised) Minecraft modding API is a feature that has been extensively requested over the years and is still being requested. This is mainly because an official (or officially supported) API would solve some of the problems that exist with the currently standard API used for modding (Forge) that arise from the unofficial status of the API.

The biggest of these problems that arise are the fact that the API (shortly) lags behind the current version of the game. If an API would be supported by Mojang, this wouldn't be much of a problem, since updates could be created with compatibility with the API in mind, or at the very least have the development of the compatible version start when the development of a new updates starts, rather than when it is finished.

Another problem that ties into the developmental problem, is that making an official API would make mods more backwards (or forwards) compatible with updates. This would cause modders to have to rewrite less of their mods after each update, and allow them to update their mods faster, and make their mods more extensive, without having an updating burden that slows them down.

Finally: having modding support without having to rely on an external API would contribute to the ease of modding, the ease of installing mods and the stability of those mods. These factors combined could also contribute to the spread of the use of mods, contributing to the longevity of the game.

 

How

There are of course many ways to go about implementing a modding API into Minecraft, but I will narrow it down to two routes:

1) Starting an official collaboration with Forge

This would be the fastest route to an official modding API. The existing Forge API would be implemented into the game, and (parts of) the Forge team would have a close collaboration with the Mojang team to ensure compatibility with the base game, even during development. This option would also make it easier for the current modding community to move to an official API. The biggest problem with this option is that many problems can arise from the collaboration with Forge, as they would have a complicated relationship.

2) Implementing (extensive) modding support into the existing data pack framework

This route would be a more complicated route to implementation, both for the modding community and the Mojang team, but would in the long run make things less complicated. It would involve adding support for (completely) custom blocks, items, gui's, dimensions and other features (for example: cubic chunks, magic power dependant on chunk area, etc) to the existing data pack structure. The biggest con with this route, though, is that the current modding community would have to migrate. This problem can be solved, however, by making the new modding API compatible with the mods created for the old, or at least creating an extension that allows that (or working together with the Forge team to make such an extension for the first few updates so the transition is smoother).

 

 

Avatar
Registered User shared this idea

12 Comments

Please sign in to leave a comment.

Date Votes
Sorted by oldest
  • 8
    Registered User commented
    Comment actions Permalink

    It would be almost worthless unless it downloaded required files on connect so I wouldn't have to get external mod files. Otherwise it would be the current state of forge.

    This seems to be the answer to most of anything in this feedback forum. If we had a modding API we wouldn't need to post things here.

    It makes me frustrated that this only has 3 votes.

    Edit: 4 votes.

  • 4
    Registered User commented
    Comment actions Permalink

    This is really what the game needs. Minecraft has always been about the mods for me since I first purchased the game back when it was transitioning from alpha to beta. A major annoyance is that there is always a massive lag between the game updating and the mods updating (minecraft changes tend to break minecraft forge and require complete overhauls). A consistent official modding API would allow modders to focus on developing and balancing content for their mods rather than porting their mods to newer versions of the game. If the API is consistent it can even be a "workshop" like environment where modders can upload their mods and users can download them (and will just work with their version of MC).

  • 3
    Registered User commented
    Comment actions Permalink

    This is the thing I want most. Minecraft is an open world game that has a lot of potential. Most of the things people ask for will probably never be in the game, which is why I think official mod support is important.

    Also fabric has its own API, so Mojang should collaborate with them too.

  • 3
    Registered User commented
    Comment actions Permalink

    This is one of those posts that I wish I could add 1,000 votes to on the spot.

    I've been developing a minecraft server hoping for a clean and smooth but modded experience, without every player having to download a mod (dangit optifine keeps breaking). I've had to use datapacks and a resource pack for most of the additions, so that the clients can see all of our features, but still so many things have had to be dropped and are only visible on modded clients because there's no feasible performance-friendly way to do them otherwise (random mob variants). If there were more extensions for the datapack system, including creation of custom entities, blocks, and items, many more servers would spring up around these features. If there were more extensions for the resource pack system, including creation of custom armor models and entity models to facilitate the datapack features mentioned above, that would also open many windows (and mac lol), even without the new datapack features. I hope that Mojang will consider this, and you have my vote. (Mojang if you're reading this hi, and thank you for your time)

  • 2
    Registered User commented
    Comment actions Permalink

    Yes, it is also a problem to me that forge must show ads and try to download through an adfocus link, when a large portion of the Minecraft community is dependent upon it. Minecraft should at least fund it, if they don't provide their own modding API.

    The approach I would prefer is if they made their own modding API, and shipped it with the game. They could include mods in the marketplace, and you could select them in the profile creator in the launcher. Existing mods could be placed on the marketplace for free, and people could make mods and sell them for money on the marketplace.

    These are a lot of features to ask for, but the first big step is an official modding API.

  • 2
    Registered User commented
    Comment actions Permalink

    I hope it would be able to get on all versions of MC. 

  • 2
    Registered User commented
    Comment actions Permalink

    Make sure you retitle the post to [Java Modding API] because a modding API is being developed for bedrock, but this post is about the java edition.

  • 1
    Registered User commented
    Comment actions Permalink

    It is (compared to many other posts) quite a new post, so I'm sure that it'll have more votes in due time (if people want this ofc).

  • 1
    Registered User commented
    Comment actions Permalink

    PSToxThicc, I think that's a great idea. Unfortunately I suffer from a bug on the feedback website that doesn't allow me to log in to the account I made this post with (it logs me in on a Microsoft account instead), so I can't change it... I contacted support about half a year ago for this, but I haven't heard back from them. :/

  • 0
    Registered User commented
    Comment actions Permalink

    I think this is what Minecraft is missing and it would be a great step forward for the whole community.

  • 0
    Registered User commented
    Comment actions Permalink

    I agree

  • 0
    Registered User commented
    Comment actions Permalink

    I personaly beliv ethat i perfore the curent system of quilt plus modrinth launcher also people will want to extend it but they cant.Also if a api is used its a "plug-in" not a "mod" as it dosent modify the game code(