Here is a blueprint for a basic parameterized bot-served biochamber*. (Note: I play with Bob's Adjustable Inserters. This blueprint contains only basic straight inserters, so it should be compatible with vanilla Factorio, but if it doesn't work, then install 'bobinserters 1.3.2 ...

If a parameterized blueprint has a parameter which sets the recipe for a machine, then normally when placing the blueprint the user is offered a dialogue which allows them to select from the recipes that machine can perform. It is even smart enough that, if the blueprint contains multiple types of ...

You missed wood (obviously biological) and agricultural science packs (not prima facie biological, but they spoil into spoilage, so what else can they be?), which both also recycle into themselves.

I suspect that text might be a holdover from some earlier step in development, when it was planned ...

The range for normal-quality Lightning Rods and Lightning Collectors are listed as '15 + Lightning reach' and '25 + Lightning reach' respectively. When I saw this, I initially assumed it would be something like worker robot speed: 15/25 was the base value, but there would be some research (possibly ...

Certain signals cannot be parameterized in blueprints. If you hit 'parameterize blueprint' on a blueprint where these signals are set, the signal they are set to is not offered as a parameterizable value. If you have the same signal used elsewhere in the blueprint and make it a parameter, the value ...

Hrm. Looks like the same issue exists for the 'Read working' parameter on assemblers.

I suspect this is the side-effect of an intended - and honestly quite useful, if poorly documented and explained - behaviour. Namely, the ability to make a blueprint that refers to a given item at multiple quality levels. For instance, I have a blueprint that I use to build a set of 5 storage chests ...

Loewchen wrote: Tue Nov 26, 2024 5:34 am 121360

This is not the same bug as the one you have linked. Please move this thread back to Bug Reports.

+1

Perhaps not necessarily a 10x reduction, but something to make it worth using at green tier. Right away when you unlock it, it's the only thing you can spend power on at all, but as soon as you unlock roboports it's in your interests not to use it until power armor.

I'd say 10kW makes sense ...

@Loewchen: How is this a duplicate? I'm not talking about parameterization altering a constant stack size when it shouldn't; I'm talking about not being able to parameterize what signal is used to dynamically set stack size.

You cannot parameterize what signal the 'Set stack size' option uses.

This blueprint contains an inserter with 'Set stack size' enabled and the signal set to [Wooden Chest]. If you try hitting the 'Parameterize blueprint' button, it says there's nothing to parameterize:
0eNptkOFugzAMhN ...

But far worse, covering that 100kW draw through Nauvis's night would demand 226kJ of battery capacity - more than 11 Mk1 personal batteries. Battery is 20 MJ which is 200 seconds of 100 kW draw. Certainly longer than Nauvis night.

Huh. You're right. I think I misread the battery capacity as 20 ...

Belt Immunity Equipment draws 100kW of power constantly, whether on a belt or not. This makes it entirely impractical to use until you have at least a Portable Fission Reactor - which is really annoying, because the early Modular Armour era is exactly when being immune to belts would be most useful ...

The electric network window shows a history of power production and consumption, as well as accumulator charge level. But the power production graph only shows the actual power generation, not the maximum power generation available. Having a history of that would be very helpful for things like ...

If you build a logistics chest outside of logistics coverage, you get a nice little warning icon. However, if you have a building which is set to enable itself based on the contents of the logistics network (all buildings which can be enabled or disabled using a circuit network also have an option ...

@boskid: Do you still require more information?

You've set it to only read the red wire for condition checks, so it definitely won't do that. When you use "Each" mode, think of it as the combinator switching to a vector mode and evaluating the conditions for every input signal separately. In this case, since you've selected to evaluate only red ...

Example:
0eNrdldtuwjAMht/F1wHR07ZW2l4EoSptDURrky5NYQj13eeknAYMxrYLNPXGceL/tz8p6RqyssVaC2kgWYPIlWwgGa+hETPJS5uTvEJIoMBcFKgHuaoyIblRGjoGQhb4DonXsTMlVsxwac7X+N2EAUojjMDe0y1WqWyrDDWJsktCDGrVUK2S1pH0BsGTN4wYrCCJR+EwIqdCaMz7IyGzKkarMs1wzheCJKiu6febzzH1sh2MwVSUBvVx1qxq29lCaNPS0LtWewgDjzJvtEHzUFIqXblD1H ...

While it is not really needed and can be overcome quite easily, I feel like having the "else" condition in combinators would make them feel more complete, especially after the 2.0 update they got.


Agree 100%.

And with the extended boolean conditions and multiple outputs introduced in 2.0, I ...

Also add different colours for areas covered by lighting rods, lighting collectors, and lightning attractors (which are the pre-existing lightning protection systems you find among the ruins. Since they return different amounts of power - in the case of the lightning attractors, no power at all - it ...