Copyright violations - the big and dangerous weapon
Posted: 5 Aug 2014, 20:15
Hi everyone, I have some major news to share in relation to this project's progress.
I paid a visit to some lawyers today, and received some suggestions on protecting our project's legitimacy.
Like in a lot of cases, using copyright content is a risk, our case is no exception. We currently are seemingly in the safe zone, but I plan to do some reorganization to address some of the holes before our first release. This should (hopefully) ensure that we will be just fine.
1) I plan to remove any Nintendo like graphics from the site's design, and replace them with other graphics. Either preferably under an open license like the CC, (Creative Commons) or I'll draw them myself.
2) The main forum theme is planned to receive an overhaul, including the replacement of any copyright forum icons to my own custom icons. All Mario styled icons will be saved in the "SMBX section specific style".
3) It's necessary that we have a non-copyright graphic pack for replacing SMBX's content without any issues before the release. I plan to use Talkhaus's content pack for our first few projects. But even they don't have all the copyright graphics replaced, which means it will be necessary for us to replace them.
4) My own OPL3 Chip SFX pack could be the first default sound pack for the first few games based on our engine.
5) Users creating their game projects with our engine must use their own originally made content or ensure it's licensed under something like the Creative Commons, I.e. users should be free to use anything, from the music & sounds, to the graphics.
6) We should put SMBX's graphics pack on the SMBX community site and must not have them on the our server.
7) When this project begins to finally pick up more popularity, I'll have to change the SMBX forum section to private, which will be visible only to special group members, like "Mario fan" and others.
I would like to once again make my point clear, that it's very important to not have any copyright content in this project.
Please understand this, as we clearly don't want to repeat Redigit's mistake
I paid a visit to some lawyers today, and received some suggestions on protecting our project's legitimacy.
Like in a lot of cases, using copyright content is a risk, our case is no exception. We currently are seemingly in the safe zone, but I plan to do some reorganization to address some of the holes before our first release. This should (hopefully) ensure that we will be just fine.
1) I plan to remove any Nintendo like graphics from the site's design, and replace them with other graphics. Either preferably under an open license like the CC, (Creative Commons) or I'll draw them myself.
2) The main forum theme is planned to receive an overhaul, including the replacement of any copyright forum icons to my own custom icons. All Mario styled icons will be saved in the "SMBX section specific style".
3) It's necessary that we have a non-copyright graphic pack for replacing SMBX's content without any issues before the release. I plan to use Talkhaus's content pack for our first few projects. But even they don't have all the copyright graphics replaced, which means it will be necessary for us to replace them.
4) My own OPL3 Chip SFX pack could be the first default sound pack for the first few games based on our engine.
5) Users creating their game projects with our engine must use their own originally made content or ensure it's licensed under something like the Creative Commons, I.e. users should be free to use anything, from the music & sounds, to the graphics.
6) We should put SMBX's graphics pack on the SMBX community site and must not have them on the our server.
7) When this project begins to finally pick up more popularity, I'll have to change the SMBX forum section to private, which will be visible only to special group members, like "Mario fan" and others.
I would like to once again make my point clear, that it's very important to not have any copyright content in this project.
Please understand this, as we clearly don't want to repeat Redigit's mistake



