hot  /  reviews  /  video  /  blogs  /  forum

Bungie ordered to return stock to fired composer Marty O’Donnell

Aug 19 // Steven Hansen    @dtoidsteven

Money fight!

In April, Bungie fired its longtime composer, Marty O'Donnell. O'Donnell, one of the remaining original Bungie employees, was responsible for the music in Halo and the upcoming Destiny. He claimed he was "terminated without cause." In his firing, he was stripped of his founders' shares in Bungie. They are likely worth a considerable sum.

O'Donnell signed a deal stating he would give up his unvested founders’ shares if he left Bungie voluntarily, but he was fired. A court arbitrator ruled Bungie has to return the founders' shares to O'Donnell, according to VentureBeat. The studio can still appeal.

Bungie lawyers argued that O'Donnell would be a, "bothersome presence at board meetings and in the company" if his shares were restored, but the arbitrator overruled them.

In a separate case, O’Donnell sued Bungie to recover unpaid wages related to overtime and other compensation. He was awarded $95,000.

Arbitrator orders Bungie to give fired music chief Marty O’Donnell his stock back (exclusive) [VentureBeat]


 BLOG A RESPONSE



Steven Hansen // Features Editor
 Follow Blog + disclosure dtoidsteven Tips
Steven watches anime & sports, buys meat out of trucks, dates a Muppet, and is only good at cooking. He stands before you bereft of solace and well on the road to perdition. (´^ω^) full profile | More staff profiles

Get more destructoid:   We're indie-run, blogging for the love of it, and our site will always be free. Optionally, you can support us and get: (1) Faster pages from our cloud server (3) Wide(r)screen (3) No big ads on Dtoid, Japanator, Tomopop, or Flixist (4) Auto contest entries, and (5) Dibs on betas & downloads. Try it out

Get comment replies by email.     settings



Unsavory comments? Please report harassment, spam, and hate speech to our comment moderators

Can't see comments? Anti-virus apps like Avast or some browser extensions can cause this. Easy fix: Add   [*].disqus.com   to your security software's whitelist.

advertisement:

805 PEOPLE ARE READING:



Back to Top