Jump to content

Recommended Posts

Posted (edited)

Forge version: 1.12.2-14.23-5.2768

 

Hi,

 

Having recently wrote a little mod and gotten it all working I am now ready to move the config options to an external file rather than being hard coded.

 

The documentation I have found for this relates to adding the @Config annotation to my config class, however when I type that annotation on my class in Eclipse it's underlined red and when I however over it, Eclipse shows "Config is not an annotation type" and shows no import options as there have been with the other annotations I've used.

 

Any ideas how to get this working?

 

Cheers

Dave

 

 

Edited by raverdave2k
Posted (edited)

Try importing the annotation manually:

import net.minecraftforge.common.config.Config;

 

If that fails to import, it is likely that something went wrong during the setup of the workspace. In that case, try setting up the workspace again.

Edited by DavidM

Some tips:

Spoiler

Modder Support:

Spoiler

1. Do not follow tutorials on YouTube, especially TechnoVision (previously called Loremaster) and HarryTalks, due to their promotion of bad practice and usage of outdated code.

2. Always post your code.

3. Never copy and paste code. You won't learn anything from doing that.

4. 

Quote

Programming via Eclipse's hotfixes will get you nowhere

5. Learn to use your IDE, especially the debugger.

6.

Quote

The "picture that's worth 1000 words" only works if there's an obvious problem or a freehand red circle around it.

Support & Bug Reports:

Spoiler

1. Read the EAQ before asking for help. Remember to provide the appropriate log(s).

2. Versions below 1.11 are no longer supported due to their age. Update to a modern version of Minecraft to receive support.

 

 

Posted (edited)

Sooooo, this is a might awkward.

 

I added the import line manually as you suggested and it underlined with the error "The import net.minecraftforge.common.config.Config conflicts with a type defined in the same file". After staring at it for a moment I suddenly realised maybe it didn't like my config class being called "Config", sure enough a quick rename and the annotation immediately imported ?

 

So thanks for the response, while not quite how intended it still solved the problem.

Edited by raverdave2k
Posted

Also don’t call it ModConfig, cause that’s  what the Forge config class is called in 1.13. I suggest ModNameConfig or ModOptions or ModConfiguration or even ModSettings.

About Me

Spoiler

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)

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.

Announcements



×
×
  • Create New...

Important Information

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