Continuity Error - Rytlock's Eyes pre-HoT story

There seems to be a continuity Error.Rytlock's eyes are NOT support to be blue for Personal Story, Season 2, Story Dungeon, because this is before he became revanant. Yet his eye color is blue.Also during HoT and Season 3 when he is revanant we dont see his eyes because he wears the blind fold the entire time. The only time we should be able to see his blue eyes is during PoF expansion story.

This is Rytlock right now in Story Dungeon pre-HoT event:

And this is what Rytlock's eyes SHOULD BE during Story Dungeons pre-HoT event:

Please correct these changes because it is immersion breaking.

Already been fixed:

By "wrong" do you mean compared to what you saw in the PoF demo?

I didn't say anything about PoF demo...If you play personal story, and story dungeon, his eyes were once brownish yellow. Now it's blue. His eyes are only blue in PoF, not pre-Revenant era.

@DreamyAbaddon.3265 said:I didn't say anything about PoF demo...If you play personal story, and story dungeon, his eyes were once brownish yellow. Now it's blue. His eyes are only blue in PoF, not pre-Revenant era.

Maybe that's intentional? You know, he's seen The Mists.

@Alatar.7364 said:

@DreamyAbaddon.3265 said:I didn't say anything about PoF demo...If you play personal story, and story dungeon, his eyes were once brownish yellow. Now it's blue. His eyes are only blue in PoF, not pre-Revenant era.

He has not seen the mist yet...

Or does he?

Rytlock Brimstone does not have Blue eyes and has not been to the Mist during Personal Story, Story Dungeon, or Season 1. During the 2nd Season there is a mission where Rytlock jumps down to the mist to get his sword and we never see him again until HoT. When we see him in HoT he has a blind fold the whole time. Same with Season 3. When we see Rytlock again in PoF demo, that is when our player character notices his eyes again and this time it is blue.

Currently Rytlock's eyes are blue even in story missions before he went to the mist which is a Continuity Error. This must be addressed.

So what you're saying is that they retroactively changed his old model eyes to blue, which matches his new model eyes.

And you're assuming that they are meant to be different colors because he went to the Mists and wore a blindfold

Notice that they also retroactively changed Sohothin's model. This is not a bug but an intentional retroactive change in model to match new visions (pun intended). They did this before, a prime example being the Losaru centaurs in gw1. Originally they looked like the Maguuma and Shiverpeak centaurs, but when Nightfall was released they changed their model to match the Elonian centaurs.

No changes needed. You just need to stop assuming his eyes should be different just because he went into the Mists and became a revenant.

he's been touched by the white walker....

@Konig Des Todes.2086 said:So what you're saying is that they retroactively changed his old model eyes to blue, which matches his new model eyes.

And you're assuming that they are meant to be different colors because he went to the Mists and wore a blindfold

Notice that they also retroactively changed Sohothin's model. This is not a bug but an intentional retroactive change in model to match new visions (pun intended). They did this before, a prime example being the Losaru centaurs in gw1. Originally they looked like the Maguuma and Shiverpeak centaurs, but when Nightfall was released they changed their model to match the Elonian centaurs.

No changes needed. You just need to stop assuming his eyes should be different just because he went into the Mists and became a revenant.

If that's the case they need to update ALL cutscenes with Rytlock's eyes because the cinematic scenes his eyes are not blue. It breaks immersion.

Maybe he discovered a time machine, and contacts, and went back and gave his former self said contact lenses. Anything is possible in the Mists!
:astonished:

@DreamyAbaddon.3265 said:

@Konig Des Todes.2086 said:So what you're saying is that they retroactively changed his old model eyes to blue, which matches his new model eyes.

And you're assuming that they are meant to be different colors because he went to the Mists and wore a blindfold

Notice that they also retroactively changed Sohothin's model. This is not a bug but an intentional retroactive change in model to match new visions (pun intended). They did this before, a prime example being the Losaru centaurs in gw1. Originally they looked like the Maguuma and Shiverpeak centaurs, but when Nightfall was released they changed their model to match the Elonian centaurs.

No changes needed. You just need to stop assuming his eyes should be different just because he went into the Mists and became a revenant.

I always find it funny when someone picks a small detail and claims it breaks immersion. How's this for circumventing the breaking of immersion:In the world of Guild Wars 2, total makeover kits exist. Rytlock uses them periodically to change his eye color.

Problem solved.

Rytlock also used a pistol when he was classified as a warrior. My warrior can't use pistols. Breaks my immersion?

Mass panic!

@Wolfheart.7483 said:I always find it funny when someone picks a small detail and claims it breaks immersion. How's this for circumventing the breaking of immersion:In the world of Guild Wars 2, total makeover kits exist. Rytlock uses them periodically to change his eye color.

Problem solved.

They still sell it as a story heavy game. Stuff like character appearance and continuity should not be a small detail.

@TheRandomGuy.7246 said:

@Wolfheart.7483 said:I always find it funny when someone picks a small detail and claims it breaks immersion. How's this for circumventing the breaking of immersion:In the world of Guild Wars 2, total makeover kits exist. Rytlock uses them periodically to change his eye color.

Problem solved.

Appearance and continuity, generally speaking, should be accurate, I agree. This thread is specifically about eye color. That's a tiny detail in the overall scope of appearance and continuity. My makeover kit example may seem a bit silly, but technically it is a perfectly viable explanation within the context of the world so someone with such a fragile level of immersion doesn't break it.

Wait, here is another:We have head armor skins that just give different colored glowing eyes. Maybe Rytlock has his own unique skin he equipped to change his eye color.

There is an issue that needs to be solved. Ignoring it or coming up with excuses is not a solution to bugs like this.

They seem to be amber in the launch trailer. Can't really tell from this if that's immersion-breaking, or not. :confused:

@DreamyAbaddon.3265 said:

@Konig Des Todes.2086 said:So what you're saying is that they retroactively changed his old model eyes to blue, which matches his new model eyes.

And you're assuming that they are meant to be different colors because he went to the Mists and wore a blindfold

Notice that they also retroactively changed Sohothin's model. This is not a bug but an intentional retroactive change in model to match new visions (pun intended). They did this before, a prime example being the Losaru centaurs in gw1. Originally they looked like the Maguuma and Shiverpeak centaurs, but when Nightfall was released they changed their model to match the Elonian centaurs.

No changes needed. You just need to stop assuming his eyes should be different just because he went into the Mists and became a revenant.

Eye color is such a small thing it simply isn't worth redoing all the pre-rendered cinematics. Maybe Sohothin's update would make it worthwhile but it is rarely a focus.

It'd actually be easier for them to update the eyes of the model rather than redo the cinematic. However, it isn't close to major enough to really be immersion breaking. As such it isn't some thing that needs fixing. Nothing even close to critical.

Want to complain, complain about all the PS models that change completely between cinematics and not. I could list four easily.

@DreamyAbaddon.3265 said:There is an issue that needs to be solved. Ignoring it or coming up with excuses is not a solution to bugs like this.

That isn't what a bug is.