You’d think the last thing a games developer should be worried about is copying his own work, right? Wrong. Last week, the High Court published its judgment of a claim brought by a games developer against his employer over a games concept which the developer had created when he was freelance but which later he copied and effectively pitched to his employer as a new company project. The developer later sued for breach of copyright and confidence, in which we now know he was unsuccessful. Read on for more details…
Need to know points
You can read a summary of the case below, but here are some upfront thoughts on the need to know/best practice points for developers which came out of this case:
- When a freelance games developer joins a new employer, discussing his/her existing games concepts at the outset and how they will be treated going forward should help to avoid any confusion as to who owns the IP later on.
- If a freelance developer creates a game concept before he joins a development company, DOESN’T tell the company about this and subsequently pitches the concept to them as a company idea then, if the game concept is taken forward, there is a risk that the developer may lose any IP rights he may have in the concept.
- The judge said game concepts discussed by a game developer with his employer are unlikely to be confidential as between the two of them, so a developer could not generally prevent his employer from for example pitching the concept to publishers (unless there is some express agreement to the contrary).
- Review carefully the provisions of your employment agreements which deal with ownership of IP rights, because they could be important if there is subsequently a dispute between the developer and the development company over who owns the IP rights in a game concept.
- Pick your legal battles carefully. Litigation is costly, lengthy and risky, as this case demonstrates. A little advice early on from experienced litigation lawyers about your prospects of success and the legal cost/benefit analysis can save a lot of time, money and stress down the line.
In around 1998 a then-freelance developer, Stuart Burrows, developed the concept for a game which came to be known as “Tracktrix”, described in Court papers as follows: “Traktrix’s gameplay is very simple: get the ball from one side of an environment to another and enter the “Finish Area” within a time limit. The player achieves this by laying a track in front of the ball as it progresses“. Burrows himself desribed it as “ ‘Marble Madness meets Tetris/Wetrix and a Scalectric track’ and ‘Super Monkey ball meets Tetris’ “.
Traktrix and Train Trax
Burrows later joined CiRCLE Studios as a senior games developer, but did not did not disclose to CiRCLE that he had already come up with the Tracktrix concept. He copied parts of his original work on Tracktrix in order to pitch a CiRCLE projet which was similar to Tracktrix, again without explaining that he had come up with Tracktrix before joining CiRCLE. CiRCLE then took the concept to publishers and, following the advice of Sir Ian Livingstone of Eidos, further developed it into a game concept known as “Train Trax”.
But ultimately no one was willing to pick up Train Trax. CiRCLE later went into administration in 2007. However, CiRCLE boss Adrian Smith and industry veteran Martin Carr formed another games development company, Crush Digital Media, which bought up some of the now-bust CiRCLE’s IP – including Train Trax. Crush then hired Burrows to work on Train Trax further and tried again to get publishers interested in, again without success unfortunately.
It seems that Burrows later began to argue that CiRCLE and Crush had infringed his copyright in Traktrix, and had breached confidence, by seeking to develop and market Train Trax. Lawyers were involved and the case went all the way to trial in 2009, despite Crush going the way of CiRCLE and entering administration in early 2009.
The High Court judgment
In a judgment published last week, Mr Justice Norris ruled that CiRCLE and its boss Adrian Smith had not copied Burrows’ copyright works in developing Train Trax because they had not known there was anything to copy. As far as they knew, Burrows had invented the Traktrix concept (which became Train Trax) for the first time when he was a CiRCLE employee. The judge found that Burrows had created Traktrix before he had joined CiRCLE, had then copied his own work to create a similar concept for the company and this then became Train Trax. So it was Burrows himself, not anyone else, who had done the copying. That was the end of the copyright claim.
As for the breach of confidence claim, the judge decided that a developer pitching a game idea to his employer ordinarily was not confidential as between the two of them. He said: “Mr Burrows was employed as a senior games designer by Circle. It was his job to come up with ideas. If he came up with an idea and shared it with his employer he was doing what he was paid to do: the disclosure would not be in circumstances importing any duty of confidence owed by the employer to the employee.”
Thoughts
The judge was pretty clear the case should never have got to trial (he referred to “the regrettable fact that the action reached trial at all“). That said, the legal issues in the case were fairly clear cut and he did not have difficulty in ruling in Smith and Crush’s favour.
Still, to my mind there were no real winners here. Yes, the case established that effectively Crush still had the rights to Train Trax but no one wanted to buy it anyway, the game was never actually developed and Crush went into administration in early 2009 anyway. As for Burrows, he was left emptyhanded and probably in fact received a substantial legal costs order against him (though it is always possible he may try to appeal). Not a great result.
Follow us at www.twitter.com/gamerlaw!
[Image credit: Mike Reeve http://en.wikipedia.org/wiki/File:Royal-courts-of-justice.jpg]
Having looked carefully though this case, a few points appear to have been overlooked and some elements don't quite add up.
Looking through the judgement and the reams of documentary evidence, Mr Burrows appears to have been the victim of some poor legal representation, which was simply followed through by the judge.
Mr Burrows' barrister appears to come under fire from the outset. Justice Norris takes issue with the way the claim has been presented, and the barrister seems to be putting forward an entirely different argument. Annoying the judge is not going to help win your claim. If the core argument has been muddied, there is little hope of success with any other points.
A key point has been made in regards to Mr Burrows' employers being unaware that the concept was his. It is unclear how this assumption could be made, as there are dozens of quite detailed design documents, clearly marked with the copyright notice with his name and the date. How did they miss them? The copyright notice should provided enough protection. If it didn't, then what is the point of the copyright notice?
It is difficult to believe that Mr Burrows, having gone to the trouble of putting copyright notices on all of his work, suddenly decided to present documentation without them.
Unfortunately for Mr Burrows, Justice Norris appears to have in explicably ignored his substantive documentary evidence; instead prefering to cite in favour of a document referenced by the defendant. These 'rough notes' do not appear to exist.
Also odd is that it is assumed, that Mr Burrows would prefer to present 'rough notes' over a well laid out, fully fledged design. All the evidence shows detailed design documentation, most several pages long, predating his employment.
Another oddity in this case is that a director of a company is not considered to be a 'guiding mind'. How could Mr Smith be regarded as anything else? Within the evidence there are emails from Mr Smith demanding a not insubstantial $380k for development costs.(This could have been a factor in the game not selling.) Smith clearly is the 'guiding mind' if is able to sign off on a prospective deal.
It appears that Mr Burrows has been particularly unlucky in his claim, and the case highlights the risks of litigation for all concerned.
If they would have been applied for a patent this might would have been not the case. Patent application protects one to copy their invention.