It is currently Fri Apr 19, 2024 8:47 pm
It may sound silly, but regularly mail yourself copies of the mod, your assets and code. Seal them in an envelope, mail it to yourself - postmarks contain dates - and don't open them. Archive them in a filing cabinet, so if a situation ever arises where you need proof of ownership, you'll have dated proof.
I’ve heard about a “poor man’s copyright.” What is it?
The practice of sending a copy of your own work to yourself is sometimes called a “poor man’s copyright.” There is no provision in the copyright law regarding any such type of protection, and it is not a substitute for registration.
There is no government registration system for copyright protection in Australia. You do not need to publish your work, put a copyright notice on it, or to do anything else to be covered by copyright — the protection is free and automatic. There are no forms to fill in, and there are no fees to be paid. You do not have to lodge your work with a government agency or anywhere else.
If there's a dispute about who created something protected by copyright it may need to be resolved by a court. A court would look at all the relevant evidence. The most important evidence would usually be oral evidence from the creator and from people who saw the material being created or who saw early copies. Other evidence may include drafts of the work.
Such cases are, however, extremely rare.
There are a number of reasons for this. First, someone who goes to court claiming they own copyright when they don't runs very large financial risks, as they might have to pay not only compensation but also both their own and the other side's legal costs. Second, if someone falsely claims in court that they have created a copyright work, they risk perjury charges (a criminal charge for lying to the court). Third, there are provisions in the Copyright Act which allow people who have been groundlessly threatened with copyright infringement to take action against the person making the threat.
Lord Ned wrote:With the entire "Mailing your stuff to you" thing -- What is it trying to prove, that you had the code?
In my honest opinion, I think the BEST way to have any security is to keep things like this:
Mappers only get the .VMF's
Coder(No Plural) only get's the Source
Material Artists only have the VMT/VTF's etc.
Modelers only have the model files, and the related materials for them.
Now obviously the mappers can't map without the VMT/VTF and test in game, so you build the mod, send him the Client.DLL, and Header.DLL, and then send him materials. Materials are less of a problem (IMO) then models or code.
This way everyone has PARTS of the mod, but not the entire thing (Except for the Leader) and there's less issues of taking it and running.
The only problem with that is if your Leader runs off, but that should never happen.
Inveramsay wrote:Lord Ned wrote:With the entire "Mailing your stuff to you" thing -- What is it trying to prove, that you had the code?
In my honest opinion, I think the BEST way to have any security is to keep things like this:
Mappers only get the .VMF's
Coder(No Plural) only get's the Source
Material Artists only have the VMT/VTF's etc.
Modelers only have the model files, and the related materials for them.
Now obviously the mappers can't map without the VMT/VTF and test in game, so you build the mod, send him the Client.DLL, and Header.DLL, and then send him materials. Materials are less of a problem (IMO) then models or code.
This way everyone has PARTS of the mod, but not the entire thing (Except for the Leader) and there's less issues of taking it and running.
The only problem with that is if your Leader runs off, but that should never happen.
This I think is a good way of A) Creating deep mistrust B) Creating massive bottlenecks.
Users browsing this forum: No registered users