339 réponses à ce sujet

[Jonttu1]

Blacklash93 wrote...

But seriously, this is what happens when you liberally trade off and replace writers through the course of a series.

You get inconsistent characterization, lore errors, and retcons that bleed stupid.

I'm glad the Dragon Age series doesn't suffer from this. They have a consistent set of good writers who each are mostly responsible for certain characters and parts of the lore. That's the way you do it, Bioware. That's how you keep things consistent.

Oh give it a rest already, they said that it was a mistake and apologized for it. It happens. To err is Human, to forgive is divine.

[Blacklash93]

Jonttu1 wrote...

Blacklash93 wrote...

But seriously, this is what happens when you liberally trade off and replace writers through the course of a series.

You get inconsistent characterization, lore errors, and retcons that bleed stupid.

I'm glad the Dragon Age series doesn't suffer from this. They have a consistent set of good writers who each are mostly responsible for certain characters and parts of the lore. That's the way you do it, Bioware. That's how you keep things consistent.

Oh give it a rest already, they said that it was a mistake and apologized for it. It happens. To err is Human, to forgive is divine.

Excuse me for giving advice at how they could avoid all the writing issues that plague this series in the future.

[Kaiser Arian XVII]

Lotion Soronnar wrote...

LetMeW1n wrote...

Err, thought you were complaining about retconns and lore inconsistencies..? Yeah of course it's a bunch of bull**** in theoretical science today. But that's the way it is, was since ME1. Not saying the games had no retconns or anything, but you ain't bitc-hin about the right ones.

Omni-tool have always been bollocks.
And creating a large blade out of nothing in 0.01 seconds and ME fields acting like magic glue is a pretty big retcon.

As for the rest, I have no idea. But seriously, why so depressive? I see what you mean, but you're just ruining your own game and time obessesed with this kind of stuff. Doesn't really matter to me though, so I won't try to explain it or anything(thought of putting a nice retort but forgot what it is , so will just use <-- this instead. o_o) Good night, lolol

Runining my own game? I didn' make those errors - they were there to begin with. I just spotted them.
Ignorance in bliss.
Maybe I should do a lobotomy - then I will be able to enjoy everything!!!
To hell wiht standards! Lowest common denominators rule!

The rule of cool ... just accept it

[CROAT_56]

Omega-202 wrote...

CROAT_56 wrote...

So it was a mix up I'm gonna go with the Normandy was in orbit and it was just a coincidence that a cruiser got blown up in front of us

Believe what you'd like, as illogical as it is.  Kaidan and James must have been running at Mach 1 to get to their shuttle, launch the shuttle, take off faster than a rocket (something we've never seen a shuttle do in atmosphere), dock with the Normandy, transfer and arrive back in Vancouver all in the time frame necessary.  Forget the fact that there was no shuttle in the Normandy's hangar during the cutscene meaning they had to dock and transfer and not just unload inside the hangar.  

we only see the left side of the Normandy and yes they can get to that shuttle that landed on the roof at the bigining of the demo.  It wouldn't take that long to get there and as I said yesterday in the other thread the Kodiak is capable of traveling faster than todays shuttles.

[Lotion Soronarr]

Jedi Sentinel Arian wrote...
The rule of cool ... just accept it

NEVER! It is the cancer of deep, immersive stories!

[Iakus]

Yuoaman wrote...

iakus wrote...

LetMeW1n wrote...

Pretty sure I'll just pretend that dreadnought is in orbit, and VS had just retrieved the Normandy from a space station when s/he said it was being pummeled. Nothing to lose there.

EDIT: which is what ^CROAT_56 said too. lol.

To take it further, said dreadnought was damaged, sank into the atmosphere where it was subsequently destroyed by Reaper fire.

Problem solved.

The perfect retcon...

I think of it more as "head canon" since it's not an official reason, but my own way of justifying it.  I mean, it makes sense that a ship's engines might get damaged in a space battle and find itself caught in the planet's gravity well, right?

I've gotten pretty good at head-canon.  It kept me sane playing ME2...

[UndercoverDoctor]

Baryonic_Member wrote...

Anyone else bothered how unserious BioWare seem to be about consistency? 

Yeah, I was thinking about this not even 5 minutes ago.

It's getting pretty bad.

[Blacklash93]

Lotion Soronnar wrote...
Well, show me where in ME1 we see ME fields used like that for the omni-blade.
Also show me when we see an omni-tool wok so fast.

At least in Star Trek the replicators were big, required lots of power and didn't make things instantly.

and it's a sad, sad day when Star Trek makes more sense......

The fact that you didn't see them used like that in ME1 and 2 doesn't mean they weren't capable of it. There's a difference between an implausible development and a retcon.

[Praetor Knight]

