Vana'Bout Round 7 VBD Dailies Not Counting

[OMGItsABear]

Operating System:
Windows 11

ISP:
Xfinity

Type of Internet Connection:
Cable Internet

Internet Connection Speed:
Unsure, Xfinity internet

Date & Time:
11/18/2025 10:13 CST

Frequency:
All VBD dailies cannot be completed

Character Name:
Gihon

Race:
Hume M

World:
Bismarck

Main Job:
Various, tried Ambuscade Lightning damage on BLM and WAR

NPC Name:
None

Monster Name:
None

Steps:
Vana'Bout "Deal 500+ Lightning Damage (VBD)" dealt multiple instances of 500+ lightning damage, Raiden Thrust and Thunder Thrust on Warrior. Dealt Multiple casts of Thunder V on BLM for 800+ damage. Tried every element for over 500 damage except for Fire as it seems the frog is strong vs fire.

Also tried "Auctioning (VBD)" listed an Oxblood, did not count so I listed it again and it did not count.

All of my VBDs turned red after accepting them. I do not know what that means.

[Dragoy]

The dialog is for *removing* the objectives, to, I believe, indicate that they can be replaced by the next objectives on the next day (so that it won't linger around for a second day to be un-done).

Not entirely sure about that still though. Haven't been testing it at all yet, and did not watch the latest freshly pickled mogivana where they might have mentioned it.

I guess when coming up with this, they didn't take into consideration that players are prooobably quuuite used to *accepting* objectives like that... and will certainly mistake it for it. :\

Edit:

Did test the cancel feature, and indeed, it will even make the second day objective appear in its place, if there is one.

I suppose that is good to have, though accident-prone, but we're still missing a catch-up mechanic it seems.

Edit too:

OK there might be a bit of a catch-up mechanic to it, too.

Hmmm... but methinks only a bit of a.

[OMGItsABear]

Yes, I now see a couple of other posts. What a terribly unintuitive design. You need to accept all other RoE quests, but Vana'Bout it will be the opposite.

[Alhanelem]

All of my VBDs turned red after accepting them. I do not know what that means. You cancelled these objectives, not accepted them.

If this is your first vana'bout, you wouldn't know- the cancelling is a new feature, so you can get rid of objectives you can't complete. But All vana'bout objectives are always active, you don't have to accept them.



What a terribly unintuitive design.I wouldn't go that far. If you look at the list, the objectives are already green, just like RoEs you accept manually. That makes it reaosnably clear (IMO) that they're arleady active.

The other reason for this is the Vana'Bout objectives do not count towards the RoE objective limit. Thats why you don't have to set them.



I guess when coming up with this, they didn't take into consideration that players are prooobably quuuite used to *accepting* objectives like that... and will certainly mistake it for it. :\ Only if this is your first vana'bout. IF you've done any of the previous ones, you'd know that VB objectives are automatically active and you don't have to manually select them.

Also, if you take the moment to read the dialog box that comes up when you click on a VB objective it does say "Remove objective?" not "Set objective?"

Anyway... this isn't a bug, it's the intended behavior. It just wasn't made clear to people who don't regularly check the website for the update notes.

So really, I have to ask- How many of you were clicking on the Vana'Bout objectives in previous events even though they didn't need to be clicked on?