In April of 2009, Rockstar Games settled out of court with with "over 100" Rockstar San Diego employees to the tune of $2.75 million (approximately $27,500 per person). The case, "Garrett Flynn, et al. v. Angel Studios, Inc./Rockstar Games et al.," was filed on August 21, 2006, by ex-Rockstar San Diego 3D artists Terri-Kim Chuckry and Garrett Flynn on behalf of themselves and fellow 3D artists, alleging that Angel Studios/Rockstar San Diego had "failed to pay overtime compensation ... to certain Angel employees whose primary duties are or were to create, produce, copy and/or install images into video games, using commercial or in-house software computer programs."
Sound familiar? That's likely due to the past week's barrage of Rockstar Games employees speaking out against alleged quality of life issues at the developer's various studios, including claims of "numerous non-exempt designers and artists have had their overtime pay cut as a result for being 'too senior.'"
In a press release issued after the settlement, Rockstar Games refuted the lawsuit's claims. "Angel denies the allegations in the lawsuit and admits no liability or wrongdoing in settlement." The settlement document (obtained earlier today by Joystiq) also spells out Rockstar's reasons for settling the suit, saying "further litigation would be protracted and expensive for all parties." Unsurprisingly, the company also contested in the settlement that a ruling against it was "relatively unlikely" for a number of reasons.
That said, when a multi-billion dollar corporation settles a suit with its employees out of court and awards them nearly $3 million in compensation, that's quite a statement unto itself -- regardless of the great lengths at which the final court settlement goes to deny that claim. We've contacted Rockstar Games for comment and haven't heard back as of publishing.
Rockstar quietly settled class-action lawsuit with 'over 100' ex-Rockstar San Diego employees
31
Reader Comments (31)
Posted: Jan 15th 2010 6:16PM Spunky Monkey 190906 said
Bit suprised at the way Rockstar handled this, been pumping out some of the best games this gen, and yet, this is happening behind closed doors
Reply
Posted: Jan 15th 2010 6:16PM BrokenTriforce said
You'd think that after making so many GTA games that the company would figure out that crime doesn't pay.
Reply
Posted: Jan 15th 2010 6:23PM whylekat said
Umm steal cars, drugs, money, helicopters, Subway trains, then kill cops and lose them by breaking line of site .... and it's totally forgotten. Eventually own a massion or penthouse apartment.. If life was like GTA, Crime definetly DOES pay! Except if you're in a biker gang..
Reply
Posted: Jan 15th 2010 6:54PM BrokenTriforce said
@ copa
I doubt any of the suits have ever played a GTA game.... Which would mean that's their regular lifestyle. o_O
Reply
I doubt any of the suits have ever played a GTA game.... Which would mean that's their regular lifestyle. o_O
Posted: Jan 15th 2010 6:16PM Captain Planet Planeteer Power said
When you walked through the door it was clear to me, you're the one we abuse, who we treat like shit, 'cause you're a...ROCKSTAR
Reply
Posted: Jan 15th 2010 6:20PM Hooch said
I question Planet's decision making skills.
http://www.youtube.com/watch?v=ZQJrovKgrTw
Why Belfast? WHYYYY!?
Reply
http://www.youtube.com/watch?v=ZQJrovKgrTw
Why Belfast? WHYYYY!?
Posted: Jan 15th 2010 6:24PM Hooch said
I most definitely am not, sorry to dissapoint you.
I just feel derailing a page of comments bashing him is pointless (And yes I realise stating those opinions is ironic as it also wastes a page) and that to be honest, he's not a troll, just a very naughty boy,
And yes, I'm crazy.
Reply
I just feel derailing a page of comments bashing him is pointless (And yes I realise stating those opinions is ironic as it also wastes a page) and that to be honest, he's not a troll, just a very naughty boy,
And yes, I'm crazy.
Posted: Jan 15th 2010 6:29PM Captain Planet Planeteer Power said
@ Hooch
Because Irish chicks will do anything...
ANYTHING...
You know what I mean...
In the butt.
Reply
Because Irish chicks will do anything...
ANYTHING...
You know what I mean...
In the butt.
Posted: Jan 15th 2010 6:37PM MystileArmor said
Did someone say anything about Irish girls and butt?
Reply
Posted: Jan 15th 2010 6:40PM Captain Planet Planeteer Power said
Hey, my wife Rosie is Irish and while she may not be much to look at, that broad puts out.
Reply
Posted: Jan 16th 2010 1:30AM (Unverified) said
Hooch: As an irishman, Lets take this one outside.
Reply
Posted: Jan 15th 2010 6:18PM (Unverified) said
I used to consider Rockstar as one of the classy studios...
Reply
Posted: Jan 15th 2010 6:25PM (Unverified) said
Wow. I would take my settlement and seek employment elsewhere. Maybe not a good idea all things considered ... and staying with Rockstar may be part of the agreement as well.
Reply
Posted: Jan 15th 2010 6:31PM (Unverified) said
Just because they settled doesn't mean they were guilty, though over one hundred employees all behind a lawsuit would suggest otherwise.
Will this be the subject of the Law Of The Game post this week?
Reply
Will this be the subject of the Law Of The Game post this week?
Posted: Jan 15th 2010 8:24PM eudaimo said
If the two cents of a Southern California employment lawyer is worth anything (I have worked on a number of similar class actions both in and outside the software industry, for what that's worth), here they are:
I haven't had time to peruse the Complaint in this case, but it was probably a "misclassification" case (the vast majority are). The idea is that employees are classified as salaried, but feel that they should have been hourly (and gotten overtime).
These cases are rarely about "guilt" or "innocence," particularly in California's highly complex and demanding overtime law structure. Usually, the employers and named employees just disagree on the law. (This is a class action so the fact that 100 employees get paid does not mean 100 employees filed a lawsuit. Usually, it would be brought by 1 or 2).
Settlement is not surprising:
1. These cases almost NEVER go to trial. I have never seen one go to trial in several years of practice in the region. It's not worth the money. It's not worth the risk. It just isn't done.
2. The settlement in this case might SOUND high (estimated 27k per employee, but it probably is not. Let's say 100-150 employees, making an average of $77k annually and working (on average) 100 hours of overtime a year. None of that is atypical in the computer industry. The potential exposure if those employees are "misclassified" would be very high. *Much* higher than 3 million. I'm not going to do the calculations, but let's be conservative and guess that the R* could see 8.5M in liability if it lost (not including legal fees, which could exceed 1M). Let's also say that counsel guessed that R* had a 2/3 chance of prevailing at trial (Very reasonable, but not a slam dunk).
A 3.5M settlement is sound business sense for both sides and reveals very little.
Reply
I haven't had time to peruse the Complaint in this case, but it was probably a "misclassification" case (the vast majority are). The idea is that employees are classified as salaried, but feel that they should have been hourly (and gotten overtime).
These cases are rarely about "guilt" or "innocence," particularly in California's highly complex and demanding overtime law structure. Usually, the employers and named employees just disagree on the law. (This is a class action so the fact that 100 employees get paid does not mean 100 employees filed a lawsuit. Usually, it would be brought by 1 or 2).
Settlement is not surprising:
1. These cases almost NEVER go to trial. I have never seen one go to trial in several years of practice in the region. It's not worth the money. It's not worth the risk. It just isn't done.
2. The settlement in this case might SOUND high (estimated 27k per employee, but it probably is not. Let's say 100-150 employees, making an average of $77k annually and working (on average) 100 hours of overtime a year. None of that is atypical in the computer industry. The potential exposure if those employees are "misclassified" would be very high. *Much* higher than 3 million. I'm not going to do the calculations, but let's be conservative and guess that the R* could see 8.5M in liability if it lost (not including legal fees, which could exceed 1M). Let's also say that counsel guessed that R* had a 2/3 chance of prevailing at trial (Very reasonable, but not a slam dunk).
A 3.5M settlement is sound business sense for both sides and reveals very little.
Posted: Jan 15th 2010 9:10PM Benjamin Gilbert said
First and foremost allow me to say that I absolutely appreciate you weighing in on this. While I think your points are valid (and things I considered while writing the piece), I don't necessarily agree with your conclusions.
I found the settlement more "revealing" in the sense that Rockstar has already gone through these kind of complications before. Furthermore, if the counsel were of sound belief that Rockstar hadn't misclassified workers, why not take it to trial? (Especially when there's plenty of money behind them and likely very little on the other side of the table.) It is a sound business decision for both sides, but that doesn't make the original necessity for the suit any less revealing. That's my two cents at least.
Reply
I found the settlement more "revealing" in the sense that Rockstar has already gone through these kind of complications before. Furthermore, if the counsel were of sound belief that Rockstar hadn't misclassified workers, why not take it to trial? (Especially when there's plenty of money behind them and likely very little on the other side of the table.) It is a sound business decision for both sides, but that doesn't make the original necessity for the suit any less revealing. That's my two cents at least.
Posted: Jan 15th 2010 11:07PM eudaimo said
Hi Ben,
Thanks. And I appreciate your analysis as well.
I'm definitely not weighing in on any of the prior complications for R*, like R* Spouse. I will note that there is a difference between misclassifying a worker as salaried and having poor employment conditions for salaried workers (the latter is arguably worse, but is not generally illegal). But I do I recognize that the high demands of crunch time leads to an unhappy workforce, thereby leading to more lawsuits, meritorious or otherwise.
I will note also that the merit of these lawsuits tends to come down to more philosophical questions than moral ones, like: Do computer programmers use "discretion?" If so, they should be salaried and not hourly. This is a legal question that has come up time and again in case after case, but is rarely the result of a "nefarious" practice. It's just a legal disagreement.
But understand that when I say these cases almost never go to trial, I don't mean the way MOST cases "almost never" go to trial. This is a very particular beast: It's not 1 in 10 or even 1 in 100. I believe the total number to have gone to trial in California is in the single digits, but I could be wrong on that point).
As for "why not take it to trial," I'm not sure I understand your analysis. To say that R* has higher resources is to suggest that R* might credibly conclude that it should "outspend" the Plaintiff's. That is rarely a good idea. In the end, you spend a couple of million dollars to litigate aggressively, just to take a chance at winning in front of a Southern California jury (which brings its own concerns). The California Plaintiff's Bar is extremely sophisticated when it comes to W&H class actions. Most credible ones are run by very experienced plaintiff's firms who have experience in dozens of prior cases.
The settlement analysis in these cases are almost always purely mathematical. After the case is filed, most attorneys will read the Complaint and come up with a "likelihood of risk." They will then do some research: find out why the employees are classified the way they are and then interviewing some employees to find out if their duties justify the classification. Based on that investigation, the "likelihood of risk" will go up or go down. I'm oversimplifying a lot, of course, but after that it's basically Likelihood of Risk(X) Total Potential Exposure. The most common approach is to file a motion to have the case thrown out. If that fails, settle.
For that group of computer programmers, even a (relatively) low risk of loss could easily produce a settlement of that size without any real "Oh crap, we screwed up here" (which I do see from time to time).
Reply
Thanks. And I appreciate your analysis as well.
I'm definitely not weighing in on any of the prior complications for R*, like R* Spouse. I will note that there is a difference between misclassifying a worker as salaried and having poor employment conditions for salaried workers (the latter is arguably worse, but is not generally illegal). But I do I recognize that the high demands of crunch time leads to an unhappy workforce, thereby leading to more lawsuits, meritorious or otherwise.
I will note also that the merit of these lawsuits tends to come down to more philosophical questions than moral ones, like: Do computer programmers use "discretion?" If so, they should be salaried and not hourly. This is a legal question that has come up time and again in case after case, but is rarely the result of a "nefarious" practice. It's just a legal disagreement.
But understand that when I say these cases almost never go to trial, I don't mean the way MOST cases "almost never" go to trial. This is a very particular beast: It's not 1 in 10 or even 1 in 100. I believe the total number to have gone to trial in California is in the single digits, but I could be wrong on that point).
As for "why not take it to trial," I'm not sure I understand your analysis. To say that R* has higher resources is to suggest that R* might credibly conclude that it should "outspend" the Plaintiff's. That is rarely a good idea. In the end, you spend a couple of million dollars to litigate aggressively, just to take a chance at winning in front of a Southern California jury (which brings its own concerns). The California Plaintiff's Bar is extremely sophisticated when it comes to W&H class actions. Most credible ones are run by very experienced plaintiff's firms who have experience in dozens of prior cases.
The settlement analysis in these cases are almost always purely mathematical. After the case is filed, most attorneys will read the Complaint and come up with a "likelihood of risk." They will then do some research: find out why the employees are classified the way they are and then interviewing some employees to find out if their duties justify the classification. Based on that investigation, the "likelihood of risk" will go up or go down. I'm oversimplifying a lot, of course, but after that it's basically Likelihood of Risk(X) Total Potential Exposure. The most common approach is to file a motion to have the case thrown out. If that fails, settle.
For that group of computer programmers, even a (relatively) low risk of loss could easily produce a settlement of that size without any real "Oh crap, we screwed up here" (which I do see from time to time).
Posted: Jan 16th 2010 11:00AM Benjamin Gilbert said
I should be more explicit! I meant by "Rockstar has had these complications in the past" that this case is revealing a history of Rockstar San Diego with misclassified worker claims. The existence of this case, regardless of how these cases usually run, is -- at very least in the court of public opinion -- a good indicator of the potential for this to be happening right now. There could very possibly be no correlation between this past case and the current allegations, but that doesn't make it *look* any better for Rockstar when this comes to light and they don't comment on it. Furthermore, there was a press release created after this case was settled that never got released. That strikes me as odd at very best (and kinda nefarious at worst).
The reason for me pointing out this case though was, more than the result, to point out that it's happened before. There's a precedent for misclassification claims at Rockstar (and Rockstar San Diego *specifically*) and that's telling. Word ... More
Reply
The reason for me pointing out this case though was, more than the result, to point out that it's happened before. There's a precedent for misclassification claims at Rockstar (and Rockstar San Diego *specifically*) and that's telling. Word ... More
Posted: Jan 16th 2010 3:32PM (Unverified) said
Ben,
While I understand what you're saying, I do think you're missing the point that DR is making.
First of all the issue specific to R*SD at least at the time of the original reclass and law suit, was very much about the legal definition of how exempt is defined in California. The main points of legal definition (not real world definiton and not getting into how "the man" is trying to keep the little guy down) for an Artistic or Creative exemption the main 2 criteria include:
1. The position has the employee artistically involved in the work they do. Over simplifying this down to a black and white description, the law is asking is the person a automatron that is basically just doing exactly what they're told to do involving a set of skills but requiring little to no artistic/creative choice. So from a legal point of view the law is saying a non-exempt 'artist' (think about what that word even means) is someone that could be a person plucked off the street and then trained via x amount of instruction to then just churn out 3D objects, textures, and game elements without regard to any inherient artistitc talent.
2. There is also a minimal salary test for this as well, which I think is around $40-45K, which in the case of R*SD is pretty much a non an issue now or back in June of 2006 when the company proactively did it's reclassification (note: well ahead of any legal action). Almost all of the Artists (even the Jr ones) are making at least that as their base, and then there's OT pay on top of that. So was a non-issue then and now.
Keep in mind that at the time of the re-classification all those that were reclassed kept their current exempt salaries in full and then started getting OT on top of that. So for a studio that at the time was averaging 45 hours per week (even factoring in periods of 'crunch') this meant an almost 18% pay increase to the artist (and all the other types of roles in the studio that were also reclassed at that time - ie myself as a programmer). On top of that the management at the time (not sure if they're still there) set everyone up as "Salary non-exempt" which meant everyone got their base salary (their original at least market rate) even if they worked under 40 hours a week, but got OT for any hours over 8 in a day or 40 in a week. Personally I made out really well, since on days when needed to take off early I got paid in full, yet in the same week if I I'd potentially get OT pay while under 40 for the overall week. In my new role is actually kind of sucked to take an effective pay cut since my base rate has been reset to fall in line to market rate with the exepected OT already built in. BTW I left for personal reasons to be closer to family back in the bay area and not because I felt abused by the R*SD management of old.
Anyway, I personally hate seeing all this playing out in the press, when there are success stories for the employees and company to be shared as well. Of course the typical R* response to press stuff is just "talk to the hand", which is a shame. I wish those still there luck with RDR which I WILL buy in support of all those who I know are working very hard and putting themselves into the game. I still miss the feeling of creating something special in the games we made vs just another internal company app.
Reply
While I understand what you're saying, I do think you're missing the point that DR is making.
First of all the issue specific to R*SD at least at the time of the original reclass and law suit, was very much about the legal definition of how exempt is defined in California. The main points of legal definition (not real world definiton and not getting into how "the man" is trying to keep the little guy down) for an Artistic or Creative exemption the main 2 criteria include:
1. The position has the employee artistically involved in the work they do. Over simplifying this down to a black and white description, the law is asking is the person a automatron that is basically just doing exactly what they're told to do involving a set of skills but requiring little to no artistic/creative choice. So from a legal point of view the law is saying a non-exempt 'artist' (think about what that word even means) is someone that could be a person plucked off the street and then trained via x amount of instruction to then just churn out 3D objects, textures, and game elements without regard to any inherient artistitc talent.
2. There is also a minimal salary test for this as well, which I think is around $40-45K, which in the case of R*SD is pretty much a non an issue now or back in June of 2006 when the company proactively did it's reclassification (note: well ahead of any legal action). Almost all of the Artists (even the Jr ones) are making at least that as their base, and then there's OT pay on top of that. So was a non-issue then and now.
Keep in mind that at the time of the re-classification all those that were reclassed kept their current exempt salaries in full and then started getting OT on top of that. So for a studio that at the time was averaging 45 hours per week (even factoring in periods of 'crunch') this meant an almost 18% pay increase to the artist (and all the other types of roles in the studio that were also reclassed at that time - ie myself as a programmer). On top of that the management at the time (not sure if they're still there) set everyone up as "Salary non-exempt" which meant everyone got their base salary (their original at least market rate) even if they worked under 40 hours a week, but got OT for any hours over 8 in a day or 40 in a week. Personally I made out really well, since on days when needed to take off early I got paid in full, yet in the same week if I I'd potentially get OT pay while under 40 for the overall week. In my new role is actually kind of sucked to take an effective pay cut since my base rate has been reset to fall in line to market rate with the exepected OT already built in. BTW I left for personal reasons to be closer to family back in the bay area and not because I felt abused by the R*SD management of old.
Anyway, I personally hate seeing all this playing out in the press, when there are success stories for the employees and company to be shared as well. Of course the typical R* response to press stuff is just "talk to the hand", which is a shame. I wish those still there luck with RDR which I WILL buy in support of all those who I know are working very hard and putting themselves into the game. I still miss the feeling of creating something special in the games we made vs just another internal company app.
Posted: Jan 20th 2010 12:32AM eudaimo said
Scotty,
Thanks for your informative post. Like I said, I hadn''t read the Complaint, so your specifics were useful.
Ben, Thanks for your vigilance as well. I don't pretend to know what is going on at R*, but I just wanted to dispel any mistaken inference by readers that settling a class action (or any case, honestly) is a smoking gun. (FYI, I can't read the entirety of your last comment, Ben. There is a link for "More," but it does not work.
Reply
Thanks for your informative post. Like I said, I hadn''t read the Complaint, so your specifics were useful.
Ben, Thanks for your vigilance as well. I don't pretend to know what is going on at R*, but I just wanted to dispel any mistaken inference by readers that settling a class action (or any case, honestly) is a smoking gun. (FYI, I can't read the entirety of your last comment, Ben. There is a link for "More," but it does not work.
Sorry, you must be logged in to leave a comment.
Featured Stories
The most popular posts
in the last 7 days
- Vita 'UMD Passport' won't be offered in US 221 comments
- Kingdoms of Amalur: Reckoning review: A tempting fate 153 comments
- David Jaffe leaves Eat Sleep Play, layoffs hit developer [Update] 107 comments
- Blizzard taking Valve to court over 'DOTA' trademark 96 comments
- Don't call it a remake: Final Fantasy X is a 'remaster,' to be clear 95 comments










