[0.13] Train conditions don't follow Boolean precedence

[Adil]

In my book that is *not* formalised.

Shall we have a poll to define a convention for factorio?
Lua follows the `and` before `or` convention too, btw.

[Loewchen]

Shall we have a poll to define a convention for factorio?

Not in Bug reports. This game is not open source, it is is not about how many people think X is better, it is about how good the arguments for X convinced the devs, and they decided to not give it any priority.

[siggboy]

Shall we have a poll to define a convention for factorio?

Not in Bug reports. This game is not open source,

Does not really matter what this game is, if we feel like holding a poll, we're going to hold the poll. The devs are free to ignore any and all results of a poll. (No, I don't want to have the poll, just sayin'.)

Having said that, I think the idea to have a poll to define a convention is rather braindead.

The convention is "AND" takes precedence over "OR", only very few programming languages treat it differently (in those cases there's no precedence).

[siggboy]

Here's somebody being royally confused because of this on Reddit: https://www.reddit.com/r/factorio/comme ... ad/d6iwm4j

[HanziQ]

Fixed for the next release (I hope).

[siggboy]

Wut? Nice.

What is the fix? Are we getting the normal Boolean precedence order?

Thanks in any case

[The Real C]

Fixed for the next release (I hope).

Being said person that was royally confused on Reddit, this pleases me greatly! Good job!

(This also means that the update will break all my train stations, as I finally figured out how to make them work like I wanted with the "old" logic pattern, but that is a tiny price to pay for Progress!)