Closed GoogleCodeExporter closed 9 years ago
DDMS screenshot of puzzle gate added for clarity.
Original comment by aitu...@gmail.com
on 1 Apr 2010 at 12:14
Attachments:
Actually the spikes are not only missing, they are at the wrong location. When
you're
near the end of that level, where there are many monsters, "flying" spikes sit
there,
and are not deadly. So it seems the spikes "tiles" are misplaced, but not their
effect.
Original comment by Ced.le.pingouin@gmail.com
on 2 Apr 2010 at 9:20
Tested and verified as fixed in version 1.2 / 10.
Original comment by aitu...@gmail.com
on 4 Apr 2010 at 4:43
I fixed the spike placement in 1.2 but there might still be floating objects
later in the level. I'll leave this bug
open to fix that.
Original comment by sm0a...@gmail.com
on 5 Apr 2010 at 3:14
Spikes above are there, which makes it impossible to get orb to blue robot,
cannot make orb in the air and cannot get orb up to get to robot. This level is
not possible...
Original comment by joypip...@gmail.com
on 12 Aug 2010 at 5:19
I think this level is impossible ... I can't make orb in air so I can't open
the door
Original comment by veteran...@gmail.com
on 21 Sep 2010 at 9:05
Fixed in 1.2.
PS: Tilt your phone up to make the orb fly.
Original comment by sm0a...@gmail.com
on 3 Jan 2011 at 2:19
The device I'm on doesn't support tilting, which makes this level REALLY
IMPOSSIBLE for me. I have actually flown through the spikes before, but have
not been able to repeat my actions. The developers should fix it so you can get
past this area of Memory #34 a different way OR a easier way to move the energy
orb (or whatever it's called) for devices that don't support tilting. Though I
am able to move with the trackball, it seems to not move the orb. I hope this
comes to the developer's notice. ♪♥♣♠♦ (-;
Original comment by 123ae...@gmail.com
on 12 Aug 2012 at 1:39
I tried tilting my phone up I doesn't go up every other tilt works but not to
send the possession orb up
Original comment by pikat...@gmail.com
on 15 Jun 2014 at 7:02
Original issue reported on code.google.com by
aitu...@gmail.com
on 1 Apr 2010 at 2:19