Tested on v115 of GMS with map 921160100. It contains a "fieldScript" property which gets put into unsupportedInfoProperties of MapInfo. Can reproduce this issue on any version by adding a fake property in a maps info node.
The JSON serializer is infinite looping/just having issues in general trying to serialize MapleLib objects due to fields like Parent, WzFileParent, parent being a WzFile, WzObject, etc, resulting in having other fields like parent, and children, ending in the serializer essentially trying to save the entire wz as a JSON file.
An option is to note all these fields as [IgnoreDataMember] but I'm not sure how well that'll work when putting the property back as that is the purpose of unsupportedInfoProperties. Looks like parent gets set again so safe? but other parent objects still cause issues. Might have to strip all of this parent data on save using [IgnoreDataMember] then fix it after deserializing.
I assume additionalNonInfoProps and additionalProps will cause the same issue.
Tested on v115 of GMS with map
921160100
. It contains a "fieldScript" property which gets put intounsupportedInfoProperties
ofMapInfo
. Can reproduce this issue on any version by adding a fake property in a mapsinfo
node.The JSON serializer is infinite looping/just having issues in general trying to serialize MapleLib objects due to fields like
Parent
,WzFileParent
,parent
being aWzFile
,WzObject
, etc, resulting in having other fields like parent, and children, ending in the serializer essentially trying to save the entire wz as a JSON file.An option is to note all these fields as
[IgnoreDataMember]
but I'm not sure how well that'll work when putting the property back as that is the purpose ofunsupportedInfoProperties
. Looks like parent gets set again so safe? but other parent objects still cause issues. Might have to strip all of this parent data on save using[IgnoreDataMember]
then fix it after deserializing.I assume
additionalNonInfoProps
andadditionalProps
will cause the same issue.