[0.9.062-BACKER#3601] Error from Loftcakes

auraen714

Member
Jul 30, 2021
20
6
28
Using lemon loftcakes to increase height repeatedly in inventory without exiting and moving gave me an error. May also be possibly double clicking the exit inventory button? Not entirely sure.

Message: Failed to find a UI state to apply. Stack:
TiTSException: Failed to find a UI state to apply.
at h (file:///C:/Users/nrott/OneDrive/Desktop/fenoxo/TiTS-backer-0.9.062-win/resources/app/main.5f6303ce.js:1:9686936)
at e.value (file:///C:/Users/nrott/OneDrive/Desktop/fenoxo/TiTS-backer-0.9.062-win/resources/app/main.5f6303ce.js:1:17190965)
at Object.y [as returnFromInventory] (file:///C:/Users/nrott/OneDrive/Desktop/fenoxo/TiTS-backer-0.9.062-win/resources/app/main.5f6303ce.js:1:17113104)
at o.value (file:///C:/Users/nrott/OneDrive/Desktop/fenoxo/TiTS-backer-0.9.062-win/resources/app/main.5f6303ce.js:1:11870510)
at file:///C:/Users/nrott/OneDrive/Desktop/fenoxo/TiTS-backer-0.9.062-win/resources/app/main.5f6303ce.js:1:11762062
at file:///C:/Users/nrott/OneDrive/Desktop/fenoxo/TiTS-backer-0.9.062-win/resources/app/main.5f6303ce.js:1:10391445
(22:33:40.790) [Core] info: GameState postLoad()
(22:34:36.116) [UserInterface] warning: Ensure we have good UI for waiting for data acquisition.
(22:38:06.245) [Serialization] info: GameOptions have been saved.
(22:38:08.962) [Inventory] info: Attempting to use item "LemonLoftcake"
(22:38:10.832) [Inventory] info: Attempting to use item "LemonLoftcake"
(22:38:12.887) [Inventory] info: Attempting to use item "LemonLoftcake"
(22:38:15.279) [Inventory] info: Attempting to use item "LemonLoftcake"
(22:38:17.462) [Inventory] info: Attempting to use item "LemonLoftcake"
(22:38:19.368) [Inventory] info: Attempting to use item "LemonLoftcake"
(22:38:21.439) [Inventory] info: Attempting to use item "LemonLoftcake"
(22:38:23.476) [Inventory] info: Attempting to use item "LemonLoftcake"
(22:38:25.096) [undefined] fatal: Failed to find a UI state to apply. ```
 

lowercase_donkey

Scientist
Apr 27, 2016
1,614
230
We are working on a fix for this. For now it seems to be caused by doing something too fast for your device. Go a little slower as a work around.