-
Notifications
You must be signed in to change notification settings - Fork 22
FAQ Troubleshooting
So, I heard you're having trouble with Growthcraft? This here guide will (hopefully) answer your questions, otherwise please do open an issue on our github page.
Here here on, the user will be referred to as YOU. To drive the point home of course. Some strong standards language may be used here such as SHOULD, MUST, WILL NOT, etc..
If running a modpack, YOU SHOULD include the Growthcraft json configs.
These configs MUST be in sync with the server and client to work correctly, otherwise Growthcraft may produce undefined behaviour.
Always test your modpacks, and check configs, possibly redeploying or re-installing the pack from scratch to ensure it works correctly.
Something like this?
java.lang.NoSuchFieldError: dispatcher
at growthcraft.core.integration.AppleCore.validateGrowthTick_AC(AppleCore.java:34)
at growthcraft.core.integration.AppleCore.validateGrowthTick(AppleCore.java:40)
Update your copy of Apple Core to 1.3.x or later
Users updating from 2.4.x, may encounter the GSON error in their game, this is solved by removing the growthcraft json configs, or updating them to the new format.
These files are located under the growthcraft directory in your minecraft configs directory.
There will be several sub directories each containing some json configs.
config/growthcraft/**/*.json
If YOU have been haphazardly updating ANYTHING (whether it be applications, packages, or mods), STOP.
YOU should be paying attention to the mods being updated; especially when they aren't updating in a teeny or patch level version (x.y.Z where Z is the teeny/patch level: eg. from 2.5.1 to 2.5.2).
Growthcraft uses semantic versions, when we update a minor version it means something critical changed and YOU SHOULD check your configs.
This is being relayed to YOU from experience within the software development community. Haphazardly updating mods, packages, or applications is a royal way to screw yourself over.
Once the configs are generated the first time, Growthcraft WILL NOT modify them: as modifying these files after creation can potentially remove user settings (dropping whole recipes from the config), AND OR add unwanted behaviour (re-adding recipes that where removed, or modified to fit the user).
com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was BEGIN_ARRAY at line 1 column 2
Remove your config/growthcraft/**/*.json config files, (this means from all .json files under the growthcraft config directory)
For more information, see at Updating from 2.4.x to 2.5.x
java.lang.NoSuchMethodError: net.minecraft.item.ItemStack.getItem()Lnet/minecraft/item/Item;
Question, are YOU using the individual jars?
- YES?, remove the
apijar. The API is already included with thecore. - NO?, try running your setup with Growthcraft ALONE. If the problem persists, please report this on the Growthcraft github issue tracker.
This issue is present in 2.4.x, with the introduction of the User API: Brewing, Fermenting, Pressing recipes are generated when YOU start minecraft and their are no config files present, the initial values are pulled from the basic config (growthcarft/cellar.cfg), if you change the brew time, or brew yield, its best to:
- A - Remove the generated JSON config files
- B - Edit the JSON config files
Note that the config options will be REMOVED in 2.5.x in favour of using the JSON API instead.
Toggle the debug option in the cellar module (growthcraft/cellar.cfg) and watch the console for error logs from Growthcraft (depending on your version of Forge, the logs may not be prefixed with Growthcraft, in that case lookout for keywords (fermenting, pressing, brewing etc..))
Growthcraft will log as best as it can the problems present in your custom recipe, if your JSON file is malformed, then the game will probably crash.
The Culture Jar works on a very specific set of rules:
- The Jar MUST be placed into a specific set of biomes defined by the
configs/growthcraft/cellar/yeast.jsonconfig in order to create yest - The Jar MUST be filled with a
YOUNGBooze of your choosing. - If YOU wish to duplicate, replicate a specific yeast, then you must FILL do the previous step and place the yeast YOU wish to dup., or rep. into the yeast slot, this will work REGARDLESS of biome.
In order to determine if a Booze is young, simply look at its name or description, it should include Young in its name or description tags
Added in 2.5.0's development is a config option to disable the Discard button.
First up, we've tried my utmost hardest to make that class as bulletproof as possible since its used for ALL the Growthcraft Registry items. In the case that it DOES fail, it means it was used in a way not meant to be (passing a null ItemStack, or a ItemStack with an invalid item etc..), in that case ItemKey will play it safe and fail immediately, nothing is messier than a gameplay error caused by the Registries
You need to change the "Brewer ID" in the cellar.conf file to the new default of 6677 instead of the old default of 10.
Fail fast and fail hard, if YOU made a mistake in the Growthcraft's config, then: YOU SHOULD FIX IT.
By ignoring these errors, they accumulate over time and cause more errors, and undesired behaviour.
By crashing early and forcing YOU to correct the problem, this removes the need for reporting user errors, and wasting valuable development time to find a non-existant, or user produced problem.
If YOU are not sure what caused the problem, or it is not covered by this FAQ, please report the issue on the github issue tracker, it will be addressed ASAP.
Stop! TOMARE! Please read the Module Contribution Guide first.
Did YOU tl;dr? Then we'll tl;dr your module idea as well.
Semantic versioning
X.Y.Z X = Major Version, we've updated to a new version of Minecraft (definitely something broke) Y = Minor Version, we've added new features to the existing Z = Teeny Version, we've fixed several minor issues, or including some small non-breaking changes