Results 1 to 3 of 3
  1. #1
    Player
    redmage's Avatar
    Join Date
    Mar 2011
    Location
    Gridania
    Posts
    393
    Character
    Topheru Jopheru
    World
    Excalibur
    Main Class
    White Mage Lv 70

    Kobold Daily Quest : Know Your Place

    Today on Ragnarok server, while attempting to complete the Beastman daily, Know Your Place, several people including myself have been unable to properly complete since each attempt at placing a Smoldering Coal results in a "The Enemy is still about!" message.

    This happens even when no enemy is able to be popped. I am guessing this is to prevent multiple people trying to pop too many mobs at once, but this still does not seem right when only a few of us are standing around and unable to pop any mob.
    (0)

  2. #2
    Player
    Lilymoon's Avatar
    Join Date
    Jun 2011
    Posts
    109
    Character
    Lily Arlune
    World
    Sargatanas
    Main Class
    Conjurer Lv 50
    Might wanna try killing off any nearby velociraptors. I got this bug yesterday and it seemed to work right whenever they moved away from the nodes. Was going to test that theory out today but didn't get the same quest again
    (0)

  3. #3
    Player
    Mazerat's Avatar
    Join Date
    Jan 2014
    Posts
    32
    Character
    Dianora Dawnshadow
    World
    Leviathan
    Main Class
    Arcanist Lv 60
    Quote Originally Posted by redmage View Post
    Today on Ragnarok server, while attempting to complete the Beastman daily, Know Your Place, several people including myself have been unable to properly complete since each attempt at placing a Smoldering Coal results in a "The Enemy is still about!" message.

    This happens even when no enemy is able to be popped. I am guessing this is to prevent multiple people trying to pop too many mobs at once, but this still does not seem right when only a few of us are standing around and unable to pop any mob.
    I and another had this issue the other day. I was able to use the other two nodes successfully and was then able to use the first one. Not sure if that's a fix or coincidence but hope it helps if you run into this issue again.
    (0)