What changed
0 fixes0 additions1 change2 removals
removedA resolution has finally been reached. Everything remains true, including: 01. I received the DMCA request after its removal from Steam with no warning/contact from either Valve/Steam or any developer associated with Call of Duty nor anyone from Activision. 02. I never was provided specific examples of assets, or screenshots of what offended them - nor given the chance to rectify or remove any offensive content prior to having our game removed from sale. This took 72 hours, of which I was both unable to externally resolve the situation for fans/product, nor investigate internally. 03. We assumed which pieces of content based on what they self-labeled from their Call of Duty games as well as community-provided assets: http://i.imgur.com/8Qx1NI2.png http://i.imgur.com/IjS7dfO.png http://i.imgur.com/ZQeBNGs.png 04. I was informed by Steam that according to their policy, Activision had 10 business days (until mid-July) to act or do anything. If Steam didn't receive a copy of a legal complaint within 10 business days, then our game would be re-instated. We immediately offered to remove ANY offensive content (it wasn't specified) and this was NOT accepted.
removed( THE LARGER PICTURE )Not providing any specific information, both in the DMCA that brought the game down as well as in multiple instances of correspondence between both parties - is prevented any of us from finding a solution or to learn more about what was going on. This costed massive damages. All that being said, that is simply a minor inconvenience in the grand scheme of things given what I learned yesterday directly from Activision. I am now in complete compliance with their complaint and I am equally as mad. While I don't agree simply based on the evidence that you are all going on about, relating to our Auto Shotgun - I do see similarities in the sights/bolts, etc. I don't believe it was important enough to remedy immediately, affecting production on all ends to simply replace that one weapon when we could just do it later on. We acted under the pretense this was the only infraction/issue. This was not the case. Regardless, I understand that was a unique perspective and that many in the community and even on the team agreed for it to go. In the end, it WAS removed from the game and will be made public in the upcoming Version 1.5.5. Last night I received evidence directly from Activision regarding assets not even mentioned in public yet. Upon receiving this it became immediately apparent that blatant rips were made. While the artist offered to remake any assets at no cost, he has now been fired immediately upon learning this. This will slightly affect production and I will get into that later.
changed( WE ARE REMOTE )What most users don't understand is that we are a remote developer, we don't work side-by-side. Hiring and full-time development happens online in different time zones and different hours of the day. This can result in situations like this and we do are best to avoid them. What most users also don't understand is that I personally don't build these weapons. I am not a 3D artist, at all. I am responsible for anything from the business, to making the maps/worlds, and making sure the product comes together. What I am responsible for is hiring the individual responsible. And this is what concerns me the most: I cannot guarantee this will be prevented in the future. I don't get to play other games, I am working on this full-time. I would
ORION: Prelude changes
removedA resolution has finally been reached. Everything remains true, including: 01. I received the DMCA request after its removal from Steam with no warning/contact from either Valve/Steam or any developer associated with Call of Duty nor anyone from Activision. 02. I never was provided specific examples of assets, or screenshots of what offended them - nor given the chance to rectify or remove any offensive content prior to having our game removed from sale. This took 72 hours, of which I was both unable to externally resolve the situation for fans/product, nor investigate internally. 03. We assumed which pieces of content based on what they self-labeled from their Call of Duty games as well as community-provided assets: http://i.imgur.com/8Qx1NI2.png http://i.imgur.com/IjS7dfO.png http://i.imgur.com/ZQeBNGs.png 04. I was informed by Steam that according to their policy, Activision had 10 business days (until mid-July) to act or do anything. If Steam didn't receive a copy of a legal complaint within 10 business days, then our game would be re-instated. We immediately offered to remove ANY offensive content (it wasn't specified) and this was NOT accepted.
removedNot providing any specific information, both in the DMCA that brought the game down as well as in multiple instances of correspondence between both parties - is prevented any of us from finding a solution or to learn more about what was going on. This costed massive damages. All that being said, that is simply a minor inconvenience in the grand scheme of things given what I learned yesterday directly from Activision. I am now in complete compliance with their complaint and I am equally as mad. While I don't agree simply based on the evidence that you are all going on about, relating to our Auto Shotgun - I do see similarities in the sights/bolts, etc. I don't believe it was important enough to remedy immediately, affecting production on all ends to simply replace that one weapon when we could just do it later on. We acted under the pretense this was the only infraction/issue. This was not the case. Regardless, I understand that was a unique perspective and that many in the community and even on the team agreed for it to go. In the end, it WAS removed from the game and will be made public in the upcoming Version 1.5.5. Last night I received evidence directly from Activision regarding assets not even mentioned in public yet. Upon receiving this it became immediately apparent that blatant rips were made. While the artist offered to remake any assets at no cost, he has now been fired immediately upon learning this. This will slightly affect production and I will get into that later.
changedWhat most users don't understand is that we are a remote developer, we don't work side-by-side. Hiring and full-time development happens online in different time zones and different hours of the day. This can result in situations like this and we do are best to avoid them. What most users also don't understand is that I personally don't build these weapons. I am not a 3D artist, at all. I am responsible for anything from the business, to making the maps/worlds, and making sure the product comes together. What I am responsible for is hiring the individual responsible. And this is what concerns me the most: I cannot guarantee this will be prevented in the future. I don't get to play other games, I am working on this full-time. I would
A resolution has finally been reached. Everything remains true, including:
- I received the DMCA request after its removal from Steam with no warning/contact from either Valve/Steam or any developer associated with Call of Duty nor anyone from Activision.
- I never was provided specific examples of assets, or screenshots of what offended them - nor given the chance to rectify or remove any offensive content prior to having our game removed from sale. This took 72 hours, of which I was both unable to externally resolve the situation for fans/product, nor investigate internally.
- We assumed which pieces of content based on what they self-labeled from their Call of Duty games as well as community-provided assets: http://i.imgur.com/8Qx1NI2.png http://i.imgur.com/IjS7dfO.png http://i.imgur.com/ZQeBNGs.png
- I was informed by Steam that according to their policy, Activision had 10 business days (until mid-July) to act or do anything. If Steam didn't receive a copy of a legal complaint within 10 business days, then our game would be re-instated. We immediately offered to remove ANY offensive content (it wasn't specified) and this was NOT accepted.
( THE LARGER PICTURE )
Not providing any specific information, both in the DMCA that brought the game down as well as in multiple instances of correspondence between both parties - is prevented any of us from finding a solution or to learn more about what was going on. This costed massive damages. All that being said, that is simply a minor inconvenience in the grand scheme of things given what I learned yesterday directly from Activision. I am now in complete compliance with their complaint and I am equally as mad. While I don't agree simply based on the evidence that you are all going on about, relating to our Auto Shotgun - I do see similarities in the sights/bolts, etc. I don't believe it was important enough to remedy immediately, affecting production on all ends to simply replace that one weapon when we could just do it later on. We acted under the pretense this was the only infraction/issue. This was not the case. Regardless, I understand that was a unique perspective and that many in the community and even on the team agreed for it to go. In the end, it WAS removed from the game and will be made public in the upcoming Version 1.5.5. Last night I received evidence directly from Activision regarding assets not even mentioned in public yet. Upon receiving this it became immediately apparent that blatant rips were made. While the artist offered to remake any assets at no cost, he has now been fired immediately upon learning this. This will slightly affect production and I will get into that later.
( WE ARE REMOTE )
What most users don't understand is that we are a remote developer, we don't work side-by-side. Hiring and full-time development happens online in different time zones and different hours of the day. This can result in situations like this and we do are best to avoid them. What most users also don't understand is that I personally don't build these weapons. I am not a 3D artist, at all. I am responsible for anything from the business, to making the maps/worlds, and making sure the product comes together. What I am responsible for is hiring the individual responsible. And this is what concerns me the most: I cannot guarantee this will be prevented in the future. I don't get to play other games, I am working on this full-time. I would
