Console setup

Console setup

The included batch files (at your _BUILD/ folder) are already setup to build for PC, Xbox and PS2;

To Build for Xbox:

C:\BF2_ModTools\data_ABC\_BUILD> munge.bat /PLATFORM XBOX

refer to the bottom of "data_ABC\_BUILD\munge.bat" for building specific .lvl files like common and shell

Errors you'll see at this point:

• Errors complaining about some missing programs ('XBOX_texturemunge', 'XBOX_modelmunge').
• And an error about a missing 'shell.req' (Because it was not intended that PC modders would rebuild the main shell )
• A bunch of 'soundflmunge.exe' errors (Because the source sounds weren't shipped with the modtools)
• An error about '...\hero' doesn't exist
• An error about your world not existing (because of the above errors)
• xbcp errors (because we don't have the xbox copy program that Pandemic did, we'll have to ftp our stuff)

Fix the console build issue

Use this batch file to get those programs in place (copy to run at your data_ABC\_BUILD directory):

https://github.com/BAD-AL/SWBF2_Xbox_mod_effort/blob/master/xbox_ps2_setup.bat

Deployment Package choice

1. DLC Package
   • Advantages
     • Code is basically the same as for a PC Addon (Except for alternative localization in the addme.script file)
     • In-game localization works just as it does on PC.
   • Disadvantages
     • XBOX is limited to ~61 DLC missions; 23 are already taken up with Pandemic DLC
2. Drop & Click Addon
   • Advantages
     • No known mission limit
     • Works on all console platforms
   • Disadvantages
     • In-game Localization not (currently) changeable
3. Roll your own mod/shell
   • Advantages
     • Total Control
   • Disadvantages
     • Lots of work, effort, learning required