21 réponses à ce sujet

[genocidal villain]

Let's face it, banning people over any glitch and claiming it is an unfair advantage for other players is just not plausible. Why? If everyone can do it, then it is considered fair. If a player is using hacking the game from an outside source then it is an entirely different thing. If players have some kind of moral value about playing the game "legit" or fair, it really doesn't apply here because that's their stance. It's like saying I'm not going to play the N7 Destroyer or the Turian Ghost Infiltrator because they're cheap ass OP characters. I don't see how butthurt people can get over a CO-OP game score and N7 rank. I welcome players that can outscore me due to their "cheap ass characters" it helps out the whole team. In the end it doesn't really matter because score is no way recorded after the end of the game for players to see only the scoreboard that disappears after you exit it, and the N7 rank doesn't prove players' skill just how much time a player spent. 

If you want to ban people over exploiting something that's not part of the gameplay mechanics then you might as well ban people who abuses "corner peeking" or reload canceling. If I can peek through a corner and shoot my target when it can't even hit me that's exploiting the game mechanics especially since it's not part of core gameplay.

Also, banning people because Bioware is too lazy to patch it, so they "buff or nerf" guns just to fix it is just poor choice. How about fix the glitch instead of punishing people because developers are making poor choices to solve the problem. I'm respect what Bioware is doing, but I do not agree with these temporary solutions. Removing charged shots can really shift the balance of the game and guns that still have the ability to charge their shots is still susceptible to abusing the missile glitch. I've only paid attention to the last 2 random ban waves but 1600 people banned is pretty significant because if you look at the weekend operations the community barely makes it. The community, from my view, barely meets the quota at +/- 15%. Now I'm starting to run into people who are total dicks because of lets kick them out because she/he doesn't have a mic, their low N7 rank, their weapon level is too low and all that other annoying crap that has no correlation between the player's skill and their equipment.

To put it short, enforce the game by fixing bugs, accept your faults for not properly patching glitchs and patch them correctly and give player warnings don't punish them unless what they did is too severe. I don't approve of cheating from a outside program, but glitching is a grey area. It's like punishing my child to the electric chair because he stole 20$ from my wallet compared to robbing banks. I don't think perma bans are the perfect solution for the current glitches because it is Bioware's fault. Unless the person who was given about 2-3 warnings does not see the picture.

