Jump to content

[1.6.2] How to make mcmod.info file the right way ?


Graphicscore

Recommended Posts

Hello there I'm trying to make a mcmod.info file, I put the file below in the root of my zipped mod but Forge wouldn't load it what does I wrong :

 

mcmod.info File :

 

{
  "modinfoversion": 2,
  "modlist": [{
    "modid": "camomod",
    "name": "Camo Mod",
    "description": "Camouflage your stuff because you never gonna now what happen",
    "version": "0.1",
    "mcversion": "1.6.2",
    "url": "-",
    "updateUrl": "",
    "authors": [ "Graphicscore", "Setix", "mehrmrhr" ],
    "credits": "Code by Graphicscore and GFX by mehrmrhr",
    "logoFile": "/assets/textures/logo.png",
    "screenshots": [ "", "" ],
    "parent": "",
    "requiredMods": [ "Forge" ],
    "dependencies": [ "" ],
    "dependants": [ "" ],
    "useDependencyInformation": "true"
  }]
}

 

If i put the mcmod file in my zip Forge disable my complete mod until I delete the file !

Link to comment
Share on other sites

Thats my content now but Forge keeps disable my mod

[{
    "modid": "camomod",
    "name": "Camo Mod",
    "description": "Camouflage your stuff because you never gonna now what happen",
    "version": "0.1",
    "mcversion": "1.6.2",
    "url": "-",
    "updateUrl": "",
    "authors": [ "Graphicscore", "Setix", "mehrmrhr" ],
    "credits": "Code by Graphicscore and GFX by mehrmrhr",
    "logoFile": "/assets/textures/logo.png",
    "screenshots": [ "", "" ],
    "parent": "",
    "requiredMods": [ "Forge" ],
    "dependencies": [ "" ],
    "dependants": [ "" ],
    "useDependencyInformation": "true"
  }]

Link to comment
Share on other sites

I always have issues with the mcmod.info file so I found a work around to the file and hard coded it directly into the mod.

 

	@PreInit
public void randomName(FMLPreInitializationEvent event) //really does not matter on the name of the public void 
{
	ModMetadata m = event.getModMetadata(); //This is required or it will not work
	m.autogenerated = false; //This is required otherwise it will not work
	m.modId = "The mods id (This must match the class or it wont work)";
	m.version = "Mod Version";
	m.name = "The Name of Said Mod";
	m.url = "http://modsofficialwebsite.com";
	m.description = "Some Descriptions";
	m.authorList.add("NameofAuthor1")
	m.authorList.add("NameofAuthor2")
}

 

This can be added basically anywhere in your mod in the main class file. if you want to add more options just type m. after just wait a few seconds for some options or you can look directly into the ModMetadata class. It will have a full source of all the options. But if you really want to use the mcmod.info file it does not go directly under the .zip file. In my mod everything is under the Nexion directory so its like Nexion 1.5.zip > Nexion > mcmod.info Which is the mods ID. Hope this helps :P

A modder uses search for solutions, a coder asks for help only after looking into the main source of the game modding. A master java programmer has solutions and is helpful. Be friendly to others, they will be friendly to you (depending on how their day goes ;) )

Link to comment
Share on other sites

mcmod.info can be placed anywhere in the mod, it doesn't matter.

You should check if modid and version are the same as declared in the mod.

You can also remove any line with no info:

[{
    "modid": "camomod",
    "name": "Camo Mod",
    "description": "Camouflage your stuff because you never gonna now what happen",
    "version": "0.1",
    "mcversion": "1.6.2",
    "authors": [ "Graphicscore", "Setix", "mehrmrhr" ],
    "credits": "Code by Graphicscore and GFX by mehrmrhr",
    "logoFile": "/assets/textures/logo.png",
    "useDependencyInformation": "true"
  }]

