Create

Create

86M Downloads

setSchedule() sets incorrect sequence of destinations

QuicksilverBou opened this issue ยท 2 comments

commented

Describe the Bug

When I use setSchedule method on train station a schedule and send the train, it goes to wrong destonation. I use a schedule that I discribe bellow and it swap two last station (C and D).

Reproduction Steps

  1. Build rail road
  2. Place Train Station and name each of that ("A", "B", "C", "D")
  3. Run the schedule that I discribe bellow

Expected Result

Train visit each train station in course.

Screenshots and Videos

No response

Crash Report or Log

no crash

Operating System

Windows 11

Mod Version

0.5.1f

Minecraft Version

1.19.2

Forge Version

43.2.17

Other Mods

In my mod build i have Create: Steam 'n' Rails, Create Stuff & Additions, Create: New Age and many addons. But in my issue i didn't use them.

Additional Context

Schedule of train

schedule = {
  cyclic = false,
  entries = {
    {
      instruction = {
        data = {
          text = "A",
        },
        id = "create:destination",
      },
      conditions = {
        {
          {
            data = {},
            id = "create:powered",
          },
        },
      },
    },
    {
      instruction = {
        data = {
          text = "B",
        },
        id = "create:destination",
      },
      conditions = {
        {
          {
            data = {},
            id = "create:powered",
          },
        },
      },
    },
    {
      instruction = {
        data = {
          text = "C",
        },
        id = "create:destination",
      },
      conditions = {
        {
          {
            data = {},
            id = "create:powered",
          },
        },
      },
    },
    {
      instruction = {
        data = {
          text = "D",
        },
        id = "create:destination",
      },
      conditions = {
        {
          {
            data = {},
            id = "create:powered",
          },
        },
      },
    },
  },
}```
commented

As the pinned issue says, make sure to search for your issue before making a duplicate issue.

commented

Duplicate of #5964 (fixed in c013173)