SupplyDepoo wrote:Claudius1729 wrote:The reason queuing orders in RTS is so popular it's because it saves so many clicks and time.
Yeah, because in a traditional RTS you have many tasks to do in different places in a short amount of time. In Factorio there's no unlocked camera that can jump around, so there's no need for queuing actions.
There's already a feature in the game that saves a lot of time by queuing actions: it's robots + blueprints, so I'm not sure why you keep saying there's no need to queue actions where a lot of players actually enjoy that feature already and it is considered a core part of the game. I just want a limited version of that feature right from the start.
Besides, even when you have one unit, it's beneficial to queue orders and save time, because it frees you time in the immediate future to make other decisions, to think, to focus, to plan.
Just like when you begin a game of Supreme Commander, you have one unit, yet many players will queue orders right at the start. Or in MOBAs, where you usually control one unit, you can also queue orders sometimes to pre-plan stuff.
A tiny benefit in Factorio, that is true, but still a benefit to add to the main benefit, which I explain below.
Claudius1729 wrote:If one can save time and clicks in Factorio with a simple solution, then I feel that solution must be used.
You're not saving clicks with this idea, though. You literally just want to reverse the order of 1) go where you want to build something, 2) click.
At the very basic level, you would be planning better, and thus saving time. Put down the ghosts of the section in advance, then build them. Example:
Solution1: I could either put down two furnaces, four inserters, 12 belts, 2 poles, etc. which saves the time of walking multiple time along the bus, but not clicks.
Solution2: Or put down all the furnaces, then all the inserters, then all the belts, etc. Which saves a few clicks, but not the time of walking multiple times along the bus.
With ghosts+, I would have the better of the two world, and have the minimum amount of click of solution 2, and the time of solution 1.
Then when you combine it with blueprints, the gain of time is obvious.
Claudius1729 wrote:Why wouldn't you be able to place any more ghosts?
Nothing would prevent you from building more ghosts.
Because if I'm in range it'll automatically place the entity and you can't create ghosts without having at least one of that entity item.
That's not really an argument against the idea fundamentally. If we change ghosts, then we also should change ghosts limitation to accomodate for the idea. Make it require an action to construct ghosts in range, which would save a lot of clicks, or change the UI slightly.
As to what UI action would be better, what ghosts to prioritize, etc., those are still in the air.
Claudius1729 wrote:Also this feature would synergize well with blueprints (who will be more accessible in 0.15).
For instance I could make a blueprint of my basic furnace smelting unit, then place them rapidly in the guise of ghosts, then just build them.
Are you talking about making automated construction available earlier in the tech tree than flying robots? Because the devs are already aware of this issue. See
FFF-160. I'm sure they can come up with something better than your idea.
It's not technologically automated if the engineer is doing the construction. It's just serialized construction done quicker and better.
As I said before, it should not be a tech issue.
Your engineer is perfectly able to see and plan a few buildings in advance. In fact, by putting down the ghosts, you've given a list of instructions to the engineer that you could painfully execute click by click, or that could be done by the engineer as it's not rocket science.
And I'm glad the devs are aware of the issue, but then you should be aware that so far 0.15 isn't solving the issue from what we know, just making robots available earlier. Unless miraculously blueprints are available right at the start, and when I use them, my engineer will go build the ghosts. That is also what I am suggesting.