Thinkcrown
March 15th, 2026, 20:01
A few maps have been silently crashing when opened (blank, with blank in the layers/editing section). When clicking the button to expand them to the desktop, the console reports the following error:
[3/15/2026 1:09:51 PM] [ERROR] API: System.InvalidOperationException: No head found. Cycle or invalid data. at DAAODGMMAPE.IIEFABIBPOE (System.Collections.Generic.List`1[T] HKLENLFEHIE) [0x00096] in <b600322ea27a4b56b7e84cd63d093a92>:0 at DAAODGMMAPE.JDBKBKCOKGD () [0x00071] in <b600322ea27a4b56b7e84cd63d093a92>:0 at FG.ImageControlUI.NBKPLCGIFNM (FAMHIHGHNFC BHLCOBGDGPC, LKBBEJPOGJG ONBOFNKGDJI) [0x00047] in <b600322ea27a4b56b7e84cd63d093a92>:0 at FG.ImageControlUI.BuildImage () [0x0009f] in <b600322ea27a4b56b7e84cd63d093a92>:0 at HDACBIMOOAJ.NBFPBOBCPOB (UnityEngine.Vector2 CKEBNJKBOBJ, System.Double EJGCGPDDFNB) [0x0002b] in <b600322ea27a4b56b7e84cd63d093a92>:0 at LBOKCEJMKEH.FINOEJDLGOO (HDACBIMOOAJ JONBOGMOEOM, System.Int32 PHEIFCEIGBH) [0x00039] in <b600322ea27a4b56b7e84cd63d093a92>:0 at HDACBIMOOAJ.CNGFAPKBEFF (System.IntPtr FAMBEIDCDAM) [0x0000e] in <b600322ea27a4b56b7e84cd63d093a92>:0
google ai "believes" it has to do with folders/layers being incorrectly parented/siblinged into a recursive loop.
tried all backups--none fix the maps in question.
checked the map images themselves. They're fine.
turned off all extensions. Issue persists regardless.
In the db.xml: In the layers section of one of the maps in question, I removed all folders code, as well as changed all parentid tags to a simple <parent />, and removed all sibling tags, and that at least lets the map run, but only the one bitmap not in a folder survived (or rather, is visible to the host). Tokens exist on map, and the ray tracing line of sight wall mechanics still function when a token is selected, even though the layer with said wall mechanics tied to it doesn't render in the layers section.
tried re-parenting them to a new folder, but wasn't able to--might be too exhausted to brain-make-work.
I assume v5.1.6 restructured layering, and-or fixed whatever weas making the layer system wonky the past month (when these maps were made). The wonkiness causing some layers to incorrectly attribute who their parent/sibling is, causing the loop only now, after 5.1.6 fixed the issue allowing the corruption.
maps were working last week at session time Sunday, and on Monday.
I'll try fixing the sibling/parent structure in the db.xml tomorrow myself, but I'd love any advice, or uh... reassurance of a patch-patch or... Etc.
Thank you for taking the time.
[3/15/2026 1:09:51 PM] [ERROR] API: System.InvalidOperationException: No head found. Cycle or invalid data. at DAAODGMMAPE.IIEFABIBPOE (System.Collections.Generic.List`1[T] HKLENLFEHIE) [0x00096] in <b600322ea27a4b56b7e84cd63d093a92>:0 at DAAODGMMAPE.JDBKBKCOKGD () [0x00071] in <b600322ea27a4b56b7e84cd63d093a92>:0 at FG.ImageControlUI.NBKPLCGIFNM (FAMHIHGHNFC BHLCOBGDGPC, LKBBEJPOGJG ONBOFNKGDJI) [0x00047] in <b600322ea27a4b56b7e84cd63d093a92>:0 at FG.ImageControlUI.BuildImage () [0x0009f] in <b600322ea27a4b56b7e84cd63d093a92>:0 at HDACBIMOOAJ.NBFPBOBCPOB (UnityEngine.Vector2 CKEBNJKBOBJ, System.Double EJGCGPDDFNB) [0x0002b] in <b600322ea27a4b56b7e84cd63d093a92>:0 at LBOKCEJMKEH.FINOEJDLGOO (HDACBIMOOAJ JONBOGMOEOM, System.Int32 PHEIFCEIGBH) [0x00039] in <b600322ea27a4b56b7e84cd63d093a92>:0 at HDACBIMOOAJ.CNGFAPKBEFF (System.IntPtr FAMBEIDCDAM) [0x0000e] in <b600322ea27a4b56b7e84cd63d093a92>:0
google ai "believes" it has to do with folders/layers being incorrectly parented/siblinged into a recursive loop.
tried all backups--none fix the maps in question.
checked the map images themselves. They're fine.
turned off all extensions. Issue persists regardless.
In the db.xml: In the layers section of one of the maps in question, I removed all folders code, as well as changed all parentid tags to a simple <parent />, and removed all sibling tags, and that at least lets the map run, but only the one bitmap not in a folder survived (or rather, is visible to the host). Tokens exist on map, and the ray tracing line of sight wall mechanics still function when a token is selected, even though the layer with said wall mechanics tied to it doesn't render in the layers section.
tried re-parenting them to a new folder, but wasn't able to--might be too exhausted to brain-make-work.
I assume v5.1.6 restructured layering, and-or fixed whatever weas making the layer system wonky the past month (when these maps were made). The wonkiness causing some layers to incorrectly attribute who their parent/sibling is, causing the loop only now, after 5.1.6 fixed the issue allowing the corruption.
maps were working last week at session time Sunday, and on Monday.
I'll try fixing the sibling/parent structure in the db.xml tomorrow myself, but I'd love any advice, or uh... reassurance of a patch-patch or... Etc.
Thank you for taking the time.