(Bare with me I'm still editing to making it sound right without making me trying to make Bioware look an ass sorry about that)

Modifié par genocidal villain, 27 octobre 2012 - 02:12 .

[Bryan Johnson]

Hmm we are lazy, interesting.

[Bryan Johnson]

Cake Tasty wrote...

Bryan Johnson wrote...

Hmm we are lazy, interesting.

Obviously. Posting on the forum whilst at work.

It's 7pm, core hours are 9-6 for me

[Bryan Johnson]

Geth Platforms wrote...

Bryan Johnson wrote...

Hmm we are lazy, interesting.

well you guys didnt fix ML glitch, change all charge gun, i think you mess up kyrase even more, because you cant double shoot it anymroe, before anyone say anything, bioware say it ok, and you guys only came out two patchs and some patchs bring new glitch,( unable to SS altas) and when is that getting fix? next patchs? in another 6 months? op have some point, other then that you guys are great

We did fix it, we fixed the original one.
Here is an example, you go to the doctor for a flu he gives you medicine to help you with that flu. 
In the meantime you catch another type of flu. From the outside the doctor did exactly what he was supposed to and help you get better for the original flu but from the outside looking in you still have the flu.


Now I don't mean to be rude have you ever tried to write software? It isn't easy.

Then there is this question,

How many programmers are on the team vs before launch?
How well do those programmers know the systems they now have to work on that they didnt before?
What are you even allowed to do in a patch?
What is the target audience affect?
How severe is the issue?

Yes from the outside looking in things may seem one way but there are a lot of questions that people don't think of that we have to consider and weigh.

This is one of the reason I have been so active as of late is to try and educate people what it is like working in the industry.

Modifié par Bryan Johnson, 27 octobre 2012 - 01:22 .

[Bryan Johnson]

Computron2000 wrote...

cowwy wrote...

Ok I have a question for the OP, if baseball players are using steroids, and it is EXPLICITLY stated that using such performance enhancing drugs, even though they are available, will get you kicked out of the MLB, is it the MLB's fault?

This analogy is not correct. The correct one is as follows

If baseball players get forcefully injected with steroids in 1 in 10000 swings of the bat, and it is EXPLICITLY stated that using such performance enhancing drugs, even though they are available, will get you kicked out of the MLB, is it the MLB's fault?

The answer is yes.

Now in Bioware's defense, the entire ban threat is a time buying technique. They neeed time to fix it and if they can't patch it up through an update and require a patch, it will take even more time.

If they said, "We're sorry, if you get the glitch, until we fix it its fine because its our fault", every bad tom, dick and harry will exploit it because there are no negative consequences

I believe your analogy is incorrect because it removes the very thing we are discussing here and that is "choice". We arent banning people who come accross the thing accidentally we are banning those that viciously exploit it.

[Bryan Johnson]

I do not believe we have taken a stance on the 6/6/6/6/6 glitch but I could be wrong. We are asking people to respec or promote. I am going to be talking to one of our teams on monday to see if we can take all those kits that are affected by this and return all the talent points to re-allocate. Having a 6/6/6/6/6 character will not get you an automatic ban, we realize it is a glitch and not an exploit (like the missile "glitch" is).

[Bryan Johnson]

jpraelster93 wrote...

cowwy wrote...
Well the thing is they got it partially right, but they didn't realize there was a different way to abuse the glitch, but as I stated, patching things takes time because they have to be properly tested and go through lengthy certification processes, they are 100% aware of the glitch, but now they have to find a way to fix it without breaking anything else, or implement that solution if they already have it.

I know patching takes time but you have to know PART of the reason that it takes as long as it does is because they have to pay for the patches I refuse to believe that isnt somewhat of a factor

Not everything is about money, how would a company like MS or Sony respond to us submitting a new patch every week for 3 months.
It would cause:
1) Other products to be delayed because we are clogging the cert process
2) Them to hire more staff, but what happens when we stop doing weekly patches do those people have to be fired?
3) Mass confusion from having so much going on at once.

[Bryan Johnson]

comrade8472 wrote...

Bryan Johnson wrote...

Geth Platforms wrote...

Bryan Johnson wrote...

Hmm we are lazy, interesting.

well you guys didnt fix ML glitch, change all charge gun, i think you mess up kyrase even more, because you cant double shoot it anymroe, before anyone say anything, bioware say it ok, and you guys only came out two patchs and some patchs bring new glitch,( unable to SS altas) and when is that getting fix? next patchs? in another 6 months? op have some point, other then that you guys are great

We did fix it, we fixed the original one.
Here is an example, you go to the doctor for a flu he gives you medicine to help you with that flu. 
In the meantime you catch another type of flu. From the outside the doctor did exactly what he was supposed to and help you get better for the original flu but from the outside looking in you still have the flu.


Now I don't mean to be rude have you ever tried to write software? It isn't easy.

Then there is this question,

1)How many programmers are on the team vs before launch?
2)How well do those programmers know the systems they now have to work on that they didnt before?
3)What are you even allowed to do in a patch?
4)What is the target audience affect?
5)How severe is the issue?

Yes from the outside looking in things may seem one way but there are a lot of questions that people don't think of that we have to consider and weigh.

This is one of the reason I have been so active as of late is to try and educate people what it is like working in the industry.

? you fixed the original one? 

writing soft ware just some t i85 graphing calc for math in grade 12 ( just to do the work... no I did not make or design the Ti85 calculators.)

