Rising Event

[LyraKuroneko]

I were mainly thinking of the game translation in general. here i think it's most the event itself that is a problem.

[worldofneil]

I hope this isn't the future of all instances. Like in 5.0 to stop another Raubahn Savage... MSQ instance only available for 1 hour every 12 hours :S

[Lexi]

Welp I made an alt on each Data Center for Japanese servers and they are all standing around the same spot we are waiting for the NPC and he didn't spawn. It's really sad seeing this many people on so many servers standing in the same spot waiting for something that we don't know when is going to happen..

[Rowde]

logged in out of curiosity, 11am CST, and no NPC available.

it popped at 11pm CST on Primal last night... so the 3 hours open, 9 hours down thing might not be accurate

[Claviusnex]

The Japanese text also had nothing in it to insinuate that the spawn times of the NPC were going to be random. The “exercises occur irregularly” seemed to be referring to the nature of the FATE spawns within the instance.

And, from what I have read, the JP playerbase also stood waiting around wondering when the NPC would spawn—even wondering if they had to do something special to spawn him.



And if there is no pattern?

Regardless, this was a poorly implemented event. More so because the developers could not even be bothered to inform its playerbase that it would set up timeslots for each region to participate, and instead they just let them stand around and wait while saying only “it’s working as intended”. It is absolutely rude to not inform your playerbase that an anticipated event such as The Rising will have a random/limited spawn factor to its content. This was never done before for any other past event.



Okay, so we have:
—9pm to 12am PST, where the NA servers are located.
—9pm to 12am JST, where the JP servers are located.

Where are the EU servers (time zone-wise) and what was the exact spawn time for him yesterday? Was he up 9pm to 12am during the EU’s server time? Can anyone from EU answer this? I want to write down these times and see if he spawns again at the same time today/tomorrow.

If the windows are consistent, at least we will have the windows for the Recruiter (if they’re consistent—wouldn’t surprise me at this point for it to be entirely random, but I’m hoping that isn’t the case). But this is still incredibly awful design—the NA times are 11pm to 2am my time, 12am to 3am for my best friend, and fairly early hours for people who may be in EU but play on NA data centers. Same for anyone, really, in a different region from their home region’s data center.

I'm not sure that is true for all of NA. I was on and off around midnight EDT and did not see a recruiter on Adamantoise. I just got on now hoping that maybe it was a 12 hour interval and still nothing.

[Deithwen]

The Japanese text also had nothing in it to insinuate that the spawn times of the NPC were going to be random. The “exercises occur irregularly” seemed to be referring to the nature of the FATE spawns within the instance.

And, from what I have read, the JP playerbase also stood waiting around wondering when the NPC would spawn—even wondering if they had to do something special to spawn him.



And if there is no pattern?

Regardless, this was a poorly implemented event. More so because the developers could not even be bothered to inform its playerbase that it would set up timeslots for each region to participate, and instead they just let them stand around and wait while saying only “it’s working as intended”. It is absolutely rude to not inform your playerbase that an anticipated event such as The Rising will have a random/limited spawn factor to its content. This was never done before for any other past event.



Okay, so we have:
—9pm to 12am PST, where the NA servers are located.
—9pm to 12am JST, where the JP servers are located.

Where are the EU servers (time zone-wise) and what was the exact spawn time for him yesterday? Was he up 9pm to 12am during the EU’s server time? Can anyone from EU answer this? I want to write down these times and see if he spawns again at the same time today/tomorrow.

If the windows are consistent, at least we will have the windows for the Recruiter (if they’re consistent—wouldn’t surprise me at this point for it to be entirely random, but I’m hoping that isn’t the case). But this is still incredibly awful design—the NA times are 11pm to 2am my time, 12am to 3am for my best friend, and fairly early hours for people who may be in EU but play on NA data centers. Same for anyone, really, in a different region from their home region’s data center.

I managed to get inside the instance at around midnight Paris time, so 10 pm (GMT), from the phoenix server. I am not really sure when the npc spawned precisely, but it's likely it has spawned at 9pm GMT.

[InkstainedGwyn]

Nothing on Exodus. I'm tempted to make an alt on a Japanese Data Center to see if it's up there.

It was up between 9 and 12 PST last night on Exodus, give or take a bit of time bc I didn't stand around. I want to do this with my friends so I'm going to wait until we can all be together, and if I miss the event it's SE's fault.

[Lexi]

It was up between 9 and 12 PST last night on Exodus, give or take a bit of time bc I didn't stand around. I want to do this with my friends so I'm going to wait until we can all be together, and if I miss the event it's SE's fault.

Thanks! I'll try again later tonight. =)

[VaatiTheMage]

Cecily Jisi from Balmung here. Been sitting around since around 8amEDT this morning. It's now noon and still no sign of them in any city state. This is not how I wanted to spend my day off.

[Iscah]

So it stayed active with the npc available the whole 3 hours?

Every time I checked (fairly often), yes. I don't know if there was a cutoff point where some people might be asked to wait because the instance was full, but I went in and out a few times on different characters.

There isn't a start and end of the instance, in practical terms - it's a cycle of five FATEs, after which the NPC "in charge of the commemorative exercises" will declare it's finished, but will start again soon. You don't need to leave the instance after that, just wait, and then the scenario starts again. You might enter the instance at any point in the cycle.