Posted April 17, 20178 yr I just updated from 13.20.0.2228 to 13.20.0.2282 and my Annotation Config is no longer working. It worked before, is there something I am doing wrong? https://github.com/LogicTechCorp/NetherEx/blob/b8f3aa89f1a7b6cf5f7007f11f7f8b38a2731ded/src/main/java/nex/handler/ConfigHandler.java Edited April 17, 20178 yr by LogicTechCorp
April 20, 20178 yr Author I have still been unable to solve this. Is there anyone who has an idea on what I am doing wrong?
April 20, 20178 yr I have no idea what the hell that is, how it works, or what the problem is. Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable. If you think this is the case, JUST REPORT ME. Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice. Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked. DO NOT PM ME WITH PROBLEMS. No help will be given.
April 20, 20178 yr Author 33 minutes ago, Draco18s said: I have no idea what the hell that is, how it works, or what the problem is. It is the new system Forge has implemented for configs.
April 21, 20178 yr Author @Choonster I saw that you use the new config system in your test mod and was wondering if you could help me?
April 21, 20178 yr What exactly do you mean by "not working"? Please don't PM me to ask for help. Asking your question in a public thread preserves it for people who are having the same problem in the future.
April 21, 20178 yr Author 1 hour ago, Choonster said: What exactly do you mean by "not working"? It creates a Config file that contains categories but no options. Edit: It looks like this # Configuration file nex { client { } dimension { } block { } potion_effect { } entity { } biome { } } Before I updated it had more sub categories and it had a lot of config options. Edited April 21, 20178 yr by LogicTechCorp
April 21, 20178 yr I found the issue: Only the class for the top-level category (i.e. the one annotated with @Config) can have static fields, all other category classes must use non-static fields. I've fixed this and pushed the fix to a fork of your repository. You can view the changes and/or merge them here. Please don't PM me to ask for help. Asking your question in a public thread preserves it for people who are having the same problem in the future.
April 21, 20178 yr Author 46 minutes ago, Choonster said: I found the issue: Only the class for the top-level category (i.e. the one annotated with @Config) can have static fields, all other category classes must use non-static fields. I've fixed this and pushed the fix to a fork of your repository. You can view the changes and/or merge them here. Thank you for all of your help. I really appreciate it.
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.