[A20 r693 (x64)] Zoning Error

Support Resolved Reports
1

spam some 1x1 farming zones…
Zones can no longer be accessed, the ui does not show up. This is true for new storage zones as well.
Game will not save & Esc Menu Stops working. Only solution is to close the game.

I checked the folder again, the save actually went through! here it is:
1484681242044.rar (5.6 MB)
here is the save before I did this…not sure how helpful it will be
auto_save error.rar (5.7 MB)
stonehearth.log (215.2 KB)

2

Did you try with F5? That solves it for me.
This is the error that appears:

Uncaught Error: Assertion Failed: calling set on destroyed object
Error: Assertion Failed: calling set on destroyed object
    at r (http://radiant/stonehearth/ui/root/js/libs/ember-1.8.1.min.js:4:18375)
    at Object.n.assert (http://radiant/stonehearth/ui/root/js/libs/ember-1.8.1.min.js:2:88)
    at y (http://radiant/stonehearth/ui/root/js/libs/ember-1.8.1.min.js:5:16885)
    at n.set (http://radiant/stonehearth/ui/root/js/libs/ember-1.8.1.min.js:8:25617)
    at http://radiant/stonehearth/ui/game/modes/zones_mode/farm/farm.js:110:18
    at c (http://radiant/stonehearth/ui/root/js/libs/jquery-1.10.2.min.js:4:26036)
    at Object.fireWith [as resolveWith] (http://radiant/stonehearth/ui/root/js/libs/jquery-1.10.2.min.js:4:26840)
    at i.(anonymous function) (http://radiant/stonehearth/ui/root/js/libs/jquery-1.10.2.min.js:4:27824)
    at foward_fn (http://radiant/radiant/js/radiant/object.js:144:22)
    at finish_fn (http://radiant/radiant/js/radiant/object.js:149:16)
3

Ah! I forgot to try it, that might have fixed it.

Its wierd tho, because the ESC menu would show up but not allow me to click on anything so I didn’t think it was something that a ui refresh would solve- its not like the entire ui froze up, it was just not allowing clicking.

4

Got a UI Error popup, so I’m posting it here since I figured you guys would want to see it.

release-687 (x64)
Uncaught Error: Assertion Failed: calling set on destroyed object
Error: Assertion Failed: calling set on destroyed object
    at new Error (native)
    at Error.r (http://radiant/stonehearth/ui/root/js/libs/ember-1.8.1.min.js:4:18375)
    at Object.n.assert (http://radiant/stonehearth/ui/root/js/libs/ember-1.8.1.min.js:2:88)
    at y (http://radiant/stonehearth/ui/root/js/libs/ember-1.8.1.min.js:5:16885)
    at p.default._.create.set (http://radiant/stonehearth/ui/root/js/libs/ember-1.8.1.min.js:8:25617)
    at http://radiant/stonehearth/ui/game/modes/zones_mode/farm/farm.js:20:27
    at c (http://radiant/stonehearth/ui/root/js/libs/jquery-1.10.2.min.js:4:26036)
    at Object.p.fireWith [as resolveWith] (http://radiant/stonehearth/ui/root/js/libs/jquery-1.10.2.min.js:4:26840)
    at i.(anonymous function) (http://radiant/stonehearth/ui/root/js/libs/jquery-1.10.2.min.js:4:27824)
    at foward_fn (http://radiant/radiant/js/radiant/object.js:144:22)

had to knock out the second t in http so the system wouldn’t detect them as links

2 Likes
5

Thanks for the report @Krinkles, and welcome to the Discourse! I’ve put the UI Error inside of a code block, that prevents Discourse from attempting to auto-hyperlink them.

What were you doing when this error popped up?

1 Like