I am not sure about the logo file either. You might want to remove the path and put the logo image next to this file.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • https://mclo.gs/4UC49Ao
    • Way back in the Forge 1.17 days, work started for adding JPMS (Java Platform Module Support) to ModLauncher and ForgeModLoader. This has been used internally by Forge and some libraries for a while now, but mods (those with mods.toml specifically) have not been able to take advantage of it. As of Forge 1.21.1 and 1.21.3, this is now possible!   What is JPMS and what does it mean for modders? JPMS is the Java Platform Module System, introduced in Java 9. It allows you to define modules, which are collections of packages and resources that can be exported or hidden from other modules. This allows for much more fine-tuned control over visibility, cleaner syntax for service declarations and support for sealed types across packages. For example, you might have a mod with a module called `com.example.mod` that exports `com.example.mod.api` and `com.example.mod.impl` to other mods, but hides `com.example.mod.internal` from them. This would allow you to have a clean API for other mods to use, while keeping your internal implementation details hidden from IDE hints, helping prevent accidental usage of internals that might break without prior notice. This is particularly useful if you'd like to use public records with module-private constructors or partially module-private record components, as you can create a sealed interface that only your record implements, having the interface be exported and the record hidden. It's also nice for declaring and using services, as you'll get compile-time errors from the Java compiler for typos and the like, rather than deferring to runtime errors. In more advanced cases, you can also have public methods that are only accessible to specific other modules -- handy if you want internal interactions between multiple of your own mods.   How do I bypass it? We understand there may be drama in implementing a system that prevents mods from accessing each other's internals when necessary (like when a mod is abandoned or you need to fix a compat issue) -- after all, we are already modding a game that doesn't have explicit support for Java mods yet. We have already thought of this and are offering APIs from day one to selectively bypass module restrictions. Let me be clear: Forge mods are not required to use JPMS. If you don't want to use it, you don't have to. The default behaviour is to have fully open, fully exported automatic modules. In Java, you can use the `Add-Opens` and `Add-Exports` manifest attributes to selectively bypass module restrictions of other mods at launch time, and we've added explicit support for these when loading your Forge mods. At compile-time, you can use existing solutions such as the extra-java-module-info Gradle plugin to deal with non-modular dependencies and add extra opens and exports to other modules. Here's an example on how to make the internal package `com.example.examplemod.internal` open to your mod in your build.gradle: tasks.named('jar', Jar) { manifest { attributes([ 'Add-Opens' : 'com.example.examplemod/com.example.examplemod.internal' 'Specification-Title' : mod_id, 'Specification-Vendor' : mod_authors // (...) ]) } } With the above in your mod's jar manifest, you can now reflectively access the classes inside that internal package. Multiple entries are separated with a space, as per Java's official spec. You can also use Add-Exports to directly call without reflection, however you'd need to use the Gradle plugin mentioned earlier to be able to compile. The syntax for Add-Exports is the same as Add-Opens, and instructions for the compile-time step with the Gradle plugin are detailed later in this post. Remember to prefer the opens and exports keywords inside module-info.java for sources you control. The Add-Opens/Add-Exports attributes are only intended for forcing open other mods.   What else is new with module support? Previously, the runtime module name was always forced to the first mod ID in your `mods.toml` file and all packages were forced fully open and exported. Module names are now distinguished from mod IDs, meaning the module name in your module-info.java can be different from the mod ID in your `mods.toml`. This allows you to have a more descriptive module name that doesn't have to be the same as your mod ID, however we strongly recommend including your mod ID as part of your module name to aid troubleshooting. The `Automatic-Module-Name` manifest attribute is now also honoured, allowing you to specify a module name for your mod without needing to create a `module-info.java` file. This is particularly useful for mods that don't care about JPMS features but want to have a more descriptive module name and easier integration with other mods that do use JPMS.   How do I use it? The first step is to create a `module-info.java` file in your mod's source directory. This file should be in the same package as your main mod class, and should look something like this: open module com.example.examplemod { requires net.minecraftforge.eventbus; requires net.minecraftforge.fmlcore; requires net.minecraftforge.forge; requires net.minecraftforge.javafmlmod; requires net.minecraftforge.mergetool.api; requires org.slf4j; requires logging; } For now, we're leaving the whole module open to reflection, which is a good starting point. When we know we want to close something off, we can remove the open modifier from the module and open or export individual packages instead. Remember that you need to be open to Forge (module name net.minecraftforge.forge), otherwise it can't call your mod's constructor. Next is fixing modules in Gradle. While Forge and Java support modules properly, Gradle does not put automatic modules on the module path by default, meaning that the logging module (from com.mojang:logging) is not found. To fix this, add the Gradle plugin and add a compile-time module definition for that Mojang library: plugins { // (...) id 'org.gradlex.extra-java-module-info' version "1.9" } // (...) extraJavaModuleInfo { failOnMissingModuleInfo = false automaticModule("com.mojang:logging", "logging") } The automatic module override specified in your build.gradle should match the runtime one to avoid errors. You can do the same for any library or mod dependency that is missing either a module-info or explicit Automatic-Module-Name, however be aware that you may need to update your mod once said library adds one. That's all you need to get started with module support in your mods. You can learn more about modules and how to use them at dev.java.
    • Faire la mise à jour grâce à ce lien m'a aider personnellement, merci à @Paint_Ninja. https://www.amd.com/en/support 
    • When I came across the 'Exit Code: I got a 1 error in my Minecraft mods, so I decided to figure out what was wrong. First, I took a look at the logs. In the mods folder (usually where you'd find logs or crash reports), I found the latest.log file or the corresponding crash report. I read it through carefully, looking for any lines with errors or warnings. Then I checked the Minecraft Forge support site, where you can often find info on what causes errors and how to fix them. I then disabled half of my mods and tried running the game. If the error disappeared, it meant that the problem was with the disabled mod. I repeated this several times to find the problem mod.
    • I have no idea - switch to a pre-configured modpack and use it as working base    
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.