Version 0.17.29

[Shadewing]

Here is a link to my suggestion for bringing back obstacle avoidance without the loss of most of the simplified planner benefits.
viewtopic.php?f=6&t=69448

[Sente]

I would also like to have obstacle avoidance for ghost rail-building back. I really appreciated that feature quite a bit. I use it pretty extensively in my games.

[nuhll]

Is it correct that u cant place blueprint books in blueprint books? Or is it a bug?

[mward]

1. Clicking without shift:
   1. If the whole rail is within reach: direct build mode
   2. When any part of the rail gets out of reach, automatically switch to ghost build mode while avoiding obstacles"
2. Clicking with shift or pressing shift enters ghost build mode while removing obstacles. Releasing shift switches back to the other mode (avoiding obstacles either direct build or ghost build depending on the range)

If you really must place a short length of ghost which is within reach, and do not want to direct build it, then you simply have to move out of range first.

This allows cliff avoiders to carry on avoiding cliffs, but also follows the player's natural instinct to press shift when they are ghost buiding and see an obstacle that they want the bots to remove.

[leadraven]

1. Clicking without shift:
   1. If the whole rail is within reach: direct build mode
   2. When any part of the rail gets out of reach, automatically switch to ghost build mode while avoiding obstacles"
2. Clicking with shift or pressing shift enters ghost build mode while removing obstacles. Releasing shift switches back to the other mode (avoiding obstacles either direct build or ghost build depending on the range)

If you really must place a short length of ghost which is within reach, and do not want to direct build it, then you simply have to move out of range first.

This allows cliff avoiders to carry on avoiding cliffs, but also follows the player's natural instinct to press shift when they are ghost buiding and see an obstacle that they want the bots to remove.

It is a terrible idea to involve reach into building control.

[Shingen]

1. Clicking without shift:
   1. If the whole rail is within reach: direct build mode
   2. When any part of the rail gets out of reach, automatically switch to ghost build mode while avoiding obstacles"
2. Clicking with shift or pressing shift enters ghost build mode while removing obstacles. Releasing shift switches back to the other mode (avoiding obstacles either direct build or ghost build depending on the range)

If you really must place a short length of ghost which is within reach, and do not want to direct build it, then you simply have to move out of range first.

This allows cliff avoiders to carry on avoiding cliffs, but also follows the player's natural instinct to press shift when they are ghost buiding and see an obstacle that they want the bots to remove.

It is a terrible idea to involve reach into building control.

I agree it's a bad idea, and also that doesn't solve the issue of having too many different building states, which is what Wube seem to have wanted to simpllify.
Which, btw., i also think was a bad idea.

#TeamMoreOptions

[mward]

I agree it's a bad idea,

Why is it a bad idea? What is bad about it?

With any other blueprint placing, if I see an obstacle I hold shift to place the blueprint while removing the obstacle. This makes the same function work with rails.

[5thHorseman]

I agree it's a bad idea,

Why is it a bad idea? What is bad about it?

With any other blueprint placing, if I see an obstacle I hold shift to place the blueprint while removing the obstacle. This makes the same function work with rails.

Rails are fundamentally different than all other objects, in that you can (and actually must in some circumstances) place them by using a unique mode. It's reasonable to expect that mode has other unique qualities to make it work better.

[Shingen]

I agree it's a bad idea,

Why is it a bad idea? What is bad about it?

With any other blueprint placing, if I see an obstacle I hold shift to place the blueprint while removing the obstacle. This makes the same function work with rails.

that "I agree it's a bad idea" was a response to involving REACH into building and now you're talking about something completely different.
firstly, reach is not involved in any other building IIRC (besides obviously being/not being able to manually place something further away),
secondly, it already worked in such a way that holding shift placed a ghost and marked obstacles for deconstruction.

if anything, they actually made it work the same as other objects that without shift you always place that object manually, while with it you place a ghost and decon obstacles.
the problem is, we think they shouldn't.

but i understand their point, and i think i would personally prefer to have a separate "rail planner" item with appropriate options/checkboxes to remove obstacles or not (and also options to build 2 parallel rails with automatic signals etc.), and keep the rail item to work like any regular item, or leave it working the way it works now.

[jockeril]

I agree it's a bad idea,

Why is it a bad idea? What is bad about it?

With any other blueprint placing, if I see an obstacle I hold shift to place the blueprint while removing the obstacle. This makes the same function work with rails.

[...]

but i understand their point, and i think i would personally prefer to have a separate "rail planner" item with appropriate options/checkboxes to remove obstacles or not (and also options to build 2 parallel rails with automatic signals etc.), and keep the rail item to work like any regular item, or leave it working the way it works now.

Anything but another item I'd rather they make an option in the options -> other menu to have the old way or the new way then have another item in my already too small inventory, especially at the start - or they can add a button to the new addition to the quickbar to toggle that behaviour

[BlueTemplar]

Planners don't necessarily take space : they can be kept in your blueprint library.

[nuhll]

Planners don't necessarily take space : they can be kept in your blueprint library.

Hahahah lol, u can, but they loose your settings (dont know which genius thought that this would be a good idea)

[BlueTemplar]

Well, then they shouldn't. (Hopefully this will changed in the current blueprint rework.)

[nuhll]

I also hope. It makes so much sense. You have upgrade and remove next to your hotbar, can change the settings (and they get saved) if you want to have multiple settings, you just drop it into your inventar (like its now). Problem solved.