57139 réponses à ce sujet

[blooregard]

SS2Dante wrote...

Fingertrip wrote...

Marzillius wrote...

The trees are there because they were there in an earlier stage in development of the area. Then Bioware changed the area before Shepard gets hit by the beam, and forgot/didn't bother to go back and change the area after Shepard gets hit by the beam too.

No IT, just an ordinary developer error.

This, most likely this.

This was the same day they forgot to change the cubemap for the crucible. And the day QA were out drinking, missing the ghost keeper. And the same day the sound team forgot about theming and used the whispers from the dream in the TIM scene. And the day they forgot that in every other scene he's Anderson, not Admiral Anderson. And the same day etc etc etc

I'm sorry, but can you not see how unlikely it is all of this happened by accident? Considering the rest of the game stays internally consistant? 

Cube map can be seen as a dev error its easy to miss, ignorable, and you actually have to look for the reflections to see the trees .Same goes for the ghost Keeper you can shoot through it simply because they wanted to put a Keeper on screen but out of the way of your path. This however is far too noticable to have been forgotten and something this obvious wouldn't have been ignored when/if they changed the scene.

Modifié par blooregard, 06 mai 2012 - 09:13 .

[SubAstris]

SS2Dante wrote...

Fingertrip wrote...

Marzillius wrote...

The trees are there because they were there in an earlier stage in development of the area. Then Bioware changed the area before Shepard gets hit by the beam, and forgot/didn't bother to go back and change the area after Shepard gets hit by the beam too.

No IT, just an ordinary developer error.

This, most likely this.

This was the same day they forgot to change the cubemap for the crucible. And the day QA were out drinking, missing the ghost keeper. And the same day the sound team forgot about theming and used the whispers from the dream in the TIM scene. And the day they forgot that in every other scene he's Anderson, not Admiral Anderson. And the same day etc etc etc

I'm sorry, but can you not see how unlikely it is all of this happened by accident? Considering the rest of the game stays internally consistant? 

But most of those things you bring out are less than inconsequential. And I think you give BW too much credit when it comes to other elements of the game. If you analysed other scenes in as much detail as you did this one, you would of course find mistakes that you would leave you thinking, "how did they forget that?"

[Fingertrip]

I'm really down with IT, but some stuff are so bloody subtle that your average gamer won't even spot it. That seems like a pretty faulty way to hint at at a bigger scheme to the overall plot. The subtle-in game hints are perfectly valid, but when it comes to digging through files and really "grasp" at straws, which can be seen somewhat of an "error" is abit stretching it abit.

There's alot of other stuff that I think are far more intriguing and can be seen more of a good example of proof for IT to be valid. The trees is abit of a 50/50 if you ask me.

[Sero303]

SubAstris wrote...

SS2Dante wrote...

Fingertrip wrote...

Marzillius wrote...

The trees are there because they were there in an earlier stage in development of the area. Then Bioware changed the area before Shepard gets hit by the beam, and forgot/didn't bother to go back and change the area after Shepard gets hit by the beam too.

No IT, just an ordinary developer error.

This, most likely this.

This was the same day they forgot to change the cubemap for the crucible. And the day QA were out drinking, missing the ghost keeper. And the same day the sound team forgot about theming and used the whispers from the dream in the TIM scene. And the day they forgot that in every other scene he's Anderson, not Admiral Anderson. And the same day etc etc etc

I'm sorry, but can you not see how unlikely it is all of this happened by accident? Considering the rest of the game stays internally consistant? 

But most of those things you bring out are less than inconsequential. And I think you give BW too much credit when it comes to other elements of the game. If you analysed other scenes in as much detail as you did this one, you would of course find mistakes that you would leave you thinking, "how did they forget that?"

Where as I agree with you in one respect about giving them too much credit, one would think they would pay extra special attention to the final act. The final act (aka: everything that led to this moment, the defining moment of the story etc etc etc). When telling a story you don't simply 'forget' or or fail to fix the mistakes ( many many many mistakes) like that.

So I think it is a little from column A, and little from column B,...and column C(aka: synthesis)

