1.7.2 - EvilCraft-1.7.2-0.4.0b-6 Vague warnings/errors on startup.
sibomots opened this issue · 6 comments
There are two or three types of messages in the log during client-startup that I'm wondering about.
Type 1 - [10:56:27] [Client thread/FATAL] [EvilCraft]: Invalid config property class.
"Invalid config property class" ? I turned on debugging but cannot tell which configuration in the .cfg file is responsible.
Type 2 - [10:56:27] [Client thread/INFO] [EvilCraft]: [CONFIGCHECKER] class evilcraft.blocks.EvilBlock has no static 'TYPE' field.
"has no static 'TYPE' field"
On type 1, could you also printout the value.toString() in the error log so we can find the error-causing entry?
On type 2, same story - it's not clear which line in the .cfg is the offending line.
Are you a player or a developer? Because that debug option in the config file should only be enabled when in development mode, I should make this a bit clearer though...
As for the error "Invalid config property class.". You probably have set a wrong datatype inside the config file, like for example setting a number instead of a boolean. But I'll look into making these errors a bit clearer for the next update. For now, you can try deleting (make backup) the config file and let it regenerate, which will make a valid one.
Both. I am troubleshooting the development of a pack. Plus, I'm a developer.
As far as the "invalid config property class" warnings -- I'm using the stock config file generated by the mod itself. Unchanged from the default.
I did try removing the config file and let it regenerate it. Same warnings.
Thanks for the quick reply.
Ok, that should not happen, I will look into it later today.
The fix will probably be released once Forge for 1.7.10 releases, which should be anytime now.
Thanks for reporting this.
I'll probably have more time to patch it for 1.7.2. I just want the warnings to go away ;-) But as usual a warning can point to something wrong. It doesn't sound like a big deal.
I'll patch my fork and hope to see your improvement down the line.
Thank you for checking into this. Much appreciated. Your mod is the center of our pack.
Anyways, even when you see the errors, they are only a result of a small derp of mine while refactoring some code, but it should not influence the gameplay at all. It only broke some blocks and items that are still in development, but since they are not craftable/usable, that shouldn't be any problem.
Ok. Good to know. Thx.
Sent from my Windows Phone
From: Ruben Taelmanmailto:[email protected]
Sent: 6/26/2014 12:30 PM
To: rubensworks/EvilCraftmailto:[email protected]
Cc: sibomotsmailto:[email protected]
Subject: Re: [EvilCraft] 1.7.2 - EvilCraft-1.7.2-0.4.0b-6 Vague warnings/errors on startup. (#105)
Anyways, even when you see the errors, they are only a result of a small derp of mine while refactoring some code, but it should not influence the gameplay at all. It only broke some blocks and items that are still in development, but since they are not craftable/usable, that shouldn't be any problem.
Reply to this email directly or view it on GitHub:
#105 (comment)