-
Notifications
You must be signed in to change notification settings - Fork 1
Console setup
The included batch files (at your _BUILD/ folder) are already setup to build for PC, Xbox and PS2;
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
You'll get a few errors complaining about some missing programs.
Use this batch file to get those programs in place (copy to run at your data__BUILD directory):
https://github.com/BAD-AL/SWBF2_Xbox_mod_effort/blob/master/xbox_ps2_setup.bat
For PC mods that go into the addon folder, it wasn't necessary to munge shell.lvl because the system is setup to add mods that are present there. XBOX works like that too and some content was delivered that way from Pandemic. But it's signed content and anything you put in the Xbox's addon folder that isn't signed properly will get blown away.
So, we need to modify shell.lvl to get new levels to show up in the selection list (missionlist.lua). The mod tools do not (by default) set you up to munge the shell.lvl file. But the shell files are included in the mod tools.
Copy the 'BF2_ModTools\data\Shell' folder to 'data_ABC\'.
Now when you munge, the typical "missing shell.req" error will be gone from the munge log.
More to come...
- Developing a SWBFII DLC package
-
Notes
- SWBFII Lua Environment
- common.lvl notes
- PSP notes
- PPSSPP notes
- Console world memory notes
- Shipped world sizes
- Sides memory notes
- Sound File analysis
- Sound file Notes
- Console memory adjustments
- Important Links
- Productivity Tips
- Useful Debugging Functions
- BF1 Notes
- UnleashX Menu Notes
- Video Conversion Notes