[0.17.66] Blueprint tooltip always includes loco and wagons, which is incorrect when BP Editor does not appear

We are aware of them, but they have low priority. We have more important things to do. They go here in order not to take space in the main bug thread list.
Post Reply
User avatar
TheBloke
Fast Inserter
Fast Inserter
Posts: 123
Joined: Mon Dec 03, 2018 2:48 am
Contact:

[0.17.66] Blueprint tooltip always includes loco and wagons, which is incorrect when BP Editor does not appear

Post by TheBloke »

Train locos and wagons are not included in blueprints by default, including in Copy blueprints. However, the blueprint tooltip will always show locomotives and wagons as being included in the blueprint.

Screenshots of using Copy on track + train

This is not a problem for standard BPs, as their default action is to open the Blueprint Editor, where the user can then tick Trains. So it's not illogical for the tooltip to include trains, given the user does have the option to include them.

However, in the case of:
  • Copy blueprints, when shift is not held
  • Standard blueprints, when shift is held
The blueprint editor will not appear, and therefore the tooltip is misleading and likely confusing when first encountered.

This is particularly an issue in the case of the Copy/Cut BPs, as it is wrong in the default and majority use case. It's also my opinion that Copy BPs are likely to become the standard method for replicating entities, given how quick and easy to use they are, and therefore it would be ideal if the tooltip could be correct when they are used.

I imagine this is already known about and it's certainly not too serious. I mention it now as I'm working on some documentation/tutorials for new 0.17 features, in preparation for the stable release, and find myself needing to tell the user to ignore the tooltip when using a Copy BP on trains, and that they must remember to hold shift when they want the trains included, despite what the tooltip says.

Expected Behaviour:

The blueprint tooltip does not include locos and wagons when:
  • A copy BP is dragged, without shift held
  • A normal BP is dragged, with shift held
Alternatively

An alternative change would be for Copy and Cut BPs to include trains by default - ie as if Trains were ticked in the BP Editor. That would make the tooltip accurate and would also, IMHO, be a useful usability gain.

At least in my personal experience, if I run a BP over trains I almost always want them included. And when not wanted, one could always just hold shift and untick Trains.

EDIT: Another reason to make Trains=included the default is that, as it stands, Cut BPs cannot be used to move trains, and in fact using a Cut BP on a train is currently a little broken. Let me know if you want this in another report, but in brief: Dragging a Cut BP over a section of track + train will result in the track being marked for deconstruction, but not the train. Thereafter the construction bots just hang there, trying to remove the track but unable to do so with wagons/locos on top. This requires manual intervention to resolve: one must either cancel the deconstruction of the track, or manually mark the train for deconstruction, else the bots will remain stuck.

Screenshots of using Cut on track + train

If one drags a Cut BP while holding Shift to bring up the BP Editor, one can then tick Trains, and this results in a working track+train BP. However, editing a Cut BP turns it into a Copy BP. Therefore there is no way to cut trains; one must copy them, then DP them.

Having trains be included by default in Copy and Cut BPs would seem to improve all these issues: the tooltip would be correct, it would be possible to Cut track+trains, and using Cut on track+trains would not jam. IMHO this would be a much more useful default than the present case of trains not being included.

posila
Factorio Staff
Factorio Staff
Posts: 5202
Joined: Thu Jun 11, 2015 1:35 pm
Contact:

Re: [0.17.66] Blueprint tooltip always includes loco and wagons, which is incorrect when BP Editor does not appear

Post by posila »

Thanks for the report.
I tried to see if it could be easily adjusted to fit the expectation, but it can't be done without some non-trivial changes and since I don't consider this to be an issue to begin with, I am moving it to the minor issues.

User avatar
TheBloke
Fast Inserter
Fast Inserter
Posts: 123
Joined: Mon Dec 03, 2018 2:48 am
Contact:

Re: [0.17.66] Blueprint tooltip always includes loco and wagons, which is incorrect when BP Editor does not appear

Post by TheBloke »

posila wrote:
Wed Aug 28, 2019 2:21 pm
Thanks for the report.
I tried to see if it could be easily adjusted to fit the expectation, but it can't be done without some non-trivial changes and since I don't consider this to be an issue to begin with, I am moving it to the minor issues.
OK, thanks checking and for the reply.

What about having trains be included by default in Copy/Cut BPs? As well as making the tooltip correct, it would also fix Cut BPs on trains, which are currently non-functional for two reasons:
* it's not possible to Cut trains, because you must filter to include trains, and you can't filter a Cut without it becoming a Copy
* currently, if you run a Cut on trains, it will mark the track but not the trains, and therefore construction bots will hang there indefinitely, trying to remove the track but being unable to do so because they still have trains on top.

IMHO this is a poor user experience, and worse than the incorrect Copy tooltip. But both issues could be solved if trains were included by default in Copy and Cut BPs, which I believe is also more intuitive.

posila
Factorio Staff
Factorio Staff
Posts: 5202
Joined: Thu Jun 11, 2015 1:35 pm
Contact:

Re: [0.17.66] Blueprint tooltip always includes loco and wagons, which is incorrect when BP Editor does not appear

Post by posila »

Create a thread in ideas and suggestions, I suppose. I am comfortable deciding about tooltip info, but I am not right person to decide how should Cut behave, but I don't think the current behavior can be classified as a bug.

Post Reply

Return to “Minor issues”