[FIXED] [0.9.108-PUBLIC#5358] Cannot interact with Anno

Mumon

Member
Jun 26, 2022
12
0
26
Code:
Version: 0.9.108-PUBLIC-ELECTRON#5358 Message: Can't call IncrementFlag on ANNO_SEXED because it's not a number based value, it's "13Nice. Now so’re you.11111111111111111111111", typeof "string"! Stack:
TiTSException: Can't call IncrementFlag on ANNO_SEXED because it's not a number based value, it's "13Nice. Now so’re you.11111111111111111111111", typeof "string"!
    at h (file:///./resources/app/main.01a06689.js:1:9893235)
    at $ (file:///./resources/app/main.01a06689.js:1:10769265)
    at o.value (file:///./resources/app/main.01a06689.js:1:77924)
    at Object.window.annoFollowerApproach [as func] (file:///./resources/app/content_follower.a50298ff.js:1:1564433)
    at e.value (file:///./resources/app/main.01a06689.js:1:17885157)
    at Object.freeze.s.FUNCTIONS (file:///./resources/app/main.01a06689.js:1:34235256)
    at HTMLDocument. (file:///./resources/app/main.01a06689.js:1:12207251)
    at HTMLDocument.o (file:///./resources/app/vendors.27568aa7.js:1:48987)
(10:03:26.793) (Core) info: GameState postLoad()
(10:03:28.807) (Serialization) info: Setting gameloading marker false
(10:03:34.011) (UserInterface) info: Pushing [I]"Main Text"[/I] to UI state stack, replacing with "Rest".
(10:03:37.255) (UserInterface) info: Popping from [I]"Rest"[/I] and setting [I]"Main Text"[/I] as active state.
(10:03:45.767) (UserInterface) info: Pushing [I]"Main Text"[/I] to UI state stack, replacing with "Trade".
(10:03:51.384) (UserInterface) info: Popping from [I]"Trade"[/I] and setting [I]"Main Text"[/I] as active state.
(10:03:51.393) (ImagePack) info: Has Images Available For Download: Yes 46. Approx. 5.50 mbytes.
(10:04:24.481) (Serialization) info: ImageGalleryStateStorage has been saved.
(10:04:33.901) (Core) fatal: Can't call IncrementFlag on ANNO_SEXED because it's not a number based value, it's "13Nice. Now so’re you.11111111111111111111111", typeof "string"!
 

lowercase_donkey

Scientist
Apr 27, 2016
1,569
218
I had a fix for this in the most recent patch, but it was inadequate. A more complete fix should be in the next patch. Ty for reporting!