Version 0.16.49

[FactorioBot]

Bugfixes

• Fixed belts in blueprints weren't selectable in the blueprint GUI.
• Fixed bad mouse-point when holding blueprints with belts.
• Fixed wrong connectivity in underground belt fast replace. (60589)

Use the automatic updater if you can (check experimental updates in other settings) or download full installation at http://www.factorio.com/download/experimental.

[DRY411S]

Does this also fix 60844? viewtopic.php?f=7&t=60844

[SuperSandro2000]

Does this also fix 60844? viewtopic.php?f=7&t=60844

yes they fixed it.

[DRY411S]

Does this also fix 60844? viewtopic.php?f=7&t=60844

yes they fixed it.

So why isn't it in the bugfixes list above?

I hate to say this, but the devs are getting a bit sloppy with these latest releases.

[Wackerstamfer]

I hate to say this, but the devs are getting a bit sloppy with these latest releases.

I suggest you read this:https://www.factorio.com/blog/post/fff-242

Why are there suddenly so many problems with save loading in experimental?
0.16.36 is stable, but as we needed to fix some additional bugs, we started releasing experimental releases 0.16.37 up to 0.16.42 and so on. From the perspective of the player, there were a lot of new bugs introduced, unloadable saves, weird train problems, or even the infamous version 0.16.40 that disabled all signals causing trainocalypse which even made a baby cry.

Most of these problems (apart from the trainocalypse) were actually caused on purpose. It might sound weird, but it should make sense to you soon.

[dasiro]

blueprint from ghost can't be placed 60848 is also fixed


p.s. factoriobot hasn't updated the steamnews yet

[DRY411S]

I hate to say this, but the devs are getting a bit sloppy with these latest releases.

I suggest you read this:https://www.factorio.com/blog/post/fff-242

Sure but to introduce a bug in 0.16.48 then fix it it in 0.16.49, but fail to mention it in the release notes IS sloppy.

[dasiro]

Sure but to introduce a bug in 0.16.48 then fix it it in 0.16.49, but fail to mention it in the release notes IS sloppy.

then they're sloppy with the release notes, not the release itself

[Merssedes]

Is automatic update fixed for .47->.48 switch?

[Dragony]

Update from .48 to .49 fails with "File [long path]/factorio.exe has unexpected content". Anyone else?

[Loewchen]

Update from .48 to .49 fails with "File [long path]/factorio.exe has unexpected content". Anyone else?

This does not belong here, check the bug forum.

[bobingabout]

Sure but to introduce a bug in 0.16.48 then fix it it in 0.16.49, but fail to mention it in the release notes IS sloppy.

then they're sloppy with the release notes, not the release itself

There's actually a few instances of that.

The first features I programmed in weren't in the log, because I didn't know how to update the log at the time.

In short, if the author of the fix doesn't update the log, it doesn't get logged.

[dasiro]

I didn't know you did work for wube, but it explains why your mods are so elaborate

[Jap2.0]

I didn't know you did work for wube, but it explains why your mods are so elaborate

He doesn't work for Wube, he just has source access (and makes use of it occasionally).

[bobingabout]

I didn't know you did work for wube, but it explains why your mods are so elaborate

He doesn't work for Wube, he just has source access (and makes use of it occasionally).

Rarely. I've made about half a dozen commits total, on 2 features.

[dasiro]

I didn't know you did work for wube, but it explains why your mods are so elaborate

He doesn't work for Wube, he just has source access (and makes use of it occasionally).

doing work for is not the same as working for, but I get the confusion