Bugged?[]
I left the map in the middle of the quest (after talking to No Spine), and upon returning couldn't find 'the beast' anywhere and thus finish the quest. By abandoning the quest completely, getting it from Command Post again and doing it in one run, I was able to finish it. Other people on GWGuru-forums seem to have troubles with it too but no surefire solutions. Any comments? 193.167.197.35 02:37, 1 November 2006 (CST)
- You're not the only one —
kyrasantae 20:35, 2 November 2006 (CST)
Also bugged[]
im also having the exact same issue, but i did not have the time to cancel the quest and reobtain it.
Exploit[]
Should we really be promoting exploits on the wiki? 67.87.113.101 02:15, 17 September 2007 (CDT)
- Yeah, but does depend on the nature of the exploit. Many articles have details of ways to bypass or solve things quickly, indeed, some might argue just by pre-reading how a quest for example will "play out" before you do it yourself could be consider as a spoiler or even cheating etc. However, I believe the general idea would be that if you're reading these articles, it's because you're looking for help solving the quest or at least wanting some guidelines. Also, just because a exploit of this nature is documented, doesn't mean you have to use it. :D If the exploit was of a more "game wreaking" nature (like how to use / create a gaming-bot), that would (personally speaking) be a different kettle of fish, and those should not have any place on GuildWiki. The "trick" detailed on this article about how to get out of paying the 5 platinum, would say is ok. --Wolfie
(talk|contribs) 05:37, 17 September 2007 (CDT)
- The thing with other guides though, is that it's not actually cheating nor an exploit to use them. This quite literally exploits an oversight in programming. I never saw anything on the wiki about the captured son exploit all that time ago, why have one listed here? Trust me, I'm all for not paying money when I don't need to-but then I'll just do the quest the way they plan on doing it, not cheating through it.67.87.113.101 15:00, 17 September 2007 (CDT)
- Just reporting back - it still works. --Birchwooda Treehug 00:09, 4 June 2009 (UTC)