Regarding Omni-tools' minifacturing fabricator, we have 3-D Printing today.

Open Source 3-D Printer Turns Designs Into Objects

First flight of 3D printed plane

Edit: and check out this particular 3-D Printer: ZPrinter 650

Edit2: one last video: Amazing 3D Printer

Modifié par Praetor Shepard, 14 février 2012 - 08:28 .

[Killjoy Cutter]

Lotion Soronnar wrote...

Jedi Sentinel Arian wrote...
The rule of cool ... just accept it

NEVER! It is the cancer of deep, immersive stories!

The rule of cool is one of the most pathetic excuses for lazy writing and production ever drooled onto a fanbase.

[pnakasone]

I don know if any one has said this but the codex says a dreadnought can not safely land on a planet. Nothing is said a bought not being able to enter the atmosphere and hover a few kilometers above the ground.

It may just be impractical and it risks attack from ground fire or someone blowing up a WMD under your ship. Or ships mass effect field engine deciding to have a problem at that time.

Dreadnought are very expensive to risk in atmosphere battle unless it is like what is happening on Earth. Then all bets are off.

[LetMeW1n]

Invisible post

[LetMeW1n]

@Lotion Right, then, sorry about that. Can't change how you see things and your attitude, lol. Apparently you survived quite a few years on BSN with unchanged viewpoints(seen a lot of your posts here b4, lol). But I'll just say that I never said to live in a fool's paradise or have some kind of idiot's contentment. I noticed these things and errors too, all the time. Just that most of the time, I let errors this small slip by and instead think about how some other people would have a real problem with it.. It's not pefect people in a perfectly profitable company designing this game, and in a creative industry, especially. Not even remotely trying to convince you, lol, just to speak. It's not bad to demand the best quality or anything, but do a video game in this industry and age..? Your tresholds for error are too low. A mediocre sequel to an brilliant, never-seen-before piece of sci-fi writing would have perfectly justified universal derision, but ME is hardly brilliant and new, and it's standard is, well, still probably way above all the other crap we see.

And you have to read the codex entry for omni-tools in ME1.(using phone here) Perfectly explains how omni-blades can exist, abeilt with simple explanations of mass effect fields(again) and graphene. Just that Shepard didn't have one of those in ME1.. It's cool now though.

[Ji99saw]

The ship did not land in the atmosphere it was taking off from the surface to go to space.

[Praetor Knight]

LetMeW1n wrote...

And you have to read the codex entry for omni-tools in ME1.(using phone here) Perfectly explains how omni-blades can exist, abeilt with simple explanations of mass effect fields(again) and graphene. Just that Shepard didn't have one of those in ME1.. It's cool now though.

It's mentioned to be silicon-carbide for the blade.


I posted it earlier: social.bioware.com/forum/1/topic/323/index/9230159/9#9262198
And direct links to codex stuff, posted here: social.bioware.com/forum/1/topic/323/index/9230159/9#9263936

Modifié par Praetor Shepard, 15 février 2012 - 12:16 .

[XFemShepX]

Sylvf wrote...

I hope you could answer this question though, so is the Normandy SR2 nearby in a docking bay or somewhere in atmo?

I actually don't know - that was Mac's level, and he'd have more details on what he pictured going down, and when.

I would've never guessed that was Mac's level.

....

[Lotion Soronarr]

Blacklash93 wrote...

Lotion Soronnar wrote...
Well, show me where in ME1 we see ME fields used like that for the omni-blade.
Also show me when we see an omni-tool wok so fast.

At least in Star Trek the replicators were big, required lots of power and didn't make things instantly.

and it's a sad, sad day when Star Trek makes more sense......

The fact that you didn't see them used like that in ME1 and 2 doesn't mean they weren't capable of it. There's a difference between an implausible development and a retcon.

I dont' recall that I specificly called it a retcon.
Doesn't really matter what you want to call it it.

It's bad.
No such ability has been seen before. It wasn't hinted.
And again, if ST looks more sensible in comparison, you got a problem!

[littlezack]

Lotion Soronnar wrote...

Blacklash93 wrote...

Lotion Soronnar wrote...
Well, show me where in ME1 we see ME fields used like that for the omni-blade.
Also show me when we see an omni-tool wok so fast.

At least in Star Trek the replicators were big, required lots of power and didn't make things instantly.

and it's a sad, sad day when Star Trek makes more sense......

The fact that you didn't see them used like that in ME1 and 2 doesn't mean they weren't capable of it. There's a difference between an implausible development and a retcon.

I dont' recall that I specificly called it a retcon.
Doesn't really matter what you want to call it it.

It's bad.
No such ability has been seen before. It wasn't hinted.
And again, if ST looks more sensible in comparison, you got a problem!