All this speculation is of course moot, we can debate every little thing, what this might mean, or what that is supposed to be,  but it's doesn't really matter ( much like the decisions you made in the game ) because it is all in the hands of a higher power now. ( and when I say "higher" I don't mean elevation )

[blooregard]

Fingertrip wrote...

I'm really down with IT, but some stuff are so bloody subtle that your average gamer won't even spot it. That seems like a pretty faulty way to hint at at a bigger scheme to the overall plot. The subtle-in game hints are perfectly valid, but when it comes to digging through files and really "grasp" at straws, which can be seen somewhat of an "error" is abit stretching it abit.

There's alot of other stuff that I think are far more intriguing and can be seen more of a good example of proof for IT to be valid. The trees is abit of a 50/50 if you ask me.

Unlike the ghost keeper or the cube map the post laser trees are very noticable same as the shrubs on the way to the beam and the piles of bodies after being hit by harby those are a little more noticable then the reflections you can make out if you go to a special spot on the map and look at it at the right angle

[paxxton]

Another hint at something IT-related.
When ordering Shepard to the Mars Archives, Hackett states that they've been searching them with Liara and found something. But when Shepard arrives in the facility, Liara is surprised that Hackett ordered him to go there.

It's suspicious that Hackett survives the initial attack and does not report back to Earth, just to pop up on the comm screen after Shepard leaves Earth.

Modifié par paxxton, 06 mai 2012 - 09:28 .

[SS2Dante]

SubAstris wrote...

SS2Dante wrote...

Fingertrip wrote...

Marzillius wrote...

The trees are there because they were there in an earlier stage in development of the area. Then Bioware changed the area before Shepard gets hit by the beam, and forgot/didn't bother to go back and change the area after Shepard gets hit by the beam too.

No IT, just an ordinary developer error.

This, most likely this.

This was the same day they forgot to change the cubemap for the crucible. And the day QA were out drinking, missing the ghost keeper. And the same day the sound team forgot about theming and used the whispers from the dream in the TIM scene. And the day they forgot that in every other scene he's Anderson, not Admiral Anderson. And the same day etc etc etc

I'm sorry, but can you not see how unlikely it is all of this happened by accident? Considering the rest of the game stays internally consistant? 

But most of those things you bring out are less than inconsequential. And I think you give BW too much credit when it comes to other elements of the game. If you analysed other scenes in as much detail as you did this one, you would of course find mistakes that you would leave you thinking, "how did they forget that?"

Back down to the central divide again. I disagree that these are inconsequential issues. Small, perhaps, but not inconsequential. To give an example, the Admiral Anderson thing. What are the odds Bioware actually has to type the name of the speaker for the subs every time? Almost certainly nill. It would be automated. This means that someone added a new "character" into the system, at a completely arbitrary point. And people don't seem to realise the srcutiny this stuff is under. There's not a whole bunch of spelling mistakes or grammer errors, and this is because it is combed through very carefully to check all this. How many testers played through the London mission to check the subs were working correctly, I wonder. Making sure it was all as per script. And noone noticed?

As I said, it's simply too much.

But as ever this is not really a level we can reason each other out of I suppose. Judgement call and all that.

Modifié par SS2Dante, 06 mai 2012 - 09:28 .

[SS2Dante]

paxxton wrote...

Another hint at something IT-related.
When ordering Shepard to the Mars Archives, Hackett states that they've been searching them with Liara and found something. But when Shepard arrives in the facility, Liara is surprised that Hackett ordered him to go there.

It's suspicious that Hackett survives the initial attack and does not report back to Earth, just to pop up on the comm screen after Shepard leaves Earth.

Shepard is supposed to be grounded on earth, awaiting court marshal. Isn't that the cause of surprise?

I don't understand your second point? He's the leader, having him on Earth would be madness.

[Rifneno]

Marzillius wrote...

The trees are there because they were there in an earlier stage in development of the area. Then Bioware changed the area before Shepard gets hit by the beam, and forgot/didn't bother to go back and change the area after Shepard gets hit by the beam too.

No IT, just an ordinary developer error.

"Ignorance begets confidence more often than does knowledge." - Charles Darwin

[paxxton]

SS2Dante wrote...

paxxton wrote...

Another hint at something IT-related.
When ordering Shepard to the Mars Archives, Hackett states that they've been searching them with Liara and found something. But when Shepard arrives in the facility, Liara is surprised that Hackett ordered him to go there.

It's suspicious that Hackett survives the initial attack and does not report back to Earth, just to pop up on the comm screen after Shepard leaves Earth.

Shepard is supposed to be grounded on earth, awaiting court marshal. Isn't that the cause of surprise?

I don't understand your second point? He's the leader, having him on Earth would be madness.

By reporting back I meant sending info.

And Liara asks "Why'd he order you here?". So she's surprised about the order rather than about seeing Shepard.

Modifié par paxxton, 06 mai 2012 - 09:36 .

[SubAstris]

Sero303 wrote...

SubAstris wrote...

SS2Dante wrote...

Fingertrip wrote...

Marzillius wrote...

The trees are there because they were there in an earlier stage in development of the area. Then Bioware changed the area before Shepard gets hit by the beam, and forgot/didn't bother to go back and change the area after Shepard gets hit by the beam too.

No IT, just an ordinary developer error.

This, most likely this.

This was the same day they forgot to change the cubemap for the crucible. And the day QA were out drinking, missing the ghost keeper. And the same day the sound team forgot about theming and used the whispers from the dream in the TIM scene. And the day they forgot that in every other scene he's Anderson, not Admiral Anderson. And the same day etc etc etc

I'm sorry, but can you not see how unlikely it is all of this happened by accident? Considering the rest of the game stays internally consistant? 

But most of those things you bring out are less than inconsequential. And I think you give BW too much credit when it comes to other elements of the game. If you analysed other scenes in as much detail as you did this one, you would of course find mistakes that you would leave you thinking, "how did they forget that?"

Where as I agree with you in one respect about giving them too much credit, one would think they would pay extra special attention to the final act. The final act (aka: everything that led to this moment, the defining moment of the story etc etc etc). When telling a story you don't simply 'forget' or or fail to fix the mistakes ( many many many mistakes) like that.

So I think it is a little from column A, and little from column B,...and column C(aka: synthesis)

All this speculation is of course moot, we can debate every little thing, what this might mean, or what that is supposed to be,  but it's doesn't really matter ( much like the decisions you made in the game ) because it is all in the hands of a higher power now. ( and when I say "higher" I don't mean elevation )

There were many mistakes, but you have to realise that BW wanted more time anyway and endings are notoriously one of the hardest bits of the narrative to write anyway

[MaximizedAction]

paxxton wrote...

Another hint at something IT-related.
When ordering Shepard to the Mars Archives, Hackett states that they've been searching them with Liara and found something. But when Shepard arrives in the facility, Liara is surprised that Hackett ordered him to go there.

It's suspicious that Hackett survives the initial attack and does not report back to Earth, just to pop up on the comm screen after Shepard leaves Earth.

I don't exactly recall the dialoges, but it might've been that Liara just wasn't informed about Shep's arrival. After all, the facility had been sabotaged. Hence, her surprise about Shepard, because the report would've probably contained that he was released from detention.

But Hackett does have this way of popping up randomly. But he said during the first comm on the Normandy that he had to sacrifice the 6th fleet, which is logged in the Codex. And if the Codex contains only legit info, then here Hackett might be legit, too.

Modifié par MaximizedAction, 06 mai 2012 - 09:35 .

[SubAstris]

SS2Dante wrote...

SubAstris wrote...

SS2Dante wrote...

Fingertrip wrote...

Marzillius wrote...

The trees are there because they were there in an earlier stage in development of the area. Then Bioware changed the area before Shepard gets hit by the beam, and forgot/didn't bother to go back and change the area after Shepard gets hit by the beam too.

No IT, just an ordinary developer error.

This, most likely this.

This was the same day they forgot to change the cubemap for the crucible. And the day QA were out drinking, missing the ghost keeper. And the same day the sound team forgot about theming and used the whispers from the dream in the TIM scene. And the day they forgot that in every other scene he's Anderson, not Admiral Anderson. And the same day etc etc etc

I'm sorry, but can you not see how unlikely it is all of this happened by accident? Considering the rest of the game stays internally consistant? 

But most of those things you bring out are less than inconsequential. And I think you give BW too much credit when it comes to other elements of the game. If you analysed other scenes in as much detail as you did this one, you would of course find mistakes that you would leave you thinking, "how did they forget that?"

Back down to the central divide again. I disagree that these are inconsequential issues. Small, perhaps, but not inconsequential. To give an example, the Admiral Anderson thing. What are the odds Bioware actually has to type the name of the speaker for the subs every time? Almost certainly nill. It would be automated. This means that someone added a new "character" into the system, at a completely arbitrary point. And people don't seem to realise the srcutiny this stuff is under. There's not a whole bunch of spelling mistakes or grammer errors, and this is because it is combed through very carefully to check all this. How many testers played through the London mission to check the subs were working correctly, I wonder. Making sure it was all as per script. And noone noticed?

As I said, it's simply too much.

But as ever this is not really a level we can reason each other out of I suppose. Judgement call and all that.

But it is not completely arbitrary, saying Admiral Anderson instead of merely Anderson fits better with the tone BW were trying to create at the ending

Admittedly, spelling and grammatically are much easier to change than a lot of stuff

You're assuming the Admiral Anderson bit is a mistake

[Arian Dynas]

bigstig wrote...

Rifneno wrote...

....Everything else is unimportant. It can be cloned or made with tissue from poor saps that Miranda tricked into a date and then murdered (anyone else got an explanation for her shadow broker dossier?).

I don't get the murdered part, did I miss a dossier?  I always assumed she was looking for the perfect man with the perfect genes to go with her perfect genes to create the perfect offspring either that or she was lonely. I always found this the sadest part about Miranda, the doessier shows that she cannot have children as the cloning process that made her has left her infertile.(Which does happen with current cloned animals)

I always just saw it as Miranda not wanting to become an old maid, with her standards being extremely high.

bigstig wrote...

Arian Dynas wrote...

bigstig wrote...
*Some stuff that was an enourmously unecessarily big pain in the ass to format so I just cut it out.*

Thank you so much for explaining the joke, captain buzzkill. 

Anytime,  seriously though the concept of advanced technology appearing like magic is certainly worth considering on the whole space magic thing.

Yes, but the fact is, Mass Effect doesn't do that, they take the time to explain their tech, this isn't Stargate after all. TIM says it himself, THERE IS NO MAGIC, because all "magic" gets explained in this setting. 

SS2Dante wrote...

Comguard2 wrote...

If they carefully planted ideas for the indoc-theory why do they need the voice-actors for a second run?

I can understand that, in case this was planned all along, they needed extra time to develop 1, 2 additional levels.

But if they already had the idea, why didn't they record the voice acting when they had the opportunity to?

This makes no sense at all...but after the photoshopped-Tali picture my answer to such inconsistencies in the game is not "hidden genius" but "laziness hardly imaginable by normal people".

Your argument does raise a valid point, though I suppose one could counter by pointing out that if IT was planned then it was/is supposed to be top secret until revealed. Could simply be a need-to-know situation, and the VO's didn't need to know.

One of the most striking things to me is the cubemap for the crucible, featuring the trees. May I ask how you explain that? It doesn't seem to me that it can be eplained by laziness.

Let's look at one of the other greatest twists of all time. Darth Vader. The actor portraying Vader, David Prowse was not even told until the movie came out in theathers, Hammil was only told 5 minutes beforehand. The voice actor, James Earl Jones wasn't told until he started recording the lines personally.

Morever, they SAID they didn't plan on making the EC, hence my own theory that this whole thing was a big alternate reality game, crossed with PR stunt, only people werent satisfied to wait for the conclusion DLC that would reveal indoctrination, so they had to pull the EC out of their ass.

pirate1802 wrote...

Dwailing wrote...

Why would you want to shoot Mordin?  You must be some kind of heartless puppy kicker if you actually WANT to do it.  If you want to see it, just look it up on YouTube.  No reason to subject your soul to that kind of torture.  I swear, just watching it is enough to make my soul die a little. [smilie]http://social.bioware.com/images/forum/emoticons/crying.png[/smilie]

You know you are right. I reached that point and I just couldn't kill him :S And no I didn't want to do it, just wanted to see it first hand. And no I'm not a puppy kicker, I've got 6 puppies in my home [smilie]http://social.bioware.com/images/forum/emoticons/unsure.png[/smilie]

Is it possible to just.. not shoot? I see shooting him is a Renegade interrupt, what happens if you don't take it?

[DJBare]

paxxton wrote...

SS2Dante wrote...

paxxton wrote...

Another hint at something IT-related.
When ordering Shepard to the Mars Archives, Hackett states that they've been searching them with Liara and found something. But when Shepard arrives in the facility, Liara is surprised that Hackett ordered him to go there.

It's suspicious that Hackett survives the initial attack and does not report back to Earth, just to pop up on the comm screen after Shepard leaves Earth.

Shepard is supposed to be grounded on earth, awaiting court marshal. Isn't that the cause of surprise?

I don't understand your second point? He's the leader, having him on Earth would be madness.

By reporting back I meant sending info.

And Liara asks "Why'd he order you here?". So she's rather surprised about the order than about seeing Shepard.

That's interesting, I'd assumed Liara was briefed by Hackett.

I started a topic regarding Hackett, it might be a good idea to pay more attention to him, especially since he is the one overseeing the construction of the crucible which I believe is of reaper design, like I said in my topic, we are forced into giving the crucible a reaper heart, this is not a war asset the player can avoid.

[SS2Dante]

SubAstris wrote...

SS2Dante wrote...

SubAstris wrote...

SS2Dante wrote...

Fingertrip wrote...

Marzillius wrote...

The trees are there because they were there in an earlier stage in development of the area. Then Bioware changed the area before Shepard gets hit by the beam, and forgot/didn't bother to go back and change the area after Shepard gets hit by the beam too.

No IT, just an ordinary developer error.

This, most likely this.

This was the same day they forgot to change the cubemap for the crucible. And the day QA were out drinking, missing the ghost keeper. And the same day the sound team forgot about theming and used the whispers from the dream in the TIM scene. And the day they forgot that in every other scene he's Anderson, not Admiral Anderson. And the same day etc etc etc

I'm sorry, but can you not see how unlikely it is all of this happened by accident? Considering the rest of the game stays internally consistant? 

But most of those things you bring out are less than inconsequential. And I think you give BW too much credit when it comes to other elements of the game. If you analysed other scenes in as much detail as you did this one, you would of course find mistakes that you would leave you thinking, "how did they forget that?"

Back down to the central divide again. I disagree that these are inconsequential issues. Small, perhaps, but not inconsequential. To give an example, the Admiral Anderson thing. What are the odds Bioware actually has to type the name of the speaker for the subs every time? Almost certainly nill. It would be automated. This means that someone added a new "character" into the system, at a completely arbitrary point. And people don't seem to realise the srcutiny this stuff is under. There's not a whole bunch of spelling mistakes or grammer errors, and this is because it is combed through very carefully to check all this. How many testers played through the London mission to check the subs were working correctly, I wonder. Making sure it was all as per script. And noone noticed?

As I said, it's simply too much.

But as ever this is not really a level we can reason each other out of I suppose. Judgement call and all that.

But it is not completely arbitrary, saying Admiral Anderson instead of merely Anderson fits better with the tone BW were trying to create at the ending

Admittedly, spelling and grammatically are much easier to change than a lot of stuff

You're assuming the Admiral Anderson bit is a mistake

If they'd changed it for tone he would have been Admiral Anderson during the whole London mission. But he's not. It changes right after being hit by Harbingers laser.

 

[SubAstris]

SS2Dante wrote...

SubAstris wrote...

SS2Dante wrote...

SubAstris wrote...

SS2Dante wrote...

Fingertrip wrote...

Marzillius wrote...

The trees are there because they were there in an earlier stage in development of the area. Then Bioware changed the area before Shepard gets hit by the beam, and forgot/didn't bother to go back and change the area after Shepard gets hit by the beam too.

No IT, just an ordinary developer error.

This, most likely this.

This was the same day they forgot to change the cubemap for the crucible. And the day QA were out drinking, missing the ghost keeper. And the same day the sound team forgot about theming and used the whispers from the dream in the TIM scene. And the day they forgot that in every other scene he's Anderson, not Admiral Anderson. And the same day etc etc etc

I'm sorry, but can you not see how unlikely it is all of this happened by accident? Considering the rest of the game stays internally consistant? 

But most of those things you bring out are less than inconsequential. And I think you give BW too much credit when it comes to other elements of the game. If you analysed other scenes in as much detail as you did this one, you would of course find mistakes that you would leave you thinking, "how did they forget that?"

Back down to the central divide again. I disagree that these are inconsequential issues. Small, perhaps, but not inconsequential. To give an example, the Admiral Anderson thing. What are the odds Bioware actually has to type the name of the speaker for the subs every time? Almost certainly nill. It would be automated. This means that someone added a new "character" into the system, at a completely arbitrary point. And people don't seem to realise the srcutiny this stuff is under. There's not a whole bunch of spelling mistakes or grammer errors, and this is because it is combed through very carefully to check all this. How many testers played through the London mission to check the subs were working correctly, I wonder. Making sure it was all as per script. And noone noticed?

As I said, it's simply too much.

But as ever this is not really a level we can reason each other out of I suppose. Judgement call and all that.

But it is not completely arbitrary, saying Admiral Anderson instead of merely Anderson fits better with the tone BW were trying to create at the ending

Admittedly, spelling and grammatically are much easier to change than a lot of stuff

You're assuming the Admiral Anderson bit is a mistake

If they'd changed it for tone he would have been Admiral Anderson during the whole London mission. But he's not. It changes right after being hit by Harbingers laser.

 

Sorry, how does this support IT?

[paxxton]

SS2Dante wrote...

SubAstris wrote...

SS2Dante wrote...

SubAstris wrote...

SS2Dante wrote...

Fingertrip wrote...

Marzillius wrote...

The trees are there because they were there in an earlier stage in development of the area. Then Bioware changed the area before Shepard gets hit by the beam, and forgot/didn't bother to go back and change the area after Shepard gets hit by the beam too.

No IT, just an ordinary developer error.

This, most likely this.

This was the same day they forgot to change the cubemap for the crucible. And the day QA were out drinking, missing the ghost keeper. And the same day the sound team forgot about theming and used the whispers from the dream in the TIM scene. And the day they forgot that in every other scene he's Anderson, not Admiral Anderson. And the same day etc etc etc

I'm sorry, but can you not see how unlikely it is all of this happened by accident? Considering the rest of the game stays internally consistant? 

But most of those things you bring out are less than inconsequential. And I think you give BW too much credit when it comes to other elements of the game. If you analysed other scenes in as much detail as you did this one, you would of course find mistakes that you would leave you thinking, "how did they forget that?"

Back down to the central divide again. I disagree that these are inconsequential issues. Small, perhaps, but not inconsequential. To give an example, the Admiral Anderson thing. What are the odds Bioware actually has to type the name of the speaker for the subs every time? Almost certainly nill. It would be automated. This means that someone added a new "character" into the system, at a completely arbitrary point. And people don't seem to realise the srcutiny this stuff is under. There's not a whole bunch of spelling mistakes or grammer errors, and this is because it is combed through very carefully to check all this. How many testers played through the London mission to check the subs were working correctly, I wonder. Making sure it was all as per script. And noone noticed?

As I said, it's simply too much.

But as ever this is not really a level we can reason each other out of I suppose. Judgement call and all that.

But it is not completely arbitrary, saying Admiral Anderson instead of merely Anderson fits better with the tone BW were trying to create at the ending

Admittedly, spelling and grammatically are much easier to change than a lot of stuff

You're assuming the Admiral Anderson bit is a mistake

If they'd changed it for tone he would have been Admiral Anderson during the whole London mission. But he's not. It changes right after being hit by Harbingers laser.

 

I'm sorry, but the subtitles refer to Anderson differently throughout the whole game.
For example, by the Thanix missles he is referred to as Admiral Anderson. Then for a brief time as Anderson. And after the hit as Admiral Anderson again.

Modifié par paxxton, 06 mai 2012 - 09:48 .

[SS2Dante]

SubAstris wrote...

SS2Dante wrote...

SubAstris wrote...

SS2Dante wrote...

SubAstris wrote...

SS2Dante wrote...

Fingertrip wrote...

Marzillius wrote...

The trees are there because they were there in an earlier stage in development of the area. Then Bioware changed the area before Shepard gets hit by the beam, and forgot/didn't bother to go back and change the area after Shepard gets hit by the beam too.

No IT, just an ordinary developer error.

This, most likely this.

This was the same day they forgot to change the cubemap for the crucible. And the day QA were out drinking, missing the ghost keeper. And the same day the sound team forgot about theming and used the whispers from the dream in the TIM scene. And the day they forgot that in every other scene he's Anderson, not Admiral Anderson. And the same day etc etc etc

I'm sorry, but can you not see how unlikely it is all of this happened by accident? Considering the rest of the game stays internally consistant? 

But most of those things you bring out are less than inconsequential. And I think you give BW too much credit when it comes to other elements of the game. If you analysed other scenes in as much detail as you did this one, you would of course find mistakes that you would leave you thinking, "how did they forget that?"

Back down to the central divide again. I disagree that these are inconsequential issues. Small, perhaps, but not inconsequential. To give an example, the Admiral Anderson thing. What are the odds Bioware actually has to type the name of the speaker for the subs every time? Almost certainly nill. It would be automated. This means that someone added a new "character" into the system, at a completely arbitrary point. And people don't seem to realise the srcutiny this stuff is under. There's not a whole bunch of spelling mistakes or grammer errors, and this is because it is combed through very carefully to check all this. How many testers played through the London mission to check the subs were working correctly, I wonder. Making sure it was all as per script. And noone noticed?

As I said, it's simply too much.

But as ever this is not really a level we can reason each other out of I suppose. Judgement call and all that.

But it is not completely arbitrary, saying Admiral Anderson instead of merely Anderson fits better with the tone BW were trying to create at the ending

Admittedly, spelling and grammatically are much easier to change than a lot of stuff

You're assuming the Admiral Anderson bit is a mistake

If they'd changed it for tone he would have been Admiral Anderson during the whole London mission. But he's not. It changes right after being hit by Harbingers laser.

 

Sorry, how does this support IT?

Disregard, see above.

Modifié par SS2Dante, 06 mai 2012 - 09:47 .

[blooregard]

DJBare wrote...

paxxton wrote...

SS2Dante wrote...

paxxton wrote...

Another hint at something IT-related.
When ordering Shepard to the Mars Archives, Hackett states that they've been searching them with Liara and found something. But when Shepard arrives in the facility, Liara is surprised that Hackett ordered him to go there.

It's suspicious that Hackett survives the initial attack and does not report back to Earth, just to pop up on the comm screen after Shepard leaves Earth.

Shepard is supposed to be grounded on earth, awaiting court marshal. Isn't that the cause of surprise?

I don't understand your second point? He's the leader, having him on Earth would be madness.

By reporting back I meant sending info.

And Liara asks "Why'd he order you here?". So she's rather surprised about the order than about seeing Shepard.

That's interesting, I'd assumed Liara was briefed by Hackett.

I started a topic regarding Hackett, it might be a good idea to pay more attention to him, especially since he is the one overseeing the construction of the crucible which I believe is of reaper design, like I said in my topic, we are forced into giving the crucible a reaper heart, this is not a war asset the player can avoid.

If you're saying that Hackett is indoctrinated perhaps you should rethink that as I don't believe there is a single instance of him being anywhere near a Reaper artifact until priority: Earth

[blooregard]

SS2Dante wrote...

SubAstris wrote...

SS2Dante wrote...

SubAstris wrote...

SS2Dante wrote...

SubAstris wrote...

SS2Dante wrote...

Fingertrip wrote...

Marzillius wrote...

The trees are there because they were there in an earlier stage in development of the area. Then Bioware changed the area before Shepard gets hit by the beam, and forgot/didn't bother to go back and change the area after Shepard gets hit by the beam too.

No IT, just an ordinary developer error.

This, most likely this.

This was the same day they forgot to change the cubemap for the crucible. And the day QA were out drinking, missing the ghost keeper. And the same day the sound team forgot about theming and used the whispers from the dream in the TIM scene. And the day they forgot that in every other scene he's Anderson, not Admiral Anderson. And the same day etc etc etc

I'm sorry, but can you not see how unlikely it is all of this happened by accident? Considering the rest of the game stays internally consistant? 

But most of those things you bring out are less than inconsequential. And I think you give BW too much credit when it comes to other elements of the game. If you analysed other scenes in as much detail as you did this one, you would of course find mistakes that you would leave you thinking, "how did they forget that?"

Back down to the central divide again. I disagree that these are inconsequential issues. Small, perhaps, but not inconsequential. To give an example, the Admiral Anderson thing. What are the odds Bioware actually has to type the name of the speaker for the subs every time? Almost certainly nill. It would be automated. This means that someone added a new "character" into the system, at a completely arbitrary point. And people don't seem to realise the srcutiny this stuff is under. There's not a whole bunch of spelling mistakes or grammer errors, and this is because it is combed through very carefully to check all this. How many testers played through the London mission to check the subs were working correctly, I wonder. Making sure it was all as per script. And noone noticed?

As I said, it's simply too much.

But as ever this is not really a level we can reason each other out of I suppose. Judgement call and all that.

But it is not completely arbitrary, saying Admiral Anderson instead of merely Anderson fits better with the tone BW were trying to create at the ending

Admittedly, spelling and grammatically are much easier to change than a lot of stuff

You're assuming the Admiral Anderson bit is a mistake

If they'd changed it for tone he would have been Admiral Anderson during the whole London mission. But he's not. It changes right after being hit by Harbingers laser.

*snip* 

Sorry, how does this support IT?

Disregard, see above.

You may have to explain your evidence a little...better.

[paxxton]

blooregard wrote...

DJBare wrote...

paxxton wrote...

SS2Dante wrote...

paxxton wrote...

Another hint at something IT-related.
When ordering Shepard to the Mars Archives, Hackett states that they've been searching them with Liara and found something. But when Shepard arrives in the facility, Liara is surprised that Hackett ordered him to go there.

It's suspicious that Hackett survives the initial attack and does not report back to Earth, just to pop up on the comm screen after Shepard leaves Earth.

Shepard is supposed to be grounded on earth, awaiting court marshal. Isn't that the cause of surprise?

I don't understand your second point? He's the leader, having him on Earth would be madness.

By reporting back I meant sending info.

And Liara asks "Why'd he order you here?". So she's rather surprised about the order than about seeing Shepard.

That's interesting, I'd assumed Liara was briefed by Hackett.

I started a topic regarding Hackett, it might be a good idea to pay more attention to him, especially since he is the one overseeing the construction of the crucible which I believe is of reaper design, like I said in my topic, we are forced into giving the crucible a reaper heart, this is not a war asset the player can avoid.

If you're saying that Hackett is indoctrinated perhaps you should rethink that as I don't believe there is a single instance of him being anywhere near a Reaper artifact until priority: Earth

So fighting the Reaper armada doesn't count as being near Reaper tech???? Indoctrination works by utilizing waves so he doesn't have to be in a very close proximity to get indoctrinated.

Modifié par paxxton, 06 mai 2012 - 09:53 .

[SS2Dante]

blooregard wrote...

SS2Dante wrote...

SubAstris wrote...

SS2Dante wrote...

SubAstris wrote...

SS2Dante wrote...

SubAstris wrote...

SS2Dante wrote...

Fingertrip wrote...

Marzillius wrote...

The trees are there because they were there in an earlier stage in development of the area. Then Bioware changed the area before Shepard gets hit by the beam, and forgot/didn't bother to go back and change the area after Shepard gets hit by the beam too.

No IT, just an ordinary developer error.

This, most likely this.

This was the same day they forgot to change the cubemap for the crucible. And the day QA were out drinking, missing the ghost keeper. And the same day the sound team forgot about theming and used the whispers from the dream in the TIM scene. And the day they forgot that in every other scene he's Anderson, not Admiral Anderson. And the same day etc etc etc

I'm sorry, but can you not see how unlikely it is all of this happened by accident? Considering the rest of the game stays internally consistant? 

But most of those things you bring out are less than inconsequential. And I think you give BW too much credit when it comes to other elements of the game. If you analysed other scenes in as much detail as you did this one, you would of course find mistakes that you would leave you thinking, "how did they forget that?"

Back down to the central divide again. I disagree that these are inconsequential issues. Small, perhaps, but not inconsequential. To give an example, the Admiral Anderson thing. What are the odds Bioware actually has to type the name of the speaker for the subs every time? Almost certainly nill. It would be automated. This means that someone added a new "character" into the system, at a completely arbitrary point. And people don't seem to realise the srcutiny this stuff is under. There's not a whole bunch of spelling mistakes or grammer errors, and this is because it is combed through very carefully to check all this. How many testers played through the London mission to check the subs were working correctly, I wonder. Making sure it was all as per script. And noone noticed?

As I said, it's simply too much.

But as ever this is not really a level we can reason each other out of I suppose. Judgement call and all that.

But it is not completely arbitrary, saying Admiral Anderson instead of merely Anderson fits better with the tone BW were trying to create at the ending

Admittedly, spelling and grammatically are much easier to change than a lot of stuff

You're assuming the Admiral Anderson bit is a mistake

If they'd changed it for tone he would have been Admiral Anderson during the whole London mission. But he's not. It changes right after being hit by Harbingers laser.

*snip* 

Sorry, how does this support IT?

Disregard, see above.

You may have to explain your evidence a little...better.

No, I meant paxxton proved it wrong. Sorry, didn't realise I'd been ambiguous but reading it again clearly it was

[Cyberfrog81]

Arian Dynas wrote...

Let's look at one of the other greatest twists of all time. Darth Vader. The actor portraying Vader, David Prowse was not even told until the movie came out in theathers, Hammil was only told 5 minutes beforehand. The voice actor, James Earl Jones wasn't told until he started recording the lines personally.

Morever, they SAID they didn't plan on making the EC, hence my own theory that this whole thing was a big alternate reality game, crossed with PR stunt, only people werent satisfied to wait for the conclusion DLC that would reveal indoctrination,

"We'll have something totally awesome for you soon, keep your faith in us a little longer, you will be rewarded!"

Except... that's not the message that was sent; certainly not the message people got. No, the non-sensical ending that seems to belong in a different game entirely, is what they intended, it was their vision. PR ('artistic integrity') was ****** poorly handled. I don't see how anyone, supporter of IT or not, can say otherwise.


Extended for clarity: I'm on board with the indoctrination attempt scenario. But I don't believe in blaming the audience for not "getting" something that wasn't properly communicated; or for not graciously accepting a product that didn't deliver as promised.

Modifié par Cyberfrog81, 06 mai 2012 - 10:22 .

[MegumiAzusa]

blooregard wrote...

DJBare wrote...

paxxton wrote...

SS2Dante wrote...

paxxton wrote...

Another hint at something IT-related.
When ordering Shepard to the Mars Archives, Hackett states that they've been searching them with Liara and found something. But when Shepard arrives in the facility, Liara is surprised that Hackett ordered him to go there.

It's suspicious that Hackett survives the initial attack and does not report back to Earth, just to pop up on the comm screen after Shepard leaves Earth.

Shepard is supposed to be grounded on earth, awaiting court marshal. Isn't that the cause of surprise?

I don't understand your second point? He's the leader, having him on Earth would be madness.

By reporting back I meant sending info.

And Liara asks "Why'd he order you here?". So she's rather surprised about the order than about seeing Shepard.

That's interesting, I'd assumed Liara was briefed by Hackett.

I started a topic regarding Hackett, it might be a good idea to pay more attention to him, especially since he is the one overseeing the construction of the crucible which I believe is of reaper design, like I said in my topic, we are forced into giving the crucible a reaper heart, this is not a war asset the player can avoid.

If you're saying that Hackett is indoctrinated perhaps you should rethink that as I don't believe there is a single instance of him being anywhere near a Reaper artifact until priority: Earth

So? It was pretty quick with different characters too.