Page 1 of 1
[2.0.61] Belt building broken with smart belt building disabled.
Posted: Thu Jul 31, 2025 5:15 pm
by Merssedes
With new behaviour introduced in 2.0.61, specifically:
FactorioBot wrote: Wed Jul 30, 2025 4:50 pm
- When dragging belts, going forward and back will remove the extra belts built.
Belt building is now broken when smart building is disabled.
For example:
steps
1) drag the line forward
- Screenshot from 2025-07-31 20-01-42.png (224.8 KiB) Viewed 1091 times
2) move to the side
- Screenshot from 2025-07-31 20-01-56.png (161.44 KiB) Viewed 1091 times
3) drag the line backwards
- Screenshot from 2025-07-31 20-02-06.png (181.36 KiB) Viewed 1091 times
4) move to the original belt (one belt was removed)
- Screenshot from 2025-07-31 20-02-17.png (134.92 KiB) Viewed 1091 times
5) drag the line forward
- Screenshot from 2025-07-31 20-02-34.png (111.57 KiB) Viewed 1091 times
6) move to the side (one belt removed)
- Screenshot from 2025-07-31 20-02-46.png (136.47 KiB) Viewed 1091 times
7) drag the line backwards (most of the belts removed)
- Screenshot from 2025-07-31 20-02-59.png (138.81 KiB) Viewed 1091 times
Expected result: 2 fillly built lines of belts.
Actual result: 1 belt line is built with 1 piece missing, another has only 2 belt pieces built.
Suggested solution: disable this feature when smart belt building is disabled.
Re: [2.0.61] Belt building broken with smart belt building disabled.
Posted: Fri Aug 01, 2025 2:22 pm
by MEOWMI
I ran into this as well. Needless to say, I consider it a bug.
Re: [2.0.61] Belt building broken with smart belt building disabled.
Posted: Fri Aug 01, 2025 3:08 pm
by Kenira
Agreed, it makes building without smart belt building enabled really frustrating and i would love it to be disabled when smart building is disabled.
Re: [2.0.61] Belt building broken with smart belt building disabled.
Posted: Sun Aug 03, 2025 3:35 pm
by thedoh
It's also arguable that it's not "extra" belt in the first place.
Re: [2.0.61] Belt building broken with smart belt building disabled.
Posted: Mon Aug 04, 2025 12:46 pm
by Rseding91
Thanks for the report. This is now fixed for the next release.