Jump to content

@Mod annotation not taking information


Recommended Posts

Sorry for the probably dumb question, this is my first time modding Minecraft. I keep seeing things that say you can put information about your mod in the @Mod annotation like the modID, display name, version number, etc., but when I try to do specify the field for it, it raises an error and says that it's not recognized. Am I doing something wrong? (I'm using forge 1.14 and JDK 10)

Edited by lizzyd710
Adding specs
Link to comment
Share on other sites

Since 1.13 the @Mod annotation only has a single parameter - your modid. Everything else goes in mods.toml.

  • Like 1

About Me


My Discord - Cadiboo#8887

My WebsiteCadiboo.github.io

My ModsCadiboo.github.io/projects

My TutorialsCadiboo.github.io/tutorials

Versions below 1.14.4 are no longer supported on this forum. Use the latest version to receive support.

When asking support remember to include all relevant log files (logs are found in .minecraft/logs/), code if applicable and screenshots if possible.

Only download mods from trusted sites like CurseForge (minecraft.curseforge.com). A list of bad sites can be found here, with more information available at stopmodreposts.org

Edit your own signature at www.minecraftforge.net/forum/settings/signature/ (Make sure to check its compatibility with the Dark Theme)

Link to comment
Share on other sites

Ah, thank you for clarifying! I keep seeing a file called mcmod.info being referenced, but I only have that mods.toml file. Is there a place that shows all the parameters you can set in the mods.toml, because all I seem to be finding is stuff about mcmod.info, and I only have those example parameters in my mods.toml file.

Link to comment
Share on other sites

The MDK comes with a mods.toml that shows you which values are required and which are optional.

  • Like 1

This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy.


As the most common issue I feel I should put this outside the main bulk:

The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge.

If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan.


For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety.


Logs (Most issues require logs to diagnose):


Please post logs using one of the following sites (Thank you Lumber Wizard for the list):

https://gist.github.com/100MB Requires member (Free)

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://hastebin.com/: 400KB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.


What to provide:

...for Crashes and Runtime issues:

Minecraft 1.14.4 and newer:

Post debug.log

Older versions:

Please update...


...for Installer Issues:

Post your installer log, found in the same place you ran the installer

This log will be called either installer.log or named the same as the installer but with .log on the end

Note for Windows users:

Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension


Where to get it:

Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs.


Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it).
  4. Now launch the pack through that profile and follow the "Mojang Launcher" instructions above.






or alternately, 


Fallback ("No logs are generated"):

If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft


Server Not Starting:


If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output.


Reporting Illegal/Inappropriate Adfocus Ads:


Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad.

Lex will need the Ad ID contained in that URL to report it to Adfocus' support team.


Posting your mod as a GitHub Repo:


When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub.

When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.


  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. Run the following commands:
    1. git init
    2. git remote add origin [Your Repository's URL]
      • In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git
    3. git fetch
    4. git checkout --track origin/master
    5. git stage *
    6. git commit -m "[Your commit message]"
    7. git push
  4. Navigate to GitHub and you should now see most of the files.
    • note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]


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.

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

    • Just for testing - is a pre-configured modpack with more mods working? Try ATM9 (419 mods): https://www.curseforge.com/minecraft/modpacks/all-the-mods-9 or Prominence II (370 mods): https://www.curseforge.com/minecraft/modpacks/prominence-2-classic    
    • Sorry, just seeing this now. The compiled jar was working just fine prior to me adding the custom portal, but here is the link to the entire project at the time the portal was in there: https://github.com/warrentode/TurtleBlockAcademy/tree/1.0.1 Direct link to the build.gradle: https://github.com/warrentode/TurtleBlockAcademy/blob/1.0.1/build.gradle Direct link to the access transformer file: https://github.com/warrentode/TurtleBlockAcademy/blob/1.0.1/src/main/resources/META-INF/accessTransformer.cfg And if you need to take a look at the teleporter class: https://github.com/warrentode/TurtleBlockAcademy/blob/1.0.1/src/main/java/com/github/warrentode/turtleblockacademy/world/dimension/portal/TBAMiningTeleporter.java The portal block: https://github.com/warrentode/TurtleBlockAcademy/blob/1.0.1/src/main/java/com/github/warrentode/turtleblockacademy/blocks/TBAMiningPortalBlock.java Currently, I've removed the portal block until I can figure this out and we just access the dimension via a clickable sign in the homeschooling LAN server we have here at home, but I'd really like to be able to solve and fix the problem. 
    • I doubt texture atlasing is the problem which causes the serializer to throw errors if I'm being frank. Though I am in agreement that it seems like Forge, in modern versions, poorly handles tons of mods.
    • Add crash-reports with sites like https://paste.ee/ and paste the link to it here   Delete the carryon-server.toml file from your config folder
    • <script src="https://paste.ee/e/qgZSn/0"></script>
  • Create New...

Important Information

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