So, to make min_range apply to a weapon, the ammo needs to be target_type= position or direction, and clamp_position must be true on the ammo.
If you do that, the projectile's target position should be clamped to between the weapon's min_range and max_range.

Fixed for 0.16.21. There was special code handling the case where both drag and open entity were bound to the same thing (default, on left click), but it was just using the value of the drag binding for open entity regardless. It should now account for custom bindings (and do the same thing for crea...

So it seems that a single rail was marked as having a train on it, even though it a: didn't, b: couldn't, since it was not connected to anything. Not sure if it was just data corruption, or a bug, but I was able to fix the save, if you want to keep playing it (judging by the size, you very much do :...

Fixed for 0.16.19.
Thanks for the report!

Fixed for 0.16.19.
Thanks for the report!

Could you post exact steps to reproduce this issue? Including a blueprint string to test on?
I tried creating some blueprints with roboports in the middle and right clicking them, but couldn't reproduce it.

Fixed for 0.16.16.
Thanks for the report!

Could you post your log and save file?

The overlay bug is fixed for 0.16.16. As for the suggestion about flamethrowers targeting, I'd say make a thread over on the Ideas and Suggestions board. Personally, I'd be against it, as the current behaviour makes sense to me. I'd say, if you don't want your trains flamed, just don't build flame t...

Fixed for 0.16.16, using the method you suggested, @mikael9.
Thanks for the report!

So, I tested the setup you showed in our latest dev version and it doesn't seem like this is possible anymore. That said, we've changed the logic for "sliding" around obstacles a few times recently, and are likely to do so again before release. I'll keep an eye on it and try to make sure t...

Original issue fixed for 0.16.16.
As for the second issue, not fixed yet, but could you make a separate thread?

I can't reproduce this behaviour, unless you meant what's shown in the attached screenshot? In which case, it's not a bug, you're supposed to be able to walk across 1-tile thick tiny "rivers".
If not, could you please post a save showing the issue?

Fixed for 0.16.16.
Thanks for the report.

After some discussion, we've decided to leave both of these as-is, so I'm moving to not-a-bug.
Thanks for the report anyway, though.

Fixed for 0.16.16. Thanks for the report!
Also, side note, but this bug affects everything that can be enabled/disabled by circuit network, not just stations

There is an error displayed in the log file, which mod authors can use to ensure they conform.
Moving to not a bug for now, mod authors can use the log, and it doesn't matter for end users really.

Fixed for 0.16.13, thanks for the report!
The problem was that the code expected every x.y version to have a subversion x.y.0. Which it does, in the actual factorio changelog. Starting with 0.0.1 is reasonable though, so it should be supported.

Fixed for 0.16.7
Thanks for the report!

No problem
Let me know if it happens again when you're definitely running in screen, but I think that was probably the problem.