Just because something's not hinted doesn't mean it can't be brought in. It's not like ME1 was iron-clad and they absolutely can't add stuff to the codex at later dates.

[augustburnt]

 All the people freaking out at the OP are the reason Bioware has gone to ****, if you cant keep your story straight why would I trust you to make a game? Its called an RPG, look up the meaning and learn what its about.

[Lotion Soronarr]

LetMeW1n wrote...

@Lotion Right, then, sorry about that. Can't change how you see things and your attitude, lol. Apparently you survived quite a few years on BSN with unchanged viewpoints(seen a lot of your posts here b4, lol). But I'll just say that I never said to live in a fool's paradise or have some kind of idiot's contentment. I noticed these things and errors too, all the time. Just that most of the time, I let errors this small slip by and instead think about how some other people would have a real problem with it.. It's not pefect people in a perfectly profitable company designing this game, and in a creative industry, especially. Not even remotely trying to convince you, lol, just to speak. It's not bad to demand the best quality or anything, but do a video game in this industry and age..? Your tresholds for error are too low. A mediocre sequel to an brilliant, never-seen-before piece of sci-fi writing would have perfectly justified universal derision, but ME is hardly brilliant and new, and it's standard is, well, still probably way above all the other crap we see.

Yeah, if it was only a few minor erors, I could easily look apst it. But it's not.
If it's only hings that one can easily miss or not even notice, I could easily look past it.

But if it's a whole multitude of errors and bad decisions that even a 5-year old could spot, then I can't. They should have caught those. All this shows to me, is that Bio/EA doesn't care.
Just one..ONE guy hired to go trough the script/game several times and look for inconcistencies/errors should have been enough ot get rid of 99% of them. You know, when you publish a book you have an editor who checks it out. Lords knows how usefull another layer of checking for such stupid errors would have been.

The irony is how EASY it would have been to fix 90% of all of the errors - if anyone ever bothered to. Most of those are a result of the "Rule of Cool" and serve no actual purpose..they add nothing to the story/narrative.


No my firend...my treshold for error is not too low.

And you have to read the codex entry for omni-tools in ME1.(using phone here) Perfectly explains how omni-blades can exist, abeilt with simple explanations of mass effect fields(again) and graphene. Just that Shepard didn't have one of those in ME1.. It's cool now though.

I have read it and I do know how it works. I never liked it, nor do I like the ME3 version of it.
It sucks - plain and simple.
No matter how you cut it, you have a tiny device the size of a cell phone that can not only generate complex ME fields, but also fabricate thnig bigger than iteself in 0.1 seconds.

the Omni-Blade is nothing but a gimmick.

[Lotion Soronarr]

littlezack wrote...
Just because something's not hinted doesn't mean it can't be brought in. It's not like ME1 was iron-clad and they absolutely can't add stuff to the codex at later dates.

Just because you can, doesnt' mean you should.

Omni-blades are a bad idea. The explanation is even worse.
And kind of blade would have been better than what they went with.

[Killjoy Cutter]

augustburnt wrote...

 All the people freaking out at the OP are the reason Bioware has gone to ****, if you cant keep your story straight why would I trust you to make a game? Its called an RPG, look up the meaning and learn what its about.

+1 


Why should EAware care, though, they're after the shooter crowd and turning to rented content.  

[Fleenots]

DKruger wrote...

Ashley/Kaidan is not the sharpest tool in the shed.

Well I don't know about that, Kaidan managed to be promoted from Lieutenant Commander in M2 (reference in horizon colony) to Major in M3. And  I ma guessing it doesn't been that long.

And by the way it means that Kaidan now outranks by far Shepard. Does that means that he is now the Commanding officer of the Alliance Normandy SR2?
Or will he step down as Anderson in the first ME.
LoL

[Dariansarr]

Fleenots wrote...

DKruger wrote...

Ashley/Kaidan is not the sharpest tool in the shed.

Well I don't know about that, Kaidan managed to be promoted from Lieutenant Commander in M2 (reference in horizon colony) to Major in M3. And  I ma guessing it doesn't been that long.

And by the way it means that Kaidan now outranks by far Shepard. Does that means that he is now the Commanding officer of the Alliance Normandy SR2?
Or will he step down as Anderson in the first ME.
LoL

Neither Lieutenant Commander or Major outranks Commander 

Modifié par Dariansarr, 15 février 2012 - 11:15 .

[Dariansarr]

Lotion Soronnar wrote...

littlezack wrote...
Just because something's not hinted doesn't mean it can't be brought in. It's not like ME1 was iron-clad and they absolutely can't add stuff to the codex at later dates.

Just because you can, doesnt' mean you should.

Omni-blades are a bad idea. The explanation is even worse.
And kind of blade would have been better than what they went with.

I like how they did biotic attacks for Adepts, Sentinels and Vanguard tough