please don't take wrong way I'm just  "trying" to logically approach this.

1)  doesn't matter on # of programmers
2) ok +1 to you
3)  yea what are you allowed to do in a patch?
4)  affect ? ellaboarate ?
5)  severe is the issue? 
(the 6,6,6,6,6) spec = very serious if you are banning for it... I would suggest giving them a respect card until it's fixed. * (by Bioware or whoever is contracted out to fix it.)

Missile glitch only affects platinum for pugs... so not that serious 4 out of 10. ( avoid platinum because of the guilt by being present while they spew cobras like no tomorrow.

what do you do  at Bioware?  just curius   

Yes we did

As for writing software on a calculator, lets say now you have 1million lines of code and a system 200 people have worked on. You now have to write what you did to interface what someone else did, and lets say for one reason or another that person isn't available.

1) Yes it does matter, it is called velocity, especially when there are other priorities
3) Can't comment on this one too much NDA
4) If something affects 10 users vs affecting 100k users
5) Please see previous post of mine

I have answered that question in my Q&A thread called "Meet Bryan"

[Bryan Johnson]

Azrael 007 wrote...

k1ngl1ves wrote...

Bryan Johnson wrote...

I do not believe we have taken a stance on the 6/6/6/6/6 glitch but I could be wrong. We are asking people to respec or promote. I am going to be talking to one of our teams on monday to see if we can take all those kits that are affected by this and return all the talent points to re-allocate. Having a 6/6/6/6/6 character will not get you an automatic ban, we realize it is a glitch and not an exploit (like the missile "glitch" is).

Re-allocate would be cool with me, but what of the non-BSN people?  Splash Screen...?

I too have wondered why they don't splash screen more about important things. Like, informing people to report missile glitchers or the weekly balance changes. If it wasn't for the forums, I wouldn't even know about most of them.

Splash screens aren't as easy as one would think, especially given that they have to be localized.

[Bryan Johnson]

jerrmy12 wrote...

Bryan Johnson wrote...

I do not believe we have taken a stance on the 6/6/6/6/6 glitch but I could be wrong. We are asking people to respec or promote. I am going to be talking to one of our teams on monday to see if we can take all those kits that are affected by this and return all the talent points to re-allocate. Having a 6/6/6/6/6 character will not get you an automatic ban, we realize it is a glitch and not an exploit (like the missile "glitch" is).

hey, i have an idea, unban people from ban waves 2-4, instead of a straight ban, give people a warning, no matter what they did, and/or fix the store so people don't have to exploit glitches to get some ultra-rares.
problems solved.

Warning was ban wave 1, the terms of service, our posting on the forum, common sense that cheating is wrong.

Life does not have a get out of jail free card.

[Bryan Johnson]

Draining Dragon wrote...

Bryan is showing impressive restraint.

OP, this argument is ridiculous and you should feel ridiculous.

Restraint from what, if I would post some of the ways people post at me. I would probably make news for "flipping out at fans", get in trouble at work etc.

I am a very calm person, and I also have accountability to what I say.


There was a serenity quote I wanted to use here when Mal meets the agent for the first time, but cant remember it.

Modifié par Bryan Johnson, 27 octobre 2012 - 02:03 .

[Bryan Johnson]

El_Chala_Legalizado wrote...

Bryan Johnson wrote...

Azrael 007 wrote...

k1ngl1ves wrote...

Bryan Johnson wrote...

I do not believe we have taken a stance on the 6/6/6/6/6 glitch but I could be wrong. We are asking people to respec or promote. I am going to be talking to one of our teams on monday to see if we can take all those kits that are affected by this and return all the talent points to re-allocate. Having a 6/6/6/6/6 character will not get you an automatic ban, we realize it is a glitch and not an exploit (like the missile "glitch" is).

Re-allocate would be cool with me, but what of the non-BSN people?  Splash Screen...?

