[1.12]How to make recipes configurable?

[RealTheUnderTaker11]

I have a magnet mod that has a Boolean in the config to change the recipes for every magnet in the mod (so there can be easy mode recipes or normal recipes). Before 1.12, this was easy. How would I now be able to give the player a config option to change the recipes of each item? 

Sorry if this has been asked or explained before, it's hard to find good information on this new JSON recipe system.

Edited August 28, 2017 by RealTheUnderTaker11

[MrBendelScrolls]

Is there any other solutions? It's really not the thing for many users.

[jabelar]

Wait, first you need to clarify what you're trying to do. Are you asking to allow players to create their own recipes, or do you mean you have two sets of recipes (easy mode and hard mode) that you want them to switch between?

 

If you want them to be able to switchthen the simplest way is to look at the config during the recipe registration event and register the recipes according to the config. This would require restarting the game after each change of the config, but it would be safest way. 

[MrBendelScrolls]

5 hours ago, jabelar said:

Are you asking to allow players to create their own recipes, or do you mean you have two sets of recipes (easy mode and hard mode) that you want them to switch between?

>

15 hours ago, RealTheUnderTaker11 said:

a Boolean in the config to change the recipes for every magnet in the mod (so there can be easy mode recipes or normal recipes)

------------

5 hours ago, jabelar said:

to look at the config during the recipe registration event and register the recipes according to the config.

>

15 hours ago, RealTheUnderTaker11 said:

on this new JSON recipe system

------------

¯\_(ツ)_/¯

[MrBendelScrolls]

15 hours ago, diesieben07 said:

Ok, so instead of tinkering with a config file, they now create a recipe file in a folder. What's the big deal?

For many people, including myself, it's a lot easier and cleaner just to change a line in the config than download a resourcepack.
JSON system is good for modpacks, but not for regular usage IMHO.

Edited August 29, 2017 by MrBendelScrolls

[Choonster]

15 hours ago, RealTheUnderTaker11 said:

I have a magnet mod that has a Boolean in the config to change the recipes for every magnet in the mod (so there can be easy mode recipes or normal recipes). Before 1.12, this was easy. How would I now be able to give the player a config option to change the recipes of each item? 

Sorry if this has been asked or explained before, it's hard to find good information on this new JSON recipe system.

 

You'll need to create your own condition that returns true or false based on this option and then create separate recipe files for easy and hard mode that use this condition.

 

Create a class that implements IConditionFactory and then specify this class in recipes/_factories.json. You can implement BooleanSupplier (the type returned by IConditionFactory#parse) using a lambda that returns the value of your config option.

 

In a recipe file, set the conditions property of the top-level object to an array containing an object for each condition. In each condition object, set the type property to the name of the condition type and include any other properties required by the condition type.

 

Forge will test the conditions at recipe load time and only register the recipe if all of them are met.

 

You can use the forge:not condition to invert the result of a condition.

 

 

If the hard and easy mode recipes are mostly the same except for one or two ingredients, you may want to use a conditional ingredient like this. This will allow the individual ingredients to change based on the config option instead of having one of two recipes enabled based on the config option.

 

15 hours ago, diesieben07 said:

Simple, they make a resource pack and overwrite the recipe JSON.

 

Resource packs can't overwrite server-side files like recipes or loot tables, but Mojang plans to add data packs in 1.13 to allow that.

[Draco18s]

3 hours ago, diesieben07 said:

Really, that's not possible yet? Typical...

Indeed. I already tried shoving a recipe into my own assets directory under /minecraft and it did diddly squat. Had to search around for a thread on recipe removal. Which, of course, leads to some vanilla advancements throwing an error when they load because the recipe is now missing.

[Choonster]

29 minutes ago, Draco18s said:

Indeed. I already tried shoving a recipe into my own assets directory under /minecraft and it did diddly squat. Had to search around for a thread on recipe removal. Which, of course, leads to some vanilla advancements throwing an error when they load because the recipe is now missing.

 

You can override recipes by registering a dummy recipe with the same name as the vanilla one, but this spams the log with Dangerous alternative prefix warnings from Forge.

[Draco18s]

6 minutes ago, Choonster said:

You can override recipes by registering a dummy recipe with the same name as the vanilla one, but this spams the log with Dangerous alternative prefix warnings from Forge.

Only if you're doing it with the registry event. If you're using JSON files, it just isn't loaded.

[Choonster]

3 minutes ago, Draco18s said:

Only if you're doing it with the registry event. If you're using JSON files, it just isn't loaded.

 

Indeed. JSON files are only loaded for your mod ID and always have your mod ID as the domain of their registry name.

[RealTheUnderTaker11]

Sorry to take so long to reply (been pretty busy), but all that seems like more trouble than it's worth, and I found this handy helper class that lets me register them almost exactly as I was. I might change it later but for right now it doesn't seem worth it.

[Choonster]

If you must register recipes in code (which I recommend against doing), use the registry events.

[Draco18s]

If you really want to do it in the single-call format (that is, your main class contains a new Block() line followed by a registerBlock() line) I'm in the process of updating my EasyRegistry class to 1.12, hasn't been pushed to git yet, but should be available in a day or so.

[Draco18s]

(Client)EasyRegistry for 1.12 now available.

 

Usage is straight forward. There's a separate method for every type of registration you may be interested in performing--block with item, block without item, item, items with IStateMappers, items with custom MeshDefinitions...--(if one's missing its because I haven't needed support for it myself). Note that if you wish to utilize this class, you may, just put it into a different package so it doesn't conflict if our mods are ever loaded side by side.

 

Note that the EasyRegistry is treated as both a proxy and event handler.

Edited September 1, 2017 by Draco18s