create alias bravely_second -> bravely_second:_end_layer

Link to alias

Full title, in line with bravely default: flying fairy

remove implication bravely_second -> bravely_default:_flying_fairy
create implication bravely_default:_flying_fairy -> bravely_default_(series)
create implication bravely_second:_end_layer -> bravely_default_(series)

Link to request

Rather than implicating the first game with the second, I think it would make more sense to create a series tag. There are a few related mobile/browser games that could apply to and it helps future-proof the series, seeing as Bravely Third is highly likely.

I was wondering myself why that wasn't already the case.

bravely_(series)? Or bravely_default_(series)? Or is there an better or official name for the series as a whole?

Bravely Default: Praying Brage, for example, does keep both, even though it's set long after Default and Second.

On the other hand, there is Bravely Archive and Bravely Second.

Square, why must your titling practices forever vex us so…

I don't think there's an official name for the series yet. For now bravely_default_(series) is the least ambiguous. They might name it Luxendarc after the setting, sort of how the Ivalice Alliance is a subset of Final Fantasy.

I added Praying Brage as an implication to the request.

The tag alias bravely_second -> bravely_second:_end_layer has conflicting wiki pages. bravely_second:_end_layer should be updated to include information from bravely_second if necessary.

The tag alias bravely_second -> bravely_second:_end_layer has been approved.

Bulk update request #727 failed: Implication for bravely_second not found

The bulk update request #727 has been approved.

Note: The initial alias migrated the implication bravely_second -> bravely_default:_flying_fairy to bravely_second:_end_layer -> bravely_default:_flying_fairy, which is what threw up the error.

Thanks. Wasn't sure whether the implications needed to be handled manually or not; good to know.