Page 1 of 1

[0.14.5] Tight Spot migration error REOPENED

Posted: Sun Jul 10, 2016 5:28 pm
by DaveMcW
Steps to reproduce:

1. Load a Tight Spot save from 0.12. Like this one:
tight spot 0.12.35.zip
(423.75 KiB) Downloaded 109 times
2. Press Start.

Expected result: The scenario auto-plays.

Actual result: "Error while running the event handler: Factorio/temp/currently-playing/tightspot.lua:198: Unknown item name: basic-transport-belt"

Re: [0.13.6] Tight Spot migration error

Posted: Sun Jul 10, 2016 6:13 pm
by Klonan
Thanks for the report :)

You should be able to unzip the file, and replace the control.lua with the 0.13 one from the scenarios,

But we should fix this migration regardless

Re: [0.13.6] Tight Spot migration error

Posted: Sun Sep 11, 2016 5:51 pm
by kovarex
I can load the save just fine in my 0.14 game, so I consider this fixed.

Re: [0.13.6] Tight Spot migration error

Posted: Sun Sep 11, 2016 6:05 pm
by DaveMcW
Not fixed, you forgot to do step 2 (press Start).

Error from version 0.14.5:

Code: Select all

Error while running event on_gui_click (ID 1)
Unknown item name: basic-transport-belt
stack traceback:
	...ta/Roaming/Factorio/temp/currently-playing/tightspot.lua:205: in function 'tightspot_sell_back'
	...ta/Roaming/Factorio/temp/currently-playing/tightspot.lua:216: in function 'tightspot_start_level'
	...ta/Roaming/Factorio/temp/currently-playing/tightspot.lua:346: in function 'action'
	C:/Program Files/Factorio/data/core/lualib/story.lua:86: in function 'story_update'
	...Data/Roaming/Factorio/temp/currently-playing/control.lua:67: in function <...Data/Roaming/Factorio/temp/currently-playing/control.lua:66>

Re: [0.13.6] Tight Spot migration error

Posted: Sun Sep 11, 2016 6:30 pm
by Loewchen
It causes that error for me as well; reopened.

Re: [0.14.5] Tight Spot migration error REOPENED

Posted: Sun Sep 11, 2016 6:49 pm
by kovarex
The solution is simple, start the level again from the main menu.
You can just use the picture of the preview to rebuild the level. And it will take 3 times less time than it took me to try to manually fix the internal level save to fix it.