I too have wondered why they don't splash screen more about important things. Like, informing people to report missile glitchers or the weekly balance changes. If it wasn't for the forums, I wouldn't even know about most of them.

Splash screens aren't as easy as one would think, especially given that they have to be localized.

Talking about localizations...
Can I translate some parts of the game?
Because there are some stuff in Spanish that makes me want to burn the first entity I see

Pass along what they are, and what the english equivilant is (so I can look it up in the database) and I will follow up with our localization manager to see if we can update them.

[Bryan Johnson]

Zero132132 wrote...

Bryan, I don't mean to be rude, but you should probably remember that this is the internet, and most people aren't going to change their minds just because someone posts a rational, coherent set of reasons that they're wrong. The bull**** hate for the QA team isn't going to dissipate, even if it absolutely should.

Maybe NDA prohibits talking about this too, but how well do people comment out their coding and **** in the video game industry? It seems like for bugfixing, it'd be great to detail what a specific bit of code was doing, but comments can be really time consuming. With the deadlines you guys have to meet, is that something that often ends up falling by the wayside a bit? Are a lot of the problems unrelated to that, and more related to using a game engine designed around single-player for a multiplayer mode?

Just curious.

I am well aware, its not those people I am after, it is the rational ones I wish to give more knowledge to.

Comments are present in the code base, you also have to consider you are using someone elses technology. IE we use Unreal Engine 3, so we have to use code that Epic wrote. You also have many different styles of code that you can write, the industry isn't "mature" (programming) as there are universal standards. I mean look at coding standards the industry as a whole cant even comment on what is correct for capitalization. 

Sure some stuff is not as well documented as well as it could be, but once again this is universal.

[Bryan Johnson]

comrade8472 wrote...

Bryan Johnson wrote...

Yes we did

As for writing software on a calculator, lets say now you have 1million lines of code and a system 200 people have worked on. You now have to write what you did to interface what someone else did, and lets say for one reason or another that person isn't available.

1) Yes it does matter, it is called velocity, especially when there are other priorities
3) Can't comment on this one too much NDA
4) If something affects 10 users vs affecting 100k users
5) Please see previous post of mine

I have answered that question in my Q&A thread called "Meet Bryan"

oh  right forgot it was in patch notes

ah so that' sound like  fun. and a mess.

1) ok thank you... I guess it does matter on how  quickly it'll get done.
3) NDA = hear that alot    so I'm guessing it's also against NDA to say what is in the NDA. (would be surprised if it wasn't)
4) ah  thanks
5) in  this thread if so i think I read it...

oh missed that entirely   cool I'll look through that in a bit.  


