Factorio Forums

DRY411S wrote:So my Recycling Machines Mod https://mods.factorio.com/mods/DRY411S/ZRecycling works by loading all the vanilla and installed mods recipes and reverses them by turning the original results into ingredients and the original ingredients into results.

It does this in the game data stage when the game is initially started by players.It has to use the data stage because the recipes form part of data.raw.

The problem is that at that stage there are normal ingredients and expensive ingredients, and I have to choose one or the other as the results of the recycling recipes. I'm defaulting to the normal ingredients at the moment.

Is there an event I can trap in control.lua that would allow me to alter the ingredients in data.raw when people start a new map, and decide to use expensive ingredients?

Klonan wrote:Why not just define both a normal and expensive recipe?

DRY411S wrote:

Klonan wrote:Why not just define both a normal and expensive recipe?

Normal and expensive reverse recipes?

Klonan wrote:

DRY411S wrote:

Klonan wrote:Why not just define both a normal and expensive recipe?

Normal and expensive reverse recipes?

Sure

DRY411S wrote:

Klonan wrote:

DRY411S wrote:

Klonan wrote:Why not just define both a normal and expensive recipe?

Normal and expensive reverse recipes?

Sure

So is there a variable I can test to see whether the player is using expensive recipes?

  {
    type = "recipe",
    name = "electronic-circuit",
    normal =
    {
      ingredients =
      {
        {"iron-plate", 1},
        {"copper-cable", 3}
      },
      result = "electronic-circuit",
      requester_paste_multiplier = 50
    },
    expensive =
    {
      ingredients =
      {
        {"iron-plate", 2},
        {"copper-cable", 10}
      },
      result = "electronic-circuit",
      requester_paste_multiplier = 50
    },
  }, 

DRY411S wrote:Thanks that works if I can have an array of results instead of a singular result. I'll give it a try.

bobingabout wrote:I don't even understand what the issue is.

bobingabout wrote:if normal exists, then expensive exists too.

   if recipe.normal or recipe.expensive then
      if recipe.normal then
         --do stuff with normal version
      end
      if recipe.expensive then
         --do stuff with expensive version
      end
   else
      --do stuff with base version
   end

Exasperation wrote:

bobingabout wrote:if normal exists, then expensive exists too.

A word of warning, this is apparently not strictly true. I recently had a request to change some of my code to make it compatible with a mod that was creating recipes with expensive but not normal variants. As a result, I had to move to something like this:

Code: Select all

   if recipe.normal or recipe.expensive then
      if recipe.normal then
         --do stuff with normal version
      end
      if recipe.expensive then
         --do stuff with expensive version
      end
   else
      --do stuff with base version
   end

Exasperation wrote:I don't remember exactly which mod it was, but it was some marathon-style mod. Given that, I suppose "all my users are going to use expensive recipes" was a reasonable assumption on their part. I honestly didn't test to see what happened if a recipe only had an expensive version but the difficulty was set to normal (or vice versa), I just did one of these , made the change to avoid my code crashing from attempting to index a nil, and let it be their problem to deal with from then on.

And yes, all of the vanilla recipes either have both normal + expensive or neither.