Deprecated function: Array and string offset access syntax with curly braces is deprecated in include_once() (line 20 of /home/gravitym/public_html/includes/file.phar.inc).
Remember that GM sometimes makes compound objects destroyable even if you don't want them to be when you open a level from code. Change them back to non-destroyable if that happens. Tanx ------------------ k(78,63)t(122,245)t(253,362.95)t(47.2,398.35)t(96,427.1)t(149.55,412.75)t(198.3,383.1)b(100,100,220,20,5,1,0,0,0.2)b(205,106,10,24,5,1,0,0,0.2)b(225,200,160,20,-5,1,0,0,0.2)b(18,170,20,100,0,1,0,0,0.2)b(75,210,40,20,0,1,0,0,0.2)b(300,190,20,100,70,1,0,0,0.2)b(346,135,20,100,0,1,0,0,0.2)b(345,145,20,100,10,1,0,0,0.2)b(340,160,20,100,30,1,0,0,0.2)b(332,170,20,100,45,1,0,0,0.2)b(320,180,20,100,59.27,2,0,0,0.2)b(80,86,60,4,5,5,0.1,0,0.2)b(84.65,40,60,4,5,5,0.1,0,0.2)b(52,61,48,4,95,3,0.1,0,0.2)c(29,64,20,0,0.2,0,0.2)b(120,209,49,20,-3,4,0,0.5,0.2)b(180,149,110,10,-5,1,0.1,0.5,0.2)c(145,185,3,1,0.1,0.5,0.2)b(198,155,6,12,-5,1,0.1,0.5,0.2)b(233,145,6,12,-5,2,0.1,0.5,0.2)c(145,185,12,0,0.1,0.5,0.2)c(182,174,20,4,0,0.5,0.2)b(98.25,275.15,6,57.65,-10.45,5,-1,-1,0)b(142.55,275.2,6,57.65,7.25,5,-1,-1,0)c(120.2,302.95,16,3,-1,-1,0)c(106.75,301.75,6,1,22,0.5,0.2)c(96.75,380.8,5.88,1,1,0.5,0.2)c(40.8,422,5.88,2,1,0.5,0.2)b(226.6,263.5,14.25,135.95,0,0,0,0.5,0.2)b(214.85,735.05,14.25,666,0,0,0,0.5,0.2)b(247.15,1078.85,14.25,666,0,0,0,0.5,0.2)b(247.7,567.85,14.25,333,0,0,0,0.5,0.2)b(232,685.15,14.25,333,0,0,0,0.5,0.2)j(145,185,0,0,0,0)j(109.7,303.9,0,0,0,0)j(97.65,380.5,1,666,0,0)
Do compound objects resemble an array full of '1' except the last one, which is replaced by '2' as a sentinel? If true, that's kind of weird to me. Sometimes they're all '5' with the last one being '3', just after opening a level from code, and they're indeed compounded.
Exactly right. Sometimes I use my graphics program to generate the coordinates of objects for a level, and adding the 111111112 is part of the procedure for making the code for compound objects. 5/3 comes up as well when GM generates code, and I think it's related to an object being destroyable, but GM is quirky when it comes to destroyable things, so sometimes you never know what you're going to get when you open something from code. That's why we have to check compound objects before uploading a level to make sure they haven't been randomly changed by the GM gremlin lol.
Comments
Jeff -
Jeff -