[EaWModLauncher] v1.1 - Release - First ModLauncher for STEAM EaW & FoC

[BertHunter]

[edit] *updated to 1.1

I recently released a new mod launcher for 'Star Wars: Empire at War' and 'Star Wars: Empire at War: Forces of Corruption'.

Screenshot:
http://media.moddb.com/cache/images/downloads/1/85/84438/thumb_620x2000/1_eawmodlauncherEN.jpg


Features:

• Launches the Steam or Retail version of "Star Wars: Empire at War" or "Star Wars: Empire at War: Forces of Corruption" with or without mods.
  
  
• Lists all found modifactions at the main launcher page. (Steam & Retail)
  
  
• Temporarily moves all files found in a subfolder of a modification called "Data_main" to the game's DATA folder while playing this mod. (This was coded so that modded AIs or special custom maps do not interfere with other mods and the actual game folders stay clean.) (Steam & Retail)
  
  
• Supports easily switching between game languages by clicking on flag icons at the main launcher page. (Steam & Retail)
  
  
• Shows if a mod's language is not yet translated to the game's current language. (Steam & Retail)
  
  
• Language files backup. (Steam only)
  
  
• Opens the map editor, custom maps or savegame folders. (Steam & Retail)
  
  
• Supports passing of parameters to make your own custom shortcuts to mods without ever seeing the launcher GUI. (Steam & Retail)

Download
Star Wars: Empire at War - ModLauncher v1.1.0

[[FC] SwiftBlizz]

Originally posted by BertHunter:

ModLauncher: How does the Steam mod launch work?
- The easiest method I finally found is the following one (see also "IV Known Issues"):
Steam.exe is called, passing "-applaunch 32470" and "MODPATH=" as parameters. FoC requires "runm2.dat" to temporarily replace "runme.dat".

That's so nice, and at the same time so stupid on Steams part.

Do you have any idea yet about how runme.exe and runme2.exe fits into this?

[BertHunter]

'runme.exe' is called by steam each time you start the game. It reads '32470_install.vdf' & '32472_install.vdf' and writes the found entries into the registry, then it starts the game with the language and path-variable which are listed in 'runme.dat'. (same for runme2.exe and runm2.dat)
Sadly runme2.exe can't be manually executed to start FoC immediatly...
It's all a big mess and certainly not lucasarts' greates job of 'porting' a game for steam.

But at least with this launcher, a FoC mod start is just a click away^^

[BDK]

Argh sticky this already! The way steam is handling this expansion is beyond a joke.

Edit: This launcher actually works, good job and thanks!
Edit 2: Screenshot http://s20.postimg.org/uaitxgnlp/eow_launcher.jpg

[BertHunter]

I am glad you liked it!
I actually do have a 1.1 version lying around on my PC with a windowed option and some minor improvements, but never came around of uploading it.
I will try sending it to filefront - sadly it is still the only place for all the EmpireAtWar mods despite the fact that their server system is pretty messed up.

[BDK]

http://www.gamefront.com have some mods as well ( http://www.gamefront.com/?s=empire+at+war ). Make sure to submit it so it wont be deleted after 60 days =)

But yeah, awesome launcher!

[BertHunter]

I just submitted the 1.1 version of the file to modDB. Seemed to be a good place for a mod launcher.
Have fun playing Empire at War^^

[[FC] SwiftBlizz]

Neat! Thanks! :D

[Shinobus]

I can't get the mods to work at all s: The mod launcher finds them, but the mods don't seem to work, any help would be great please :)

[stalker_dolg_4.ogf]

Woah good job. I'm definitely going to try it out. :D

[BertHunter]

@tatchibanaukyo:
Basically the launcher sees all folders in your mods folder and tries to start a possible mod inside of it if it was installed correctly. Your mod folder should contain a 'ModName' folder and in it a 'Data' folder containing other folders like Art, Audio, Ressources, Scritpts, Text, XML, etc...
Should look something like this (--> "corruption\mods\mycoolnewmod\Data\XML").
You can tell me the mods name your trying to play, if the above is of no help for you.

@Hercules plays Star Wars!:
Your welcome^^

[Starbuck]

@berthunter

I tried to use your launcher and play with mods Absolute Chaos (v2.4 upgraded) and Alliance at War

However ... only EaW starts, and never FoC (that is unless I click on FoC icone, but that defeats the purpose of playing with mods)
worse, it then crashes at the main page of EaW

my mods are both installed separately in a Mods folder in FoC
Star Wars is installed in C:/Games (and not Program Filesx86)

when your launcher starts, it informs me that the registry needs to be changed, then it goes on EaW

http://imgur.com/Vr6iI8b


would you have any ideas on how to solve this conundrum ?


best regards

[BertHunter]

@Starbuck
Weird, I downloaded ACM2.4 and started it just fine with the launcher.

Judging from your provided image, you installed the mod correcly.

Does the RegistryChangeNotification show up with each start of the launcher?
If so please start the launcher with admin rights (right click, 'run as administrator')
and hit yes when asked to update the path values. This should do the trick.

[Starbuck]

thx for the reply BertHunter

even with admin rights, your launcher still ask me to confirm the registry psth
however, I think I know what the probkem was all along

those Mods .exe assume that the game is installed in c:/program files x86
.... so I reinstalled EaW + FoC in a "traditional" way, and moved the mods there

thus far, it works (though EaW is still buggy ... but since I dont use it;))

[BertHunter]

hmm, the launcher should be able to handle any game path on your PC. Did you move the game files after downloading them from steam by chance? Maybe Win10's registry is causing some problems as well, I will do some tests on a win10 laptop... Anyway, since it works for you now, have fun playing eaw^^

[BertHunter]

@[ARG] Dopeh
hmm, never heared about this one. The retail crash may happen because of the badly working securom disc protection. Especially on Win10 this can cause problems...
The steam version though should work fine... Have you tried launching steam.exe with a rightclick and choosing 'Run as Administrator', then rightclick on EaW, properties, local files and clicking "verify integrity of game cache..."? Afterwards the game should work correctly.

If not, you can only try to complety reinstall the game, update your graphic cards driver, update directX9 and try again...


Edit: Does your Windows user name contain different symbols than 'a-z' and '0-9' ? If so, try making a new user, call it EaW or someting and try playing the game from this user account. I recall this was a problem before while saving a game, but maybe this 'fix' will work in your case, too^^