Bug: use the staff. right click. move mouse to other side of screen and press the space bar. the game freezes if you teleport to make the pool thingy go out of vision.
bug found that i am totally abusing: spam nets everywhere and possibly traps too as i did that as well somehow triggers a bug. wyrms get caught by nets and continue walking. place nets in their path to get infinite wyrms. so far i have about 200 wyrms. plz don't fix XD
what's the point of making us wait till we have the boat to fish if fishing gives us useless rubbish. rockfish is not good and takes too long to get even if it was. give us sushi in the kitchen so it can be awesome instead of useless plz.
Everyone is saying it's impossible to kill two dragons in a row. It's definitely possible. I killed the first dragon with my edge. Then I got lucky and hit the second one 2-3 times before he hit me once and then I hit again. I think I got some crits as well. Right after I ran into a wolf that hit me twice in a row and killed me. :(
you should have a more in depth tutorial, you did good on what you covered but you didnt cover everything, also option to skip it. you should make the memory larger on kong, i have to refresh every three mins. you should have the daily spin give useful rewards, like a min value of 500 gold per level, example level 14 will get something worth at least 7000, these 1000 rewards are useless to me, might make the scaling exponential because 25000 to a lvl 50 is probably nothing. you should make it a little bit harder to progress early on. you should make more games like this. you should reply to this post. my in game is WhatWasItAgain? in case you want to know.
Thank you for the feedback. The tutorial is quite long, but we'll discuss with the team. The "out of memory" error is an Unity WebGL error not unique to Shop Heroes. We recommend playing on Unity WebPlayer to avoid this error.
 "War Lands"){kind=icon}
 "Aground"){kind=icon}
 "Trigger Knight"){kind=icon}
 "The King's League: Odyssey"){kind=icon}
 "Shop Heroes"){kind=icon}
I'm sorry to say that this has finally been found and fixed - you will no longer be able to do this in 1.0.7 :P .