A major update, v.1.10, for GC Labyrinth is here!<\/p>\n
Here is the list of recent changes\/fixes:<\/p>\n
-“nearest to orb”: new gem target priority, and it’s the initial priority for all new gems
\n-space freezes\/starts time, Q switches 1x\/3x speed
\n-various typos fixed
\n-amulet descriptions clarified
\n-“build 1.000 shrines”: 1.000 -> 100
\n-“destroy 1.000 beacons with towers”: 1.000 -> 300
\n-Shadow Clash now gives the x1.24 xp multiplier as it says
\n-Fixed: gembombing tomb with time frozen multiple summon bonus glitch
\n-Fixed swarm 4x monster amount mana glitch: banishment cost >= 2 (minus banishment skill bonus), mana gain >= 1 now.
\n-Fixed tomb selection for gems: now gems always attack the tomb with the lowest armor
\n-Tombs are now painted dark red in the labyrinth map (nests are marked too)
\n-Fixed wizard level 500 issue, there is no level limit anymore
\n-Fixed: armor reduce bonus from amplifier was shown multiplied by 100 in the gem info panel
\n-Fixed: logging in (or purchasing Premium) while in the Battle settings panel didn’t activate the premium settings at once, only after going back and to the settings panel again
\n-Fixed the “Kill 1000 monsters in a row” journey amulet not being awarded
\n-Repeatedly achieved challenge amulets don’t show up in the victory panel anymore
\n-Reinforced GCL code against a Flash Player bug (randomly occuring “Error #2015: Invalid BitmapData”)
\n-the GCL vfx engine now constantly checks the performance (fps) and degrades rendering quality (or even removes vfx particles) if the game lags too much
\n-Possibly fixed severe lagging and freezing when the orb is destroyed with lots of monsters on scene
\n-“beat 100 waves” challenge amulets, if achieved from now on, will show the actual record (formerly they always showed “1”)
\n-Fixed: binding beacon’s “no mana” effect was wearing off even when the time was frozen
\n-Fixed: clicking on the speed\/pause buttons deselected the target monster(\/apparition\/shadow)
\n-To avoid accidental unlocking (and wasting mana), from now on you need to hold shift when unlocking gem types (and you can’t unlock with the numpad because of technical limitations – sorry)
\n-When combining gems, the new gem will have its target priority set the game as the gem you dragged the other gem to<\/p>\n