Regarding Skipped Cutscenes

[Camate]

Greetings,

Below is a comment from Yoji Fujito regarding cutscenes that are being skipped.



We've been receiving GM calls and bug reports for a while now regarding cutscenes being skipped automatically, but this is something that was very intricate and it took us an extremely long time to analyze. Today we've finally identified the cause and we will be implementing a fix in the upcoming version update.

The cutscenes that were being skipped were those that were part of battlefields where level restrictions were imposed. The level wasn't the issue; it was the level restriction status.

To give you a breakdown of the cause, last fall we enhanced the entry requirements and cutscene loading check, but the actual level restriction status was not included in the checks. Due to this, the entry requirements were being check properly; however, the level restriction status applied after entering the battlefield was getting stuck on the cutscene loading check, and as a result the system was incorrectly determining that the cutscene has already been watched.

By trading an item to the Goblin Footprint in the area of the battlefield where cutscene was skipped, you can watch them again. (The item will not be taken from you.)

Though there may be a loss of immersion, please check out the cutscenes that you were unable to see.

This was an extremely simple cause once we realized it, but we weren't able to identify it for a while. I deeply apologize to everyone who was really looking forward to watching the story.

[Ziyyigo-Tipyigo]

Thank you.

[Ziyyigo-Tipyigo]

Actually, will this just be the long-standing bug that eats opening cutscenes, or will this also fix the new bug that eats closing cutscenes that popped up last fall?

[Kraggy]

Greetings,

Below is a comment from Yoji Fujito regarding cutscenes that are being skipped.
This might be the first time in the history of FFXI that a developer actually EXPLAINED how an apparently W-T-F bug came about. It's great, thanks to Yoji_Fujito for posting it, it makes a hugely repfreshing change from SE's usual total silence or at least best opaquely vague and information-free comments.

Let's hope for more transparency in future.

[Aoisa]

Not being able to watch myself in the cutscene after killing the shadowlord was very distressing; I had to settle for watching a YouTube video because after the skipped cutscene, because not even the Goblin Footprint would let me watch it again.

Will this part of the glitch be fixed as well?

[Ziyyigo-Tipyigo]

because not even the Goblin Footprint would let me watch it again.

The Goblin Footprint doesn't work for a particular mission until you officially complete the mission, and for rank missions that involves going back to your home nation for the wrap-up and, in this case, officially getting rank 6.

If you go back to the Throne Room now you'll find that it works.

[Llama]

Nice catch! It's always the simplest thing that turns out to be such elusive logic errors.

[SilentSteel]

Yay, I was wondering why I was missing story as I was flowing through CoP and RoZ, Glad this fix was found before I do ToAU and WotG

[SNK]

Greetings,

Below is a comment from Yoji Fujito regarding cutscenes that are being skipped.

I know it doesn't seem like a huge request but I would love to hear the devs explain how bugs get thru. If anything it gives off more of a willingness to communicate with folks and let them know that "Working addressing the issues" even after the bug is fixed.

[FaeQueenCory]

This was an extremely simple cause once we realized it, but we weren't able to identify it for a while.
LMAO!
Why is it always something so mindnumbingly simple that messes up everything with computers? XD
A mistag, a "1" instead of a "0", an exclusion of a data check, a typo for a "inconsequential" variable... etc.
It's so easy to ruin programming.... kinda like DNA.
So I get it, these things just kinda happen... no biggie ^^

Though I have to point out, that some CSs don't have gobbie replays.
Like the "in battle" CS for the final Bastok WotG mission-quest. (if it does, I can't find where.)
That skipped for me, and since it uses the mentioned "level cap" shenanigans, I'm assuming that I missed the CS for the same reason.

[Aoisa]

The Goblin Footprint doesn't work for a particular mission until you officially complete the mission, and for rank missions that involves going back to your home nation for the wrap-up and, in this case, officially getting rank 6.

If you go back to the Throne Room now you'll find that it works.

Actually, I'd already tried that after it didn't work the first time. There was still no response from the footprint in any of Baileys, Keep or Throne Room. Time will tell, I suppose.

[Edyth]

On the topic of cutscenes, could you make it so the Dragon Quest X and FFXIV crossover cutscenes can be viewed at Bard NPCs? It's a shame we can never see the slime scenes again, and that we only get to see one variation (Bastok, Windurst, or San d'Oria) of the cutscene per character. I know that Bard NPCs refer to permanent tags on your character, such as completed quests or key items. The permanent tag for these cutscenes could be the unlocking of the Slime and Spriggan species in monstrosity: if you have those, you could view the cutscenes. {{Can I have it?}}

[Stan64]

All the times I contacted a GM about this and got told there was nothing wrong with the game or it's working as intended. Made me really angry about the game and the level of service against players having legitimate issues with the game. This isn't a relief. I have watched every single cutscene in the game by now. And had zone and backtrack to several footprints and got told this was the intended way to experience the cutscene when I clearly knew it was wrong because the FIVE OTHER people in the group got to see it and know they have to wait for me, the only one who cares about the lore in the group. What a pain I was to them.

Just ranting. I love the game and you usually do a good job yadda yadda. This was not one of them.

[Ziyyigo-Tipyigo]

we will be implementing a fix in the upcoming version update

I didn't see any mention of this in today's update notes.