is the corner peeking and shooting bannable offence???  (being in a corner so that you can shoot and see the foe. but they can't hit you)

No it's a game mechanic, same as reload canceling it is there on purpose for "high level" play.

[Bryan Johnson]

jerrmy12 wrote...

Bryan Johnson wrote...

jerrmy12 wrote...

hey, i have an idea, unban people from ban waves 2-4, instead of a straight ban, give people a warning, no matter what they did, and/or fix the store so people don't have to exploit glitches to get some ultra-rares.
problems solved.

1. maybe sum ppl don't go on the forums
2. warning is STILL better
3. actually read my last part, fix the store so people don't have to exploit glitches to get some ultra-rares
4. if you don't the playerbase WILL keep shrinking.
5. if i ever get banned i will kill myself, over 1000 games over 500 VERY painful hours of the crappy store.

The entirity of your post seems to sum up to "Ignorance is an excuse" when any of the warnings we provide are more than sufficient. 
Fix the store in what way, because it doesn't work how you expect it to, it is broken? The best analogy I can think of is, I work hard to buy a car but it isnt the best car available so I am perfectly justified stealing a car? Then when I get caught they will just tell me not to do it again. 

Yah your right when we ban people the player base will shrink, that is math. I would rather have a smaller player base of non cheaters than a player base of base that is mixed.

I mean if you are cheating yourself everything then what does that earn BioWare as a company? Certainly not any profit from buying card packs, not the appearance that we deal with people who break our rules. All it costs us is money we are paying for servers for these players to continue to break our rules. This certainly feels like a very much win-lose scenario.

If you have a gripe against me because I banned you 2 days ago, then please take a step back and think.

Modifié par Bryan Johnson, 27 octobre 2012 - 02:46 .

[Bryan Johnson]

Methenu wrote...

Bryan Johnson wrote...

Zero132132 wrote...

Bryan, I don't mean to be rude, but you should probably remember that this is the internet, and most people aren't going to change their minds just because someone posts a rational, coherent set of reasons that they're wrong. The bull**** hate for the QA team isn't going to dissipate, even if it absolutely should.

Maybe NDA prohibits talking about this too, but how well do people comment out their coding and **** in the video game industry? It seems like for bugfixing, it'd be great to detail what a specific bit of code was doing, but comments can be really time consuming. With the deadlines you guys have to meet, is that something that often ends up falling by the wayside a bit? Are a lot of the problems unrelated to that, and more related to using a game engine designed around single-player for a multiplayer mode?

Just curious.

I am well aware, its not those people I am after, it is the rational ones I wish to give more knowledge to.

Comments are present in the code base, you also have to consider you are using someone elses technology. IE we use Unreal Engine 3, so we have to use code that Epic wrote. You also have many different styles of code that you can write, the industry isn't "mature" (programming) as there are universal standards. I mean look at coding standards the industry as a whole cant even comment on what is correct for capitalization. 

Sure some stuff is not as well documented as well as it could be, but once again this is universal.

Doesn't have to be industry wide, though, does it?  I mean, BioWare has been using the UE3 engine and SDK for ME, ME2 and ME3, I would assume that at least internally there has been an implementation of a "standard" or "best practices" methodology otherwise you'd be looking at chaos.  That way if you bring a new programmer/qa'er in you don't have to explain how you nested the if else statements or whathaveyou, you just have to give them an overview of the standards BW has instituted regarding the naming of variables, comments, etc to keep everything rolling smoothly.

Or am I totally off-base here?  

No I wasnt saying that we dont use "best practices". I was using the example that a coding standard not being agreed upon is an example of how immature the software development industry is.

[Bryan Johnson]

DeathIsHere wrote...

@Bryan: The idea that the 6/6/6/6/6 spec was a bannable offense came from the cheating compendium topic Ernest Tse had up. Here's the post in question:

http://social.biowar...450/15#14551717

A few people were wondering what's considered "exploiting" the 6/6/6/6/6 spec as it's hard to tell if somebody knew it was a glitch or not. Thankfully I haven't encountered this glitch (haven't unlocked any of the characters afflicted by it unfortunately) but it seems like a major issue if this is indeed a bannable offense. Nobody knows and it seems like it'd have to be patched to be fixed so that leaves a large amount of gray area for people to get banned without realizing they were breaking the rules.

Thanks ill speak to Ernest on monday basically it is the same kind of deal as anything else if you are using it to your advantage a lot (ie you are exclusively playing that kit past what is resonable for you to fix it) then we consider it an exploit.

[Bryan Johnson]

Rip504 wrote...

Jiovanie- wrote...


BioWare doesn't release broken content; they relase content, to expect perfection is quite ludicrous. Nothing in this world is perfect, and this world will NEVER be perfect. The sooner you learn to apply that to everything in this world, the better. 

We the community asked for weekly patches; that's our fault. I would rather have monthly patches as opposed to weekly patches. The product doesn't have to advertise that there might be glitches or bugs within it. You as a person should have enough common sense to know that not everything is as it seems. 

I'm losing my faith in humanity everytime I visit the internet. It's a shame really.

