It appears json.decode is not working (Case 19249) build .971. [import]uid: 21331 topic_id: 33570 reply_id: 333570[/import]
In the recent builds the internal json stuff has changed slightly and is now more strict about things like missing/trailing commas etc You will want to validate your json data is correct as that messed us up for a while ( turns out I got lazy about this stuff when it was less strict ) [import]uid: 119420 topic_id: 33570 reply_id: 133451[/import]
Thanks again for taking the time to give me a heads-up. One comma. [import]uid: 21331 topic_id: 33570 reply_id: 133557[/import]
No worries. We were hit by missing commas in places, extra trailing commas in others. Even one case where it didn’t like the number 05 when it was meant to be 5.
Every scene in Forever Lost is described via json layouts so there were lots of files to validate. [import]uid: 119420 topic_id: 33570 reply_id: 133559[/import]
In the recent builds the internal json stuff has changed slightly and is now more strict about things like missing/trailing commas etc You will want to validate your json data is correct as that messed us up for a while ( turns out I got lazy about this stuff when it was less strict ) [import]uid: 119420 topic_id: 33570 reply_id: 133451[/import]
Thanks again for taking the time to give me a heads-up. One comma. [import]uid: 21331 topic_id: 33570 reply_id: 133557[/import]
No worries. We were hit by missing commas in places, extra trailing commas in others. Even one case where it didn’t like the number 05 when it was meant to be 5.
Every scene in Forever Lost is described via json layouts so there were lots of files to validate. [import]uid: 119420 topic_id: 33570 reply_id: 133559[/import]