Hey K__, here's a few pieces of information to assist you in your modding:
First of all, your logo is obviously based off a bitmap of the Xonotic logo. To make it look less like a hack job (unless that's the point of it), it's always better to work from source. The source of the logo can be found there:
http://git.xonotic.org/?p=xonotic/medias...f=gfx/logo . I think the font part is by Dokujisan. It might be hand-made.
Now, about the distribution of the mod... You've repackaged the entire game, but is this really necessary? As long as you only change things in the data directory (which is true most of the time), you can distribute your mod as a small pk3 to be put into the user's data directory to override the default files. Here's how it works:
By order of precedence, this is where the DarkPlaces engine searches for a file. (Note: the personal data dir is in My Documents or a similar user directory on Windows; the main data dir is the data directory from the installation directory)
- Personal data dir
- Last pk3/pk3dir in alphabetical order in the personal data dir
- Last pak in alphabetical order in the personal data dir
- Main data dir
- Last pk3/pk3dir in alphabetical order in the main data dir
- Last pak in alphabetical order in the main data dir
If an empty file is found in a pk3, the engine considers this filename to be absent from the entire hierarchy.
You can ignore the "pak" ones, we don't use that format. pk3 is a zip archive and pk3dir is a "virtual" pk3 which is just a directory with the usual contents of a pk3 file.
For example, if you want to override the background image of the luminos menu theme, you can create a pk3 file which contains the file gfx/menu/luminos/background.jpg. If you want to delete the gak model, you can create a pk3 file that contains the empty file models/player/gak.iqm.
So, put your changed files for your mod in zzz_trollnotic_060-v0r1.pk3 to make sure that it's loaded late enough to override xonotic-data201203??.pk3 even if it's placed in the main data dir. The 060-v0r1 is for versioning: you can bump it to v0r2 for minor changes, v1r1 for major changes, and bump 060-v5r7 for example to 070-v1r1 if Xonotic 0.7.0 gets released. This way, later versions come later in the alphabet and override previous versions.
Now you can release your mod as a pk3 containing only the files that are new or changed, instead of distributing an entire copy of the game. It also frees you from licensing complexity, since you only have to deal with the legality of the files that you distribute. Also, users can move the pk3 out of their data directory when they get tired of it and it all goes back to normal.
EDIT: it also makes it simpler for users to see what the mod changes. Why do you ask players to backup their data directory? Does it include changes in the gamecode as well?