Lol so am I. You are willing and accepting to pay for a product with multiple issues. Where does the threshold begin and end?
I am holding BW accountable for their actions.They released a product with multiple bugs/glitches. Fact. Nothing more. I fully understand it is a part of the product. You should not make ludicrous assumptions. I do construction. I am only allowed to be off by a tenth of an inch when laying a tile floor. There are multiple examples of perfect or near perfect products. My main question was is BW contempt with the quality of products they are releasing. Did I ever legally agree to bugs/glitches?

"I bought a controller from Best Buy. The right analog would stick a little,causing the product to not work properly or as intended. I then returned it to Best Buy to exchange it. They gave me no trouble. The new one I got is also broken. The light on the Play and charge does not work. I have returned the product and got another one. (Third) With No trouble. If I wanted my money back I would be able to get it back. Neither of these issue cause the controller to be unusable,but by definition both of these controllers are broken. As they do not function
in the way they are intended to. Proven by Best Buy willingness to fix my issue.

So while these problems barely effect anything,there is still an issue. A issue worthy of refunding my money or replacing my product. Fixing my issue. "

cowwy wrote...


Bryan might respond to this as well, but I would like to reiterate what he said earlier.

They fixed the original missile glitch.

People like you keep saying that they are not doing their job, and that they don't care about the game, and make every ridiculous claim, but the fact of the matter is that they are VERY OBVIOUSLY working on the issues.
They've stated multiple times that they are working on fixing these issues but they have to test them and go through certification processes that are both expensive and time consuming, so they try to get the most
bang for their buck, by releasing patches with more than just "Fixed an issue where players could use infinite missile launchers".

Also  take that legal argument to a court of law. Tell me how that goes for you. I don't claim to be a legal expert, but I'm pretty sure you've received the product that you've paid for.

No never once did I ever claim BW was not doing their job. BW does a very good job. That is your mistaken interpretation of what I said. I am asking was BW aware of the Missile Glitch before release? If not,why not?
If so, then BW was contempt to release a glitch/buggy product? We are suppose to accept that with open arms? Not me.

Really? Buggy DLC was advertised? I assume it was advertised as really "cool" content. Never did they tell me they were releasing a buggy product they may get some user's banned.

To the Baseball analogy. If the MLB placed the enhancements into the players lockers,then yes the MLB would also be held responsible. As BW has placed the Glitch within your character screen/stats game. People are not exploiting ways to create the glitch. They are exploiting a glitch that BW's product has placed within their game.
It is wrong and should be considered cheating by all means.

Okay so ill attempt to answer this from an industry standard/computer engineering practices. Do we want our game to have bugs in it, nope, who would? Is there a point where you have to say enough is enough, ship the product the way it is? Absolutely 

Software is not something you can compare to a real physical thing, anyone in the industry will tell you. NASA for example had a mars lander lost because it didnt know how to calculate metric properly. In software a simple logic gate doubles the complexity of your system. An int can be 2^32 different valid values, do you want to try and account for every single one of those in a single value?

Were we aware of the missile glitch before launch, nope. Because that is not a path that we took. I can stand here with pretty good certainty if it wasnt for the internet less than 1% of the people he know about missile glitching now would have no idea what that is. Finding a bug is one thing, being able to follow instructions to do it is another. It took a couple hundred thousand/millions of people 3 months to find it, 200 people over the course of 1-2 years is no where near the same.

There is a video series that is on the top of my head that used to be on the escapist where the person talks about the industry. I would recommend you watch some of them to find out what it is like because I can assure you it is vastly different working with software then it is working with construction.

[Bryan Johnson]

cowwy wrote...

WARMACHINE9 wrote...

cowwy wrote...

WARMACHINE9 wrote...

Idon't have a problem with the missile glitchers being banned as thats an obvious abuse of a unintentinal bug but banning people for the six glitch is a little harsh. I had a friend who had the six glitch happen to two characters and he played with them wondering what was up. He wasn't looking for an advantage and when it happened I told him to contact BW so they wouldn't ban him for the glitch. He's not the type to cheat and when I told him the remedy he fixed it. It would be a shame for someone like him to get bvanned as he's a huge fan and really cares about the community.

