Name policy
The MIT licence covers Enshwick’s code. It does not cover the name Enshwick.
Who may build and ship the code?
Section titled “Who may build and ship the code?”Anyone may build, change and ship the code under the MIT licence. Keep the copyright and licence notice with every copy.
What is an official build?
Section titled “What is an official build?”An official build is the files of an enshwick.zip from the
releases page, unchanged. A
build you compiled yourself, or changed in any way, is not an official build.
The files of an official build carry a signature made with our key:
powrprof.dll.sig beside powrprof.dll, and mods/enshwick/enshwick.dll.sig
beside enshwick.dll. Enshwick names any other build unofficial in its log and
on the Mods screen.
Is my Enshwick an official build?
explains what that means.
Who may ship a build under the name Enshwick?
Section titled “Who may ship a build under the name Enshwick?”Anyone may bundle an official build under the name Enshwick. Copying its files
into your own archive is fine. Keep each .sig file beside the file it signs,
or Enshwick names your bundle unofficial.
What if your build is not an official build?
Section titled “What if your build is not an official build?”Then do one of these:
- Give it a name that does not call it Enshwick.
- Call it an unofficial build of Enshwick, and link the official download.
Why does the name matter?
Section titled “Why does the name matter?”Players ask us for help with the build they run. We can vouch only for a build we released. A clear name tells players where their build came from.
Who answers questions about the name?
Section titled “Who answers questions about the name?”Write to contact@enshwick.com.