Results 1 to 4 of 4
  1. #1
    Player Suteru's Avatar
    Join Date
    May 2011
    Location
    San d'Oria
    Posts
    118
    Character
    Suteru
    World
    Asura
    Main Class
    COR Lv 99

    LegionB does not count as "Legion" zone for RoE quests (or gear)

    Platform:
    PC

    ISP:
    Verizon FiOS

    Type of Internet Connection:
    Fiber

    Internet Connection Speed:
    Gigabit

    Date & Time: 8/10/2019 around 10AM EDT

    Frequency:
    State how frequently the issue occurs. Please select from the following.
    Always

    Character Name:
    Suteru

    Race:
    Hume M

    World:
    Asura

    Main Job:
    Corsair

    Support Job:
    Dancer

    Area and Coordinates:
    Maquette Abdhaljs-LegionB (maybe A, too)

    Party or Solo:
    Party

    NPC Name:
    None

    Monster Name:
    None

    Steps:
    1. Set RoE for Ambuscade Primer Vol 1
    2. Defeat the frog in Vol 1
    3. Have it count towards the RoE (it shouldn't be doing this)
    (0)
    Last edited by Suteru; 08-11-2019 at 05:58 PM.

  2. #2
    Player VoiceMemo's Avatar
    Join Date
    Mar 2011
    Posts
    793
    Character
    Voicememo
    World
    Asura
    Main Class
    BRD Lv 99
    This is not an error if you read the ROE it specifically states for this month "vanquish the requisite number of Porogo in NON-LEGION areas."
    (0)

  3. #3
    Player Suteru's Avatar
    Join Date
    May 2011
    Location
    San d'Oria
    Posts
    118
    Character
    Suteru
    World
    Asura
    Main Class
    COR Lv 99
    That's what I'm saying, if you kill it in LegionB, it IS counting towards the RoE, when it shouldn't.
    (0)

  4. #4
    Player Sirmarki's Avatar
    Join Date
    Dec 2013
    Posts
    1,572
    Character
    Sirmarki
    World
    Asura
    Main Class
    WHM Lv 99
    Quote Originally Posted by Suteru View Post
    That's what I'm saying, if you kill it in LegionB, it IS counting towards the RoE, when it shouldn't.
    I think with a lot of other stuff still in need of addressing, I think this is a pretty minor "bug".
    (0)