1 reply to this topic

[iBud]

Aloha everyone,

I have a late 2008 MacBook Pro and a late 2009 iMac 27", both of which are running Call of Duty 4. While it's a great game, I have a question about the startup parameters of some of the mods. For example, I have Frontlines, which includes several new game types, but only if I can use their startup parameters.  On a Windows box, you have a shortcut to an executable, and the Property sheet includes an entry for "target".  After the path to, and name of, the executable, the startup paramets are entered - something like "+set fs_game Mods/frontlines +exec frontlines.cfg" (without the quote marks, of course).  

I tried that on my Macs, albeit having to provide the full path to the executable - different from the path to the Mods folder.  I made a huge terminal command from three different ones (first the path to the executable, then cd to the parent directory of the Mods folder, then the +set ... .cfg statement), separating them with semi-colons.  Everything went well with the exception of the third command.  The response in the terminal window was "+set command not found" or something close to that.  In other words, terminal was telling me that it didn't know what to do with the startup parameters given for the mod.  Of course, instructions for the mod were tailored to Windows users, as they are by far the majority of those using this mod.

I have been attempting to determine a way to get the Mac to use these parameters, but to no avail.  I would like to request information that anyone may have on how to do this, or if I'm simpliy wasting my time on this.  Any and all responses are greatly appreciated.

[UmarOMC1]

Create a text file with those parameters in it called AutoExec.cfg and place it in .../Call of Duty 4/Call of Duty 4 Data/players/profiles/yourprofile/

Let us know if it works...