Factorio Forums

This was previously on the Reddit forum because I didn't know there was an official one.

https://www.reddit.com/r/factorio/comme ... lls_makes/


Basic Jist is that there are no robots flying to me (75/75 robots in inv). There is no stationary or other robo ports in the area. Only like 300 or 600 max logistics robots moving fuel to trains far away and not connected to roboports even close to here. This is repeatable without fail and happens with spidertrons. I have PLENTY of repair packs. No mods. Factory is not that big compared to anyone megabase. This also would happen from the beginning of the game when I got a personal roboport. That means it has been happening from before I had other stationary roboports.

Post the save, see 3638.

Part of a roboport network, port based bots already on the way?
They'd need to have repair packs aviable, in chests or roboport, then they'd get a repair job assigned.

If the job is already assigned, your personal bots won't do anything.
The land based ones could be miles away, the game won't abort their job when your personal port comes in range.

But when a new job opens (you, shooting the wall), your bots will have priority over land based bots (if you have repair packs with you to get that job assigned)

The walls get instantly repaired in the save provided.

Loewchen wrote: Fri Apr 23, 2021 1:28 am The walls get instantly repaired in the save provided.

Did you damage the walls or did you go over to some already damaged walls?

Loewchen wrote: Fri Apr 23, 2021 1:28 am The walls get instantly repaired in the save provided.

Someone else on that Reddit post is also having this problem so it's not like it's isolated. It's a problem with walls being damaged before I walk into range to repair. You saw the video right? I'm no moron Everything should be working but they aren't. And the robots repair walls that I shot instantly but take forever to notice the already damaged ones.

I'll assume 28675 since the save has thousands of unbuildable ghosts.
If you find a bug after all, make a new report following 3638.