[2.1.11] Blueprints of storage chests contain new unnecessary data import_from when comparing with 2.0.77

Bugs that are actually features.
mbdevpl
Manual Inserter
Manual Inserter
Posts: 3
Joined: Wed May 28, 2025 2:46 am
Contact:

[2.1.11] Blueprints of storage chests contain new unnecessary data import_from when comparing with 2.0.77

Post by mbdevpl »

What did you do?
I made a blueprint of a storage chest that has the storage filter set, and exported such blueprint to a string, then I decode the string to JSON to see what it contains.
What happened?
I see the storage chest's filter contains the import_from entry that is related to space requests (set to default value for that item).

Example exchange string from Factorio Space Age 2.1.11:

0eNptkF1qAzEMhO+iZzdsQhxYQ09SQnA2SipYWxvZThsW3z3ypj8Uip88zOjTaIbjWHASihncDDRwTODeZkh0iX5sWvQBwUHKLP6CL8M7pgzVAMUTfoJb170BjJky4TO6fO6HWMIRRQ3m/xEGJk6a4tgoOmm3sgbu4LqV1fGC16K2w5nGjJKaJ+HQ7E/KN97Aj+OP+sX8YD4p6lr8qEupEFmCFjMwcJi8eN1J1ddFKO0KmqUwsShaOLSELzdKUPf6WlnK2OTfwxm4KX8pYneb3m43237d9baztT4AOkR2Nw==

JSON fragment in focus:

Code: Select all

            "filters": [
              {
                "index": 1,
                "name": "wood",
                "quality": "normal",
                "comparator": "=",
                "count": 1,
                "import_from": "nauvis"
              }
            ]
Full decoded JSON:

Code: Select all

{
  "icons": [
    {
      "signal": {
        "name": "storage-chest"
      },
      "index": 1
    }
  ],
  "entities": [
    {
      "entity_number": 1,
      "name": "storage-chest",
      "position": {
        "x": 6.5,
        "y": 0.5
      },
      "request_filters": {
        "sections": [
          {
            "index": 1,
            "filters": [
              {
                "index": 1,
                "name": "wood",
                "quality": "normal",
                "comparator": "=",
                "count": 1,
                "import_from": "nauvis"
              }
            ]
          }
        ]
      }
    }
  ],
  "item": "blueprint",
  "version": 562954249109505
}
What did you expect to happen instead? It might be obvious to you, but do it anyway!
Since I don't think there's anything that changed related to storage chests between 2.0 and 2.1, I expected to see it doesn't contain such entry, which was the case in 2.0.77.

Example exchange string from Factorio Space Age 2.0.77:

0eNptUNkKwjAQ/Jd9joJi1Rb8EhGJddVAs6k5PCj9dyf1QpBAIJM5drajXZO49UYiVR2Z2kmgat1RMEfRTcZEW6aKQnReH3lUnzhE6hUZ2fONqkm/UcQSTTT8lA6P+1aS3bEHQf23UNS6AJWTnAKn0XRcKLpDMS7g7/mcwNseTBPZh0wKXGf+M+adr+jD+EFfoVfn9sg6J91gKgDivEUzRbWzrfYaQwFdDUDKa0AjnFzLRLb4+65I0QVBw8jFfFrOyrJYzuYLXH3/ABeabkg=

JSON fragment in focus:

Code: Select all

            "filters": [
              {
                "index": 1,
                "name": "wood",
                "quality": "normal",
                "comparator": "=",
                "count": 1
              }
            ]
Full decoded JSON:

Code: Select all

{
  "icons": [
    {
      "signal": {
        "name": "storage-chest"
      },
      "index": 1
    }
  ],
  "entities": [
    {
      "entity_number": 1,
      "name": "storage-chest",
      "position": {
        "x": -2.5,
        "y": 1.5
      },
      "request_filters": {
        "sections": [
          {
            "index": 1,
            "filters": [
              {
                "index": 1,
                "name": "wood",
                "quality": "normal",
                "comparator": "=",
                "count": 1
              }
            ]
          }
        ]
      }
    }
  ],
  "item": "blueprint",
  "version": 562949958467584
}
In both 2.1.11 and 2.0.77 such chest looks as follows (showing filtered item with count 1):
Screenshot from 2026-07-19 19-09-45.png
Screenshot from 2026-07-19 19-09-45.png (36.97 KiB) Viewed 105 times
Does it happen always, once, or sometimes?
Always, reproduction steps:

1. open Factorio Space Age version 2.1.11 (or 2.0.77) - in my case Linux build downloaded from the Factorio website
2. start a new game (default settings)
3. press ~ to open console
4. type /editor twice in console to enter editor
5. give yourself a storage chest
6. place it in the world
7. exit the editor
8. pick wood you start the game with, set the chest filter to wood
9. make blueprint of just the chest
10. export it to exchange string
11. decode and inspect the JSON data

P.S.

The storage chest filter also probably doesn't need to store the count (usually set to 1) and I'm not sure how but I found that in some of my blueprints the storage chest filter count is set to 0 instead of the usual 1 (which you can see in-game, as the Barrel filter doesn't have a number in the screenshot below), but I'm not sure how to create those or from which Factorio version these are.
Screenshot from 2026-07-19 19-09-53.png
Screenshot from 2026-07-19 19-09-53.png (33.99 KiB) Viewed 105 times
User avatar
boskid
Factorio Staff
Factorio Staff
Posts: 4707
Joined: Thu Dec 14, 2017 6:56 pm
Contact:

Re: [2.1.11] Blueprints of storage chests contain new unnecessary data import_from when comparing with 2.0.77

Post by boskid »

Thanks for the report. Given that this has no in game effects and it is based on implementation details, i am going to classify this as Not a bug.

Implementation detail is that storage chests keep the storage filter as part of logistic section, even if the gui does not show logistic sections. Given that 2.1 includes an "import from any" feature, value of import_from can no longer be optimized for blueprint string because lack of value has different meaning than default value and as such whenever logistic sections are saved, import_from value for item filters is always saved.
mbdevpl
Manual Inserter
Manual Inserter
Posts: 3
Joined: Wed May 28, 2025 2:46 am
Contact:

Re: [2.1.11] Blueprints of storage chests contain new unnecessary data import_from when comparing with 2.0.77

Post by mbdevpl »

I see! I agree, an intended difference is definitely not a bug, thank you for clarifying! I didn't realise that the logistic filter field in storage chests uses same logic as in other places, but it makes perfect sense for it to do so.
Post Reply

Return to “Not a bug”