[Bug?] First Forest Clue
Guys, you know, I grew up playing games without quest markers, fast travel and other things for new generation of casuals, and I've completed many of those legendary titles with their unforgettable, atmospheric directions like "go over there, where the two trees grow, turn north from there, and follow the path until you see three hills shaped like a sunrise under a falling sakura petal". But this First Forest Clue quest, which honestly seems ridiculously simple, has been torturing me for two days now. I’ve explored not only all the surroundings of Skara Brae but most of the entire continent. And yeah, I'm sure the solution is painfully straightforward, but here I am, stuck for a second day. I could use some help, as silly as it sounds!
Comments
Never be afraid to challenge the status quo
So, okay, I finished the quest, and the solution was exactly where I thought it was all along, but it looks like there was probably a bug involved. Yeah, right from the start when I got this quest, I followed the path, I saw the Suspicious Trash Pile, I ran around it, tried to interact, but nothing happened. Eventually, I thought it wasn't the key and went on to explore the rest of the continent (literally), although I had a feeling something was wrong here. I returned to the Suspicious Trash Pile several times, circling around it, running to the labyrinth – nothing. It was only after I posted here asking for help that I decided to start from scratch and go through everything again. Finally, the quest moved forward, BUT! It triggered when I moved a considerable distance down from the Suspicious Trash Pile. Meanwhile, the second quest marker worked correctly in the same browser instance of the game.
The reason I think it's a bug is because over the past two days, I restarted the game multiple times (including due to disconnects), in both the web version and desktop version of ClassicUO and Enhanced Client, and the result was the same – the first Suspicious Trash Pile wouldn't trigger the quest. So it seems the problem is solved now, but it wouldn’t hurt for the developers to double-check this issue.