I couldn't decide where to put this thread: It's not a DOD problem and honestly it really belongs in the mapping forum as much as it belongs here, but I didn't want to double-post.....

I've been seeing lately too many threads on "I can't get it to work in both the custom mapping AND the custom model/skin forums. I personally don't like installers, but it's loking like I will need to resort to them in the future.

1) Which is better, really? Are both good to use?
www.nullsoft.com/free/nsis/
www.clickteam.com
Clickteam's seems easier to comprehend but has an advert at the end; is there an advantage to using Nullsoft NSIS?

2) Obviously, all installs are going to be different BECAUSE Source installs with the user's account name (ususally an e-mail address). What is the registry line I should be pointing the automatic installer to?

TIA,
Wile

Okay nix on the NSIS - I just LOOKED at it and got a headache.

So I'm working with the Clickteam install creator but cannot for the life of me get the dang thing to snatch the install directory from the registry! Somebody HELP me! :eek:

I use NSIS to make the installers for my stuff and yes, its tricky but powerful. I had a pre-made script for installing content for DoD 1.3 on Steam but haven't updated it for Source yet - although its pretty trivial todo. It detects the users Steam install folder automatically from the registry, etc.

Dang, I was hoping to get mort response :(

I know at least a couple people have used the clickteam install maker AND successfully gotten it to find teh install path fron the regisatry....

'Cmon guys, how'd you do it? Speak up!

I use the free version of ClickTeam's InstallCreator - I like it, very easy to use, looks nice too, make as many as you want - it just has a window at the end of the install advertising for clickteam - no biggy

When I get 15 minutes free I'll update the NSIS map installer script I wrote for Source. Its not a big deal to do and certainly more flexible and you can "brand" your installer yourself with custom graphics and stuff yourself.

I was just making one myself :)

I found a script for InnoSetup (http://www.innosetup.com/isinfo.php) made by Jan Albartus. (http://members.home.nl/albartus/issi/scripts/SourceForts-1.4.2-Setup-Resources.zip)

I have edited it here and there and so far I have an installer that will...



1. Has custom images inside it's window. (fairly standard item for installers)

2. Has a custom icon for dod:s. (again, a standard thing)

3. Has a readme on the second screen...or not. (most have this option as well)

4. Has an automatic search for the dod folder on the third screen... good for our "new to a file system" players ;)

5. Has a Uninstall option that appears in the add/remove Programs list (control panel) and in the Programs list... bloody good idea for update time when your custom whatever may not work because of new items added.



So far it all works great, I am trying to add a custom install section as well where you tick and un-tick items you don't want...say items in a big "pack".

I will post some links/examples when done.

The "auto find" of the dod folder is a feature that makes the added work of packing files this way... well worth the extra effort.

EDIT: Bahhh!

I got the uninstallers for two seperate custom installs (a hud and a crosshair) to show up in the same Start/Program group (for uninstalling).

But the one that is installed last is all that comes up in the Add/Remove list in the control panel.