Bryan has a post about that somewhere in this thread where he basically states that they're not going to ban people who accidently used it once or twice, they're going to ban people who realized that it was a glitch and abused it constantly to gain an advantage.

I'm really glad to hear that. At least they're swingin' that ol' hammer with a bit of a soul. Some companies aren't so nice.

I'm pretty sure that they've always been kinda lenient with the ban hammer. They always look for extenuating circumstances when deciding what kind of punishment to dole out. They look at things such as; whether or not the person abuses the glitch, or simply stumbled upon it, whether or not they self report themselves, and whether or not they go on the BSN.

Indeed we do, we are not cut and dry. There are a few people on this forum that I see that we have had reason to ban but haven't. I wont say names but they know who they are.

Modifié par Bryan Johnson, 27 octobre 2012 - 04:15 .

[Bryan Johnson]

Cyonan wrote...

Bryan Johnson wrote...

There is a video series that is on the top of my head that used to be on the escapist where the person talks about the industry. I would recommend you watch some of them to find out what it is like because I can assure you it is vastly different working with software then it is working with construction.

Are you by chance talking about Extra Creditz?

They're actually on Penny Arcade now.

Thank you, the particular episode I wanted to link is "So you want to be a producer"

[Bryan Johnson]

ray12a wrote...

If you guys could code as well as you pass the buck, we, or rather you, wouldn't be having these problems.

It seems like you guys are just about incapable of implementing features without screwing up something else in the process. How much are you paying your QA testers? Do you guys even play the game? I cannot begin to comprehend the majority of blunders that get by a series of "qualified professionals". If he/ she/ they can't perform up to par, I'd be more than happy to take that job off of their hands.

My advice: Quit stalling. Quit lying. Enough with the mistakes, the rework and time squandering. Do your jobs. People are paying for your product, and these increasingly ridiculous shortcomings could end up costing you more than manhours.

Show me where I have lied. Show me a post where a programmer has passed the buck, please I am interested to talk to them.
Since you clear are after the QA testers we have, then tell me what in my job I could do better, and please be specific. 

You are attacking my personal integreity 

Here you go: http://www.bioware.com/careers

Modifié par Bryan Johnson, 27 octobre 2012 - 09:40 .

[Bryan Johnson]

Geimhreadh wrote...

Bryan Johnson wrote...

Draining Dragon wrote...

Bryan is showing impressive restraint.

OP, this argument is ridiculous and you should feel ridiculous.

Restraint from what, if I would post some of the ways people post at me. I would probably make news for "flipping out at fans", get in trouble at work etc.

I am a very calm person, and I also have accountability to what I say.


There was a serenity quote I wanted to use here when Mal meets the agent for the first time, but cant remember it.

"Captain Reynolds.  I should tell you, so you don't waste your time: you can't make me angry."
"Please, spend an hour with him."

Or possibly "I am, of course, wearing full body armor.  I am not a moron!"

And to anyone that's wondering how these things can make it live: it's kinda shocking how many unintended consequences can show up in even a 200-line string manipulation program that nobody's really trying to break.  The number of man-hours it would take to get anywhere close to completely bug-fixing and exploit-proofing a project of this scale is... impressive.  Not to mention prohibitive.  And that's assuming that 200 people can catch every possible way the thousands of players can break the game (accidentally or otherwise).

It was actually this

Mal: No, no, you’re working this deal all crabbed. You got to open with payment. Make a flush offer and then we’ll see where this conversation goes.

The Operative: That’s a trap. I offer you money you’ll play the man of honor and take umbrage. I ask you to do what’s right, you’ll play the brigand. I’ve no stomach for games; I already know you’ll not see reason.

Modifié par Bryan Johnson, 27 octobre 2012 - 10:08 .