Those empty railgun cartridges (?) should be floating off into space, shouldnt they?

Deadlock989 wrote: ↑Mon Nov 30, 2020 2:17 pm There is no "global standard" when it comes to symbolic meaning.

There are plenty of de facto global standards for symbol meanings. Pick up practically any smartphone on Earth, and the mail app will have a red dot on it when there are new messages.

I'm a bit late to this, but 1.1 looks really super good at night.

About the new recipe badge, though: isn't a simple red circle the global standard for "new thing" these days? The yellow and black reminds me a lot of a warning sign.

I think the current lifecycle callbacks make the following case difficult to handle: There are two mods, Client and Service Service provides a remote interface Client optionally uses the interface during initialisation (and so declares an optional dependency on Service) Right off the bat, it smells ...

It definitely feels like there's a problem with the lifecycle logic Sure does. But it's what we got. I would go so far as to say that this is a design bug, and Wube should consider addressing it before 1.0. I think the solution is as simple as calling on_configuration_changed after on_init for new ...

I'm disappointed that this appears to be a hole in the API, but I've solved my problem by having my remote functions call on_load to link global tables if they haven't been linked yet.

Thanks everyone for your help!

Then create them when the client calls. It definitely feels like there's a problem with the lifecycle logic if I have to guard against uninitialised local variables. Shouldn't that be the whole point of on_load? Personally i use the on_init_config approach where i don't distunguish between the two ...

Right, but in the above scenario, when the Client mod calls the Service API in on_init, the Service mod will not have its local references to the global table yet.

Suppose I have two mods: Service and Client. Both mods work on their own, but Client needs to register something with Service if both are present. So: Client declares a dependency on Service so that its callbacks come after. Client implements on_init() and uses a remote API to register with Service....

Like the blue string displayed in the sidebar here:

Thanks yes a remote interface sounds like the way to do it.

That looks nice but the way Disco Science works is it composes a list of colours matching each ingredient. This can go to all seven science pack colours just in vanilla. Plus I think it would generally be a much bigger ask to have people annotate every recipe.

I made DiscoScience , which makes labs light up with the colour of the items they are consuming. The main source of requests for the mod are to support ingredients from other mods. At the moment, this involves putting new ingredient colours in a giant compatibility table. I would like other mod auth...

This should be fixed in Disco Science 0.16. Thanks for the help!

Thanks for the heads up! Just looking now.

Found it: it’s in the prototype data but not the API. https://wiki.factorio.com/Prototype/Rec ... chine_tint

It’s probably staring me right in the face, but where is the colour for chemical plant recipes defined?

Contains many more more suggestion into the direction of updating mods and/or the game before startup, after shutdown etc. Watch out for the topic titles! --ssilk Would it be possible to check for updates and show the prompt before loading the whole game? Since after an update the whole thing needs...

Disco Chemistry!

Slackie wrote: ↑Fri May 10, 2019 5:25 pm Having a bit of trouble completely parsing this.

"Lua API Documentation" is a link to the documentation he's referencing:

https://lua-api.factorio.com/