Skip to content

Buildcraft Robots do not seem to obey some conditions set by gates #23

@ShoobFloof22

Description

@ShoobFloof22
  • Forge Version: 47.4.0
  • BuildCraft Version (Add Hash if from github): 7.99.24.9 (the latest release from this Github fork, Is from late April, I think the 26th)

Steps to reproduce the behavior:

  1. Place a docking station on a Kinesis pipe, like you would normally do for robots
  2. Place a gate on the same segment of pipe
  3. Set conditions for the robot in that gate. For example, you could do "If Redstone Signal" then "Work in area" and provide a map location set by markers
  4. Robot ignores the conditions

An example of when I discovered this was when I built a tree farm. The way I always did this was by having a collection of three different types of bots. Picker, Planter and Lumberjack. I'd have a supply of axes, a supply of saplings, and a place for the Picker bots to deposit their items. These conditions worked fine. The Lumberjacks would be able to recognize that there is a pipe providing axes and they'd go get one. Same with the Planters, they'd get their saplings, and the Pickers would be able to deposit items correctly. Finally, their "home" is the docking station on kinesis pipes, since that's where they go when idle and it provides power to them. An example of how I normally programmed them here was by using Land Marks to create a large box, that being where they're allowed to perform tasks. So essentially it would contain the tree farm to that area. I'd then click a map location on these markers, so it saved the box coords and area to that item, and then I'd take it to the gates on the kinesis pipe and say "When there is a redstone signal, work in this area" and provide that map. That way if you gave the pipe a redstone signal, it would tell the bots to work in that area, and you could additionally turn the signal off and they'd just come back and dock.
That's what would normally happen. However, in this version, sometimes, if a task is available within render distance, the bots sometimes go and take off working before I'm even done programming the gate, and even if they don't, they go off and work anyway without a redstone signal. And regardless of if the gate is given a signal or not, they ignore the map location that sets their working area. They just go do their task anywhere they can. So that means Lumberjacks will chop down anything nearby made of logs, pickers will collect items from crazy far away, and planters will just put saplings wherever.

As far as I know, this is unintended behavior, as this exact setup worked fine in 1.7.10, the last time BC had Robots working. They'd stay in the area they were told to, and not operate unless given a redstone signal. Perhaps the logic changed and there's a different way of programming them, but this is the way I always did it, and it no longer works.

I would provide a game log here but there's no errors in it when this happens. It still happens, just doesn't log anything. If you could possibly investigate this and fix it, that would be greatly appreciated, because as it stands now, the robots are very difficult to use as they're basically uncontrollable as long as they have what they need to do whatever they're designed to do XD

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions