What happened? Combat robots do not have a collision mask defined, which makes them immune to all damage that is not a direct homing attack. This includes explosive damage from grenades, explosive rockets, explosive cannon shells, artillery. Projectiles that do not home in also do not collide with ...

A rocket silo recipe that outputs more than 1 rocket part per recipe only gets counted as one rocket part for rocket progress, as if recipe completion is what really matters as opposed to the output item count.

A mod and a save on the attachments demonstrate the issue.

That function should be enough to check for connectivity, yes. Thanks.

edit: isn't the content of a fluidbox returned from the operator [] just the fluid data? how do you get the reference for the two separate fluidboxes for the parameters, then?

The fluid system number looks very useful to tell whether two fluidboxes are connected to each other without snaking over every pipe segment in-between. The game is already keeping track of it and showing it on the debug tooltip, why not put a getter function to the Lua object? Something like LuaFlu...

I just found out that this issue existed, and thankfully got pointed to this thread. It does seem wasteful to not have the catalyst data in LuaRecipePrototype.

It doesn't look like I can access a burner's fluidbox anywhere within an entity. Bob's oil boilers reports 2 fluidboxes, not 3.

I'm not saying completely block the player from doing so, just discourage it by needing pumps everywhere to move it. The simplest way to use it would then be to place the generator directly on the fluid producer, which is what I want. Other ways to move that fluid is not a dealbreaker, as long as it...

Fluid flow parameters were removed as part of the new fluid system update, but as it's not fully implemented yet, is it possible to bring it back for .17? I want to make a power system that does not use hidden entities but discourages transport of the powered fluid. I'd assume making the fluid flow ...

Dominik wrote: ↑

Fri Mar 08, 2019 10:28 am

These values remain the same, they have only moved from the prototype into code. So this is not the reason.

That said, can modded fluids still use these properties in the prototypes in .17.X, or are these variables entirely removed from prototype declarations?

Updating from 2.0.3 to 2.0.4 gives me this error on startup: 5.371 Error ModManager.cpp:1283: Failed to load mod "deadlock-beltboxes-loaders": __deadlock-beltboxes-loaders__/data.lua:8: __deadlock-beltboxes-loaders__/prototypes/vanilla_tiers.lua:42: attempt to index field 'deadlock-stackin...

I got a crash on clicking the the main GUI button to close the GUI. 1045.337 Error MainLoop.cpp:1092: Exception at tick 28642: The mod LTN Tracker caused a non-recoverable error. Please report this error to the mod author. Error while running event LTN_Tracker::on_gui_click (ID 1) The mod Unit Contr...

I was in the process of updating mods. I changed tabs, and downloaded Deadlock's Loaders. While that hasn't finished yet, I changed to Update tab to see the progress of updates. I was greeted with this: https://cdn.discordapp.com/attachments/139677590393716737/551674811705851914/unknown.png Clicking...

Hi, how about uploading mod settings?

Hi, Bob, I'm not that sure Zelos has contacted you about this (beat him if he hasn't), but Omnicompression and Omnifluid can't handle the 1015 degrees steam.

It means people who don't subscribe to the experimental version would have their biters deleted when they update.