Oh.... fudge :(

ROFL... now this is wacky... I am going nuts, all works now but...

Big files for a hud (http://www.dodbits.com/dodbitsdownloads/oppps_insane.JPG)

Oh dear.

For Clickteam:

And you will need the absolute latest version..

I got a beta release a few weeks ago, not sure if the version I use is out yet..


Root Key:
HKEY_CLASSES_ROOT

KEY:
Applications\hl2.exe\shell\open\command


This will require you to build in \dod\*.*

Works great.. I rebuild all Maps and host them on our site, and for TPG.

Thankyou!!

Originally posted by Dunn0
For Clickteam:

Root Key:
HKEY_CLASSES_ROOT

KEY:
Applications\hl2.exe\shell\open\command


This will require you to build in \dod\*.*

can someone tell me how to manage the things i put into clickteam creator, like what can i look at to understand how the registry works with click team creator, like with this

Originally posted by Dunn0
For Clickteam:

Root Key:
HKEY_CLASSES_ROOT

KEY:
Applications\hl2.exe\shell\open\command


This will require you to build in \dod\*.*

but the prob is, i wanted to do this with other apps and games, so how can i make it detect dir's with other apps.

Originally posted by mn9500
but the prob is, i wanted to do this with other apps and games, so how can i make it detect dir's with other apps. There are games other than DOD?

LOL :D


Basically it is trial and error.

Know what directory you want.

Then search for some keys you think may work..

Then try them in ClickTeam.

I didn't have any luck with clickteam and source games. It finds half life 1 mods automatically OK... but not Half life 2 mods.

So far I have made a few in INNO setup and NSIS with all types of graphics and options in them. They both find the users dod folder automatically.

In both I still cannot make the entry in the Add/Remove programs list (control panel) report the correct size of the install.

It, (the windows registry) always reports whatever custom content... as the dod folder size.

Anyone know of a fix? It's a small thing but very annoying :D

I have made many Source Map packs that detect your user folder with clickteam.

Use the key above..

Good Luck

Originally posted by Dunn0
For Clickteam:


And you will need the absolute latest version..

I got a beta release a few weeks ago, not sure if the version I use is out yet..

That's why mine won't work, I have the latest version from the site ...but you have a Beta :)

I get it to find the directory but it stuffs up the whole address by placing a... " ... in front of it :(

"c:\valve\steam\steamapps\*email_name_removed*\day of defeat source

The clickteam one is by far the simplest wizard, very easy to use and looks the same as the basic installers in INNO setup and NSIS.

Just that the current version seems to have a bug or two... I'll wait :)

Edit: my version is build 24.

That's exactly it.. The extra character at the beginning.

I made a forum post in there forum's regarding the issue, about 2 months ago.. Look for it, and contact the main person there..

They may send you the BETA..

It just wouldn't be right for me to do so..

If theres enough demand I'll seriously consider re-doing the "do it yourself Steam installer" tutorial that was on my site. Its based on NSIS as I like free/open source stuff.

I can help too if you like, I have a working script section (from the NSIS Wiki) that browses the registry and finds the dod folder.

I am still exploring the optional install section, ( are tricky) but have got the basic install, custom graphics and uninstall in the Add /Remove programs list.

Two problems to go, tick boxes un-ticked as standard in an optional install.

The size of the dod folder is reported as the size of the modification files in the Add /Remove programs list uninstall entry.

I use HM NIS EDIT (http://hmne.sourceforge.net/) to use the scripts, compile and run them.

I'll post what I have so far... soon.

NSIS with a GUI for installing Steam game mod files, from dod cross hairs, CS:S or other source game maps, models... would be nice.

Definitely a demand for that.

If a "community installer" was made it could place all the files in a program group (start menu) .... better than digging around the dod folder. One click and it's gone :)


EDIT: I made a small package with a quick step-by-step tutorial I made as I did one. Warning its loooong :D

It has info on proggies used and some examples too.

Download here. (http://www.dodbits.com/tutorials/NSIS_dods_stuff.zip)

The clickteam installer is easier... but cannot find the folder properly... yet... this one will.

My Clickteam Version.

This is the Pro version.

Version 2.0 Build #24

I can only imagine that yes, there IS a demand for something like this, given the trouble many have with installing custom skins. Keep in mind I thnk the average user is able to understand instructions like the ones included in my skinpacks and the ones including in eSkwaad's latest release; But if given teh preference I just would have made separate executable downloads to eliminate any confusion for newcoming users. I also think that if it were posted, and then made a sticky, there would be many more people showing intrest in the furture that simply have not made it to the forums in the past 3 wekks ;)

True True

The tutorial I wrote was REALLY step by step including sample scripts and diagrams so it was easy to use. The only reason I pulled it was because they changed the spec of the scripting language which meant it no longer worked with later version.

I have written an updated version that does multi-language, sub/partial installs, etc. I just haven't gotten around to writing it up.

Originally posted by Trp. Jed
The tutorial I wrote was REALLY step by step including sample scripts and diagrams so it was easy to use.

Good one, can't wait :D

until we can find an automatic installer that will hunt down the DOD:S registry tag (correctly), or in case you just don't like making .exe's here is a handy little graphic that anyone and everyone can add to their releases if they want to

http://usera.imagecave.com/WileECoyote/installation_route.jpg

i'm interested by the ".exe".
if someone have an idea...fast/easy and without scripts if possible i'm interested.
Oh and a tool which can use pics...not a old win98 style.

maybe i ask too much.
:D

I had a bash at a tutorial here. (http://www.dodbits.com/tutorials/DoDs_NSIS_Installer.html)

It's just makes a NSIS installer with standard graphics.

I have not done another section on how to skin the installer yet.

Also not done is a more advanced "Typical or Custom" install choice section.

But this one should work for someone who has a dod folder full of content. once you have gone through it a couple of times it doesn't take long at all. Reading the tut will take time :)

Can't wait for that clickteam one it sounds very nice :)

I have been using the Clickteam installer for more then two years now and only figure it out tonight readin this thread.

So I made a teamplate (never used one before) and this made it so easy. In two hour only I basically repackage all DODS maps hosted on the dod-federation website. They now all support the path as long as you make it work once. Then the path always come back right.

Making a template was very easy, I made it trought all my choice, image top and left, text to tell where to install, since the first time you use it you still need to provide the correct path for the dod directory wich is the master directory for content.

Then I save the template with file save as. Now I put anything I have to packkage always in the same folder that I empty after using it. So basically I now do all the following step:

1 Put content in my teamplate folder that represent the dod floder. click on my template link, need to change the title variable and the click the build button and give the exe name and I am finish.

Really easy now to package and don't have to go trought all the procedure anymore. Also I get the path as a + for all that will download in the future.

I could easly write a small tutorial on it.

Just made the tutorial, a little heavy on images (27).

http://www.dod-federation.com/forum/showthread.php?t=66

Have fun !

Tutorial is nice CoolHand but I still had problems with the registry settings.

I asked Yves in the Clickteam forums (http://www.clickteam.com/CTforum/showflat.php3?Cat=&Board=ut&Number=295904&page=0&view=collapsed&sb=5&o=&part=) if he could send me a pre-release version... that he did :)

I tried it and it works fine now, (one small problem) it's version 2.0 build 25.

I entered the registry settings as in your tutorial but the ... \dod\*.* in the subkey box did not work.

So I left it blank and put ... \dod\*.* in the address box in the Installation Directory section. That worked ok.

I still have to play with this some more but for a simple thing like maps or one item it's got to be the best to use :D


I found if you require a component section... NSIS may be a better option for more complex installer tasks.


Can't see a way to implement a "tickbox optional install" components selection screen in clickteam yet, but I will look further.

Need to see what else this great little installer can do ... or if it is just limited to a simple "one choice only" type installs.

work fine for me, not sure why you had to put it else where. Anyway I wrote this the night I found out how to do it and now I use my template so I don't have to go trough all of it :)

I read your thread but I have a older version (2.0 build #21) that do not have this bug ;)

Originally posted by CoolHand
I read your thread but I have a older version (2.0 build #21) that do not have this bug ;)

Good info to know :)

Must be just version 24 with this bug then, I'll dig up my old copy... somewhere I should have it.

Originally posted by INsane_dod
I asked Yves in the Clickteam forums (http://www.clickteam.com/CTforum/showflat.php3?Cat=&Board=ut&Number=295904&page=0&view=collapsed&sb=5&o=&part=) if he could send me a pre-release version... that he did :)
Same here. Sent me a version also. works fine.
Originally posted by INsane_dod

I entered the registry settings as in your tutorial but the ... \dod\*.* in the subkey box did not work.

So I left it blank and put ... \dod\*.* in the address box in the Installation Directory section. That worked ok.Once again, same here. I just make a folder called "installs" and then make a pseudo-DOD:s folder tree in it starting with the "dod" folder (i.e. dod\materials\models\player\german)
Originally posted by INsane_dod I found if you require a component section... NSIS may be a better option for more complex installer tasks. And this is why I still haven't given up on NSIS yet, because that is VERY handy for some installs. One day I'll have the time to fool around with your tutorial :)

I am still adding more to that tutorial, busy ATM, there are some features in HM NIS EDIT that are very cool. Automatically adding whole sections of script, that sort of thing.

Knowing how to make a new wizard template HM NIS EDIT would be nice.

The tutorial needs to expand to show more on how to alter the colors / graphics of the installer... and new skins.

Forever learning... it never stops.

just a test.

can some people test it for me?

WC_M1911A1_self-installing.zip (http://www.landofozz.net/wilee/WC_M1911A1_self-installing.zip)

Haven't had much time for skinning lately, but I thought I'd give this a quick test

worked fine for me!

Worked good, found the address... oh like the pistol too :D

The clickteam installer is by far the easiest to skin and install basic packages.

The amount of maps I have downloaded could benefit from this particular release/ method.

BTW CoolHand, I couldn't find my old version, also I didn't find a download of it :(

Oh well, they will release the new one soon I hope.

yeah it looks like FINALLY I have an installer that works with the Source file struture. I am in the process of converting all my skins to self-extracting and will be using this from now on as I have gotten too many questions about how to install custom skins :), although this ain't gonna happen overnight as I am busy

Originally posted by Dunn0
For Clickteam:

Root Key:
HKEY_CLASSES_ROOT
KEY:
Applications\hl2.exe\shell\open\command

This will require you to build in \dod\*.*

Here's a little more info:
This method DOES work (with the beta version) BUT -

I discovered quite by accident tonight a potential problem with it. The program extracts to THE LAST HL2 MOD YOU PLAYED. For example:

If the last game you played was DOD:S it will install to
C:\program files\.........\day of defeat source\

but if it was Counter-Strike it will instead install to
C:\program files\.........\counter-strike source\

or maybe the single player HL2 will cause it to install here
C:\program files\.........\half-life 2\

So this method, while technically does work, is still a bit buggy. I am mentally disabled when it comes to stuff like this. Is there any keys or commands that can be added to the install making program to force it to choose DODS directory? there has to be, but I know I won't figure it out before this year is up.

Please post ideas ;)

I had also had a problem with the script I was using for NSIS.

It would find the SteamApps folder OK.. but then hook on to the first folder listed alphabetically!

Now I use this script adapted from one on haircuts site, so it may be a bit of Jeds one and haircuts combined but it seems to work OK so far...

Steam folder finder script for dods (http://www.dodbits.com/tutorials/Insert_dod_autofind_section.txt)

Steam Folder Finder for CS:s (http://www.dodbits.com/tutorials/Insert_CS_autofind_section.txt)

When I use HM Edits Wizard I just put this in front (with $INSTDIR in the Applications Default directory) it works great, much better than the old one I had.

I will do another Tutorial soon for NSIS, Jed said he would do one in this thread ... I think he is very busy ATM :D

I have started a Tutorial for NSIS installers, there are four pages so far and more to come, the first page is here. (http://dodbits.com/index.php?option=com_content&task=view&id=42&Itemid=47)

It is work in progress but it seems to be OK so far.

Sections yet to be added are complex install options and control over tick boxes, basic templates for maps, models, how to make a custom header and wizard bitmap... and a troubleshooting guide/links/further reading.

Originally posted by INsane_dod
I have started a Tutorial for NSIS installers WOOT!

Originally posted by INsane_dod
I have started a Tutorial for NSIS installers, there are four pages so far and more to come, the first page is here. (http://dodbits.com/index.php?option=com_content&task=view&id=42&Itemid=47)

It is work in progress but it seems to be OK so far.

Sections yet to be added are complex install options and control over tick boxes, basic templates for maps, models, how to make a custom header and wizard bitmap... and a troubleshooting guide/links/further reading.

Looks good. Better than my old one! :D

Thanks guys :D
I will add more pages over the week-end.

For those who are still interested in the NSIS installer, the last page of the Tutorial has been added.

It's about my limit of NSIS at the moment, I will add more if I find anything else.

Five pages and it starts here. (http://dodbits.com/index.php?option=com_content&task=view&id=42&Itemid=47)

The last page added is for some custom scripts in the components page and some more info on adding code templates.

Did I say "the last page" !!!

There are always more things to find with NSIS, this time I had a look at the UltraModern User Interface (http://ultramodernui.sourceforge.net/index.php)

It's just a larger GUI that is handy if you want to fit more into the installer pages and you would like to do some custom graphics and colors.
It's very easy to do compared with a full-on Custom skin job.

The Tutorial page is here. (http://dodbits.com/index.php?option=com_content&task=view&id=63&Itemid=55)

Have Fun.

when I get time, I'm gonna be going over this a lot :)

thanks man!

I thought I'd show off my work with NSIS, it took about a week to re-learn and make this install script. Now it is a lean mean installin' machine script ;p

I'm not actually gonna give out the script source, I'm just gonna show off some shell installers. They don't contain any files except an uninstaller so it can be uninstalled.

Shell installers: DoD_Eagles_B3_SHELL (http://s91961834.onlinehome.us/dod/icons/DoD_Eagles_B3_SHELL.exe) (324KB)
Rommels Example_SHELL (http://s91961834.onlinehome.us/dod/icons/Rommels Example_SHELL.exe) (315KB)

The Eagles shell is an example of what map installers for my clan look like and the Rommel Example one is what custom stuff I release looks like.
I left the license and readme page off on the example, but they are there just not on.

Features of the installers: Writes a registry key that remembers the language you select, all follow on Rommel installers read this
Writes the uninstaller to the \installdir\uninstallers\ directory to keep clutter down
It looks hawt, I based the skin off of our forum theme.From the template only two things need to be changed and one created
The define section which contains the map/project name and stuff.
The sections which point to the files.
The one thing that needs to be created is the left image which has a map picture. I have it setup so the file is named (map name.bmp), this way the variable that changes that reads in the define section the map name and thus saving me form having to change the path manually every time.

HERE (http://img171.imageshack.us/img171/60/testyh0.png) is a image that shows all the areas that can be skinned. The Line green, blue, orange and white can only have their color changed.

Nice work :)

I agree, it is nice work!

Originally posted by Wile E Coyote
Here's a little more info:
This method DOES work (with the beta version) BUT -

I discovered quite by accident tonight a potential problem with it. The program extracts to THE LAST HL2 MOD YOU PLAYED. For example:

If the last game you played was DOD:S it will install to
C:\program files\.........\day of defeat source\

but if it was Counter-Strike it will instead install to
C:\program files\.........\counter-strike source\

or maybe the single player HL2 will cause it to install here
C:\program files\.........\half-life 2\

So this method, while technically does work, is still a bit buggy. I am mentally disabled when it comes to stuff like this. Is there any keys or commands that can be added to the install making program to force it to choose DODS directory? there has to be, but I know I won't figure it out before this year is up.

Please post ideas ;)

I might have found a solution.

First I noticed that there was a command " %sourcesdk% which refers to your sourcesdk dir duh, but with that you could do a "get # map(s) back", and go forward to dod/cstrike etc.

But because not everyone got the SDK installed I personally won't use it in my installer.

But I just found out another possible solution.

* Steamroot = HKEY_LOCAL_MACHINE\SOFTWARE\Valve\Steam
* Shortcut to dods = D:\Valve\Steam\Steam.exe -applaunch 300

So the steamroot should be the same for everyone.
Hm now typing this I just thought "applaunch 300" IS at least MY shortcut/ref to DODS but........how to make sure the installer understands where dod root dir is....hmm.

Anyways, I could just not post this message but I hope someone might find it usefull anyway ;)

EDIT:
Man do I feel stupid now.
Check this....the register line shows:

"d:\valve\steam\steamapps\<yourname>\day of defeat source\hl2.exe" "%1"

What about giving the command go back one folder and then go one down -> "dod/ccs/ etc ;)
So you will get
1)
"d:\valve\steam\steamapps\<yourname>\day of defeat source\hl2.exe" "%1"

(one folder back, I have no clue what you last loaded)

"d:\valve\steam\steamapps\<yourname>\hl2.exe" "%1"

(So to be sure after we got back to the "root" lets make sure we go to the folder we want to go, like <VARIABLE = DODS/CCS/etc.> )


"d:\valve\steam\steamapps\<yourname>\<VARIABLE>\hl2.exe" "%1"


Does this make sense? :P