Handy Polishing Tips After Packaging Your Final Build
This tutorial/advice assumes that you have just packaged the final build of your game via Unreal Frontend and
want to make your beautiful piece of artwork look really pro when you give it out to someone to play. Some of these points will require
that you package your game and then install your packaged game on your PC.
This is what we're going to cover:
- Changing the name of your EXE
- Changing the icon of your EXE
- Extras
- Creating a custom installer (Using NullSoft)
---------------------
CHANGE THE NAME OF YOUR EXE
Instead of keeping your game called UDK.exe, this is a very simple and effective tip to make your game look professional.
- Start off by installing your packaged build to your computer.
- Locate UDK.exe in your game's install folder (example: C:\MYGAME\Binaries\Win32).
- There will be 3 files here called UDK (an Application file), UDK (an MS-DOS file), and UDK.exe (an XML file).
- Rename all of these files to your game name. (example: MyGame (an Application file), MyGame (an MS-DOS file), and MyGame.exe (an XML file)).
- Repeat these steps in the C:\MYGAME\Binaries\Win64 folder if applicable.
---------------------
CHANGE THE ICON OF YOUR EXE
Wouldn't you rather have your customized logo stamped on your game's exe? Of course you would! The more places you can put your logo, the better!
Follow these simple steps to changing the icon of your game's exe.
Icon Changer 1.0.0.0 allows free icon changes. You can download it here: http://www.softpedia.com/progDownloa...ad-190309.html
- Again, you would start off by having an installed packaged build to your computer.
- Open the software, select your custom-made icon and open.
- Select your installed game's EXE in the newly opened window and hit Open. (example: C:\MYGAME\Binaries\Win32\MyGame)
- Hit Change Now. That's it!
---------------------
EXTRAS
REMOVE ANY LOG FILES
Ensure you remove any log files after testing out your installed build. If people playing your game has issues and sends you an old log file that actually
originated from you testing the game then things can get rather confusing.
---------------------
CHANGING YOUR GAME NAME IN THE WINDOWS BAR
This does not require you to have already packaged your game, this can be done in your working folder.
When running your game in windowed mode you will see Unreal Development Kit in the window's title bar, you can change this rather easily by
opening the following file:
- C:\UDK\UDK-2012-11\UDKGame\Config\DefaultEngineUDK.ini
- Find line 35 & 36 called GameName & GameNameShort.
- Change these to your actual game name. (example: GameName=MyGame, GameNameShort=MyGame)
---------------------
CREATING A CUSTOM INSTALLER (USING NULLSOFT)
It took me a while to get to grips with Nullsoft's script system though after I figured out a few functions it was great to see things working, and
Nullsoft really does work well. I will help you through a very simple method of using the Nullsoft custom installer tools so make sure you go
download them from here before we begin: http://nsis.sourceforge.net/Download
- Download and install NSIS (Nullsoft Scriptable Install System)
- Download this script file : HERE (Unzip It!) : and place it in your NSIS install folder here: C:\Program Files (x86)\NSIS\Contrib\zip2exe - BACKUP YOUR ORIGINAL FILE FIRST!
- Open the script file with NotePad and scroll to the bottom.
Here you will see where I customized this script for MyGame. Here you can edit what you need to for your game. Let's go through some areas together:
MAKE SURE YOU REPLACE EVERY INSTANCE OF 'COMPANYNAME' AND 'MyGame' WITH YOUR OWN IN EVERY PART OF THIS TUTORIAL!
==============
CREATE THE SHORTCUTS
Code:
Section "Create Shortcuts" SetShellVarContext all AccessControl::GrantOnFile "$INSTDIR" "(S-1-5-32-545)" "FullAccess" CreateShortCut "$SMPROGRAMS\COMPANYNAME\MyGame.lnk" "$INSTDIR\Binaries\Win32\MyGame.exe" CreateShortCut "$DESKTOP\MyGame.lnk" "$INSTDIR\Binaries\Win32\MyGame.exe" WriteUninstaller "$INSTDIR\uninstall.exe" WriteRegStr HKLM "Software\Microsoft\Windows\CurrentVersion\Uninstall\COMPANYNAME\MyGame" "DisplayName" "MyGame" WriteRegStr HKLM "Software\Microsoft\Windows\CurrentVersion\Uninstall\COMPANYNAME\MyGame" "UninstallString" "$INSTDIR\uninstall.exe" SectionEnd
This allows the installer full read and write commands, this is required.
Code:
SetShellVarContext all AccessControl::GrantOnFile "$INSTDIR" "(S-1-5-32-545)" "FullAccess"
The area below defines where we want to place shortcuts and where those shortcuts will direct to after the game has installed. So first we have it
creating a shortcut to the Start Menu > All Programs > Toxic Games folder and pointing that to the game's install directory and .exe. The second command
creates a shortcut on the desktop and directs to the game's install directory and .exe again.
Code:
CreateShortCut "$SMPROGRAMS\COMPANYNAME\MyGame.lnk" "$INSTDIR\Binaries\Win32\MyGame.exe" CreateShortCut "$DESKTOP\MyGame.lnk" "$INSTDIR\Binaries\Win32\MyGame.exe"
This writes the uninstaller.
Code:
WriteUninstaller "$INSTDIR\uninstall.exe"
This area writes the registry keys (though I don't think it's correct!).
Code:
WriteRegStr HKLM "Software\Microsoft\Windows\CurrentVersion\Uninstall\COMPANYNAME\MyGame" "DisplayName" "MyGame" WriteRegStr HKLM "Software\Microsoft\Windows\CurrentVersion\Uninstall\COMPANYNAME\MyGame" "UninstallString" "$INSTDIR\uninstall.exe"
==============
INSTALL PRE-REQUISITES
Code:
Section "Redistributable Prerequisites" SetShellVarContext all AccessControl::GrantOnFile "$INSTDIR" "(S-1-5-32-545)" "FullAccess" DetailPrint "Starting the Redistributable Prerequisites Setup..." ExecWait "$INSTDIR\Binaries\Redist\UE3Redist.exe" SectionEnd
==============
THE UNINSTALLER
Basically tell it what to uninstall.
Code:
Section "Uninstall" SetShellVarContext all Delete "$SMPROGRAMS\COMPANYNAME\MyGame\MyGame.lnk" Delete "$DESKTOP\MyGame.lnk" RMDir /r "$SMPROGRAMS\COMPANYNAME" RMDir /r "$INSTDIR" Delete $INSTDIR\uninstall.exe SectionEnd
=====================
ACCESS CONTROL PLUGIN:
NOTE: Here are the Full Access Control plugin files required for this script to compile successfully:
http://dl.dropboxusercontent.com/u/2...essControl.zip
- UnZip/RAR and place these files into your NSIS directory.
This plugin is required for the installer to gain full read/write access to the installation directory.
=====================
There are lots of documention and tutorials online for NSIS if you wanted to dig deeper into the installer, but what I've
outlined here for you is a pretty good starting point.
So now that we've quickly gone through the most basic areas for NSIS let's make the installer!
- To begin, ensure you have an installed packaged build of your game on your computer. (Package the game from Frontend, Install it on your computer)
- Make any of the above changes to the icon and exe etc.
- Locate your newly installed game, select the Binaries, Engine, UDKGame folders, right click and compress your installed game contents into a .ZIP.
- Open NSIS and click 'Installer based on ZIP file', select you game's .ZIP and wait for it to allocate the files.
- Specify the Installer Name.
- Specify the Default Folder (usually something like $PROGRAMFILES\COMPANYNAME\ to ensure it ties in with the scripts)
- Specify where you want the custom installer to be created.
- Hit Generate.
That's it!
I hope this will be helpful to some folks.
Thanks,
ZeJudge
Comment