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).
Sometimes it's necessary to modify the code outside of GM to get the values you want (using a word processor, or email window, or something like that), and then use that to "open from code".
These are the orbs in my latest level: t(401.6,498.35) t(140.75,382.4) t(222.35,418.4) t(297.55,452) t(658.2,382.35) t(576.2,417.55) t(503.8,452). Many decimals are in there. Forgive me if I'm misunderstanding you.
İt is strange. I'm putting random too much orb. All no deciman. k(200,200)t(347,236)t(353.95,233)t(450,191)t(476,177)t(517,157)t(540,153)t(550,170)t(558,185)t(569,216)t(604,248)t(614,279)t(528,344)t(505,344)t(466,322)t(493,272)t(543,247)t(617,192)t(611,112)t(484,74)t(371,78)t(329,104)t(329,123)t(410,142)t(436,161)t(423,190)t(278,238)t(213,259)t(175,317)t(190,366)t(285,393)t(411,416)t(517,442)t(615,434)t(672,399)t(693,351)t(673,281)t(621,319)t(581,345)t(506,362)t(333,321)t(312,308)t(401,350)t(420,367)t(395,405)t(333,382)t(331,367)t(354,341)t(419,301)t(424,288)t(334,257)t(329,258)t(221,261)t(218,283)t(273,335)t(330,361)t(396,385)t(456,514)t(302,544)t(310,536)t(292,484)t(291,469)t(228,449)t(221,446)t(248,419)t(390,472)t(435,473)t(459,445)t(459,422) just one
k(200,200)t(108,205)t(108,210)t(106,248)t(107,255)t(108,261)t(106,283)t(108,302)t(108,325)t(110,343)t(114,363)t(110,387)t(109,406)t(112,421)t(114,445)t(118,476)t(101,488)t(73,493)t(57,495)t(49,483)t(40,469)t(32,450)t(32,431)t(220,247)t(220,247)t(220,266)t(220,302)t(217,319)t(216,350)t(216,360)t(220,385)t(221,425)t(219.05,437)t(223,466)t(237,489)t(253,490)t(278,493)t(299,496)t(329,499)t(346,502)t(356,498)t(370,493)t(367,493)t(326,503)t(310,508)t(227,369)t(237,370)t(259,368)t(291,373)t(314,374)t(351,375)t(381,375)t(330,370)t(308,366)t(271,364.05)t(223,243)t(242,247)t(270,247)t(292,249)t(321,251)t(352,255)t(362.95,254)t(339,248)t(254,221)t(251.95,242.05)t(310,247)t(321,248)t(352,248)t(433,238)t(431,246.95)t(430,275)t(430,280)t(439,306)t(449,330)t(449,352)t(452,374)t(453,391)t(450,434)t(451,442)t(452,453)t(455,499)t(455,499)t(439,428)t(447,407)t(452,384)t(433,240)t(467,244)t(469,244)t(501,242)t(522,250)t(542,252)t(552,252)t(563,252)t(563,252)t(528,259)t(506,253)t(474,248)t(461,247.95)t(464,371)t(478,371)t(505,373)t(514,372)t(535,372)t(554,372)t(562,371.05)t(581,374)t(620,244)t(615,258)t(615,281)t(618,293)t(626,315)t(631,335)t(639,345)t(642,389)t(643,398)t(648,424)t(648,438)t(650,454)t(651,464)t(651,490)t(651,508)t(651,511)t(642.05,429)t(633.05,393)t(632,375)t(630,361)t(606,248)t(630,246)t(641.95,241.05)t(656,237)t(693,237)t(700,237)t(744,239)t(747,238)t(766,235)t(717,238)t(715,238)t(651,361)t(661,389)t(669,389)t(678,382.05)t(678,382.05)t(693,375)t(710,375)t(715,375)t(739,378)t(745,378)t(748,378)t(761,381)
Created 30 sec
That's very strange, Engin! Your GM is doing something that mine is not doing. I did this in just a few seconds and then saved it and re-opened it, to give GM every chance to take the decimals away, but it didn't. k(200,200)t(82.4,504)t(92,428.75)t(93.55,386.35)t(100.8,324)t(100.8,206.35)t(92.8,96.8)t(176,84)t(324,92.8)t(436,109.55)t(557.55,118.4)t(636.75,136)t(701.55,193.6)t(752,293.6)t(772,436)t(736,534.4)t(629.55,574.4)t(472,564)t(372,544)t(242.35,480)t(152.8,400)t(188,340.75)t(240,273.6)t(248,220)t(360,176.8)t(465.6,204)t(549.55,229.6)t(634.4,276)t(680.75,372.75)t(668,476)t(524,498.35)t(432.75,448.75)t(312,336.75)t(276,245.6)t(400,260.75)t(485.6,320)t(578.4,376.75)t(665.6,460)t(530.4,456)t(365.6,332)t(284,369.6)t(220,464.75)t(102.4,528)t(156,548)t(264,532)t(333.6,452)t(380,384)t(510.35,168.8)t(398.35,133.6)t(336,117.55)t(292,97.55)t(584,48)t(701.55,72)
For an experiment, "open from code" the code in my comment above and then save it, and then open it again and "get code" to see if the decimals are still there. If you want to.
Comments
Jeff -
Engin Varol -
Engin Varol -
Jeff -
Engin Varol -
Jeff -
Engin Varol -
Engin Varol -
Jeff -
Jeff -
Engin Varol -
Jeff -
Engin Varol -
Jeff -
Mr Bob -