You might use the "energy" property of the electric interface to check for this: If its > 0, the interface is at least somewhat powered. If you want to check whether a certain treshold is reached (e.g. "at least 60% of energy demand provided"), your calculation could take the &qu...

Those glowing heat pipes emanate something sinister and powerful.

Especially that night time picture really brings the "Forges of Isengard" from the LOTR trilogy into my mind...

Great work!

But why? Hi, I'm sorry, I wasn't able to reply earlier. My reason for this proposal is that this would allow the use of animated icons for item-request-proxies that mimic the flashing entity status signs. It would also allow to create some kind of non-static icon like the rotating wrench symbol sho...

+0.5 might come in handy later. I didn't even think about the possibility of having more than one item-request-proxy prototype. I guess you want to spawn this manually and the engine keeps using the default one for stuff like blueprint modules? But has you probably have to track the proxy status an...

<marquee><blink>No thank you</blink></marquee> If my intention would be to annoy the player with unneccessarily distracting symbols, I'd just abuse the possibilities provided by the new rendering api :D In fact, this proposal is to avoid needing to render a separate animation whenever this item req...

Currently any "item-request-proxy" entity requires a type "picture" sprite for the icon of the proxy. My question/suggestion: Allow the use of type "animation" for this, too. This would make nice things possible, imagine for example an item request proxy with an icon li...

Reading the patchnotes was a punch in the gutts for me. I just hope for now, that we (the ones against the change) eventually will be able to comprehend Wube's grand schemes that made it inevitable and mandatory to rush this extremely controversial change to implementation and that the greater good ...

The explanations by V453000 are interesting and visually appealing but they nevertheless leave me behind a bit puzzled. My question is: What is your main intention behind the oil change? Is it to reduce the complexity /to smooth out the learning curve for new players? Then I’m curious why the "...

I'd argue that instead of changing the recipe, what is needed is more information. Specifically, an oil tutorial. Have the player build a pump jack, connect it to a refinery, and then instruct them to use one of the outputs to make something. Let's say a chem plant to make plastic. Once the output ...

I can only speak for myself, but the moment I discovered that refining oil in Factorio resulted in multiple by-products, I knew this was the game I had been waiting for years. Please keep the recipe as it is and allow future players to enjoy this moment as well. All other changes (inluding reserved ...

Hello together, at the moment it is easy to track production numbers for all entities of Type "CraftingMachine" using LuaEntity.products_finished . This is convienient but unfortunately not availabe for other entity types. Proposal I'd like to have a similar function for miners and lab ent...

On my modded offshore-pumps this works correct But I have also set: offshore_pump.fluid_box.filter = "apm_sea_water" [...] TIL... I wrongly assumed that changes to the fluid output will automatically change the fluidbox filter as well. The mod i use for this did not change the fluidbox fi...

Hello, i encountered a serious problem with modded offshore pumps: If an offshore pump produces any fluid but water, the ghost of this modded offshore pump will nevertheless show "water" as fluid output. This causes some trouble since the inception of the new fluid mixing prevention logic,...

Thanks for the report. I don't know if I consider it worth the time to go around making the item-request-proxy respect those flags since by it's nature it only exists to be interacted with through blueprints and the deconstruction planner. For now, I'm going to say it isn't worth it and leave it as...

Dear devs, i just stumbled upon the following issue: If i add the "not-blueprintable" and "not-deconstructible" flags to an item-request-proxy, i'm still able to deconstruct those entities with a deconstruction planner. Steps to reproduce: 1. Add the "not-blueprintable"...

Bilka wrote: ↑

Sat Apr 06, 2019 6:57 pm

Okay, added to the next version.

Thank you

Hi, I propose the exposition of the "alert_icon_shift" property that's currently available only on prototype load. I'm using the new lua.renderer functions to draw an warning icon on top of an entity. However, this function will place the icon at the center of the target entity and not at ...

[...] there's no way to know what's going to happen when a mod reads an entity's `item_requests` or sets it nil. If the "item_requests"-value of a item-request-proxy is set to nil, the item-request-proxy is fulfilled and subsequently removed (i tested this a few minutes ago). It doesn't m...

+1

Dear devs,
please make completion and cancellation of entity-type "item-request-proxy" detectable. Currently there is no efficient way to get information about this, because the "death" of item request proxies is also not covered by event.on_entity_died().

Regards,
Arcitos

Thanks for your fast reply, posila. This is indeed a real pity, but i fully understand your motivation in keeping the tile id limit at 255. I was just curious if lifting this limit would be feasible.

Regards
Arcitos