Fetching wrong update (experimental instead of stable)

[narc0tiq]

Fetching wrong update (experimental instead of stable)

[bioxz]

I think i got the problem: The updates are stored in a map (current version, next version). The update (0.13.18, 0.13.19) is later getting overwritten by (0.13.18, 0.14.0), right? So using the current_version as a unique identifier isn't working.

[bioxz]

I have proposed pull request #12 as a fix for this problem.

[narc0tiq]

The update (0.13.18, 0.13.19) is later getting overwritten by (0.13.18, 0.14.0)

How unpleasant. And, of course, if they'd been presented in the opposite order we'd never have met this bug.

[bioxz]

Now they have released 0.13.20 as experimental. So there is 0.13.19 as latest stable, 0.13.18 as latest point to upgrade to 0.14.0 and experimental releases in 0.13 and 0.14. Seems like the updater does support all of this, but it's weird that there is no way to get to 0.14.x from Factorio >= 0.13.19.

[narc0tiq]

I understand .20 went into the stable track very soon after your comment, but it's really not a setup they'd thought about before, is it?