Killing Jedies
Moderator: Moderators
-
R2-D2
-
imp_strikeforce
-
imp_strikeforce
k i just downloaded the bfbuilder pro, and it sounds like that might render my tutorial obsolete.
i havnt tried it yet but it sounds like it does(or will) all the things automatiacally that you would otherwise have to do manually-like i would try to explain
maybe i could do it real fast right now (right now im re-installing bf cause whenever i try to get on most servers online it tells me i dont have the map :evil: )
i havnt tried it yet but it sounds like it does(or will) all the things automatiacally that you would otherwise have to do manually-like i would try to explain
maybe i could do it real fast right now (right now im re-installing bf cause whenever i try to get on most servers online it tells me i dont have the map :evil: )
-
imp_strikeforce
How to munge a SIDE file
ok here goes, this is the way to do it manually
1. pick the side file you want to create- i'll use the ALL (alliance) side as an example.
2. go to the BFBuilder/modid/_build_pc/ folder of your project.
in this folder you'll find a munge.bat file, open it with notepad (or any other text editor).
there will be a section in it that looks like this:
cd Sides
REM STARTSIDES
REM cd GAM
REM @call munge.bat
REM cd ..
REM ENDSIDES
cd ..
3. remove the REM from the lines (the REM tells the program to ignore the lines) and replace the GAM with the side you want to munge, in this case, ALL. it should look like this.
cd Sides
STARTSIDES
cd ALL
@call munge.bat
cd ..
ENDSIDES
cd ..
4. go to the BFBuilder/modid/_build_pc/Sides/ folder. there should be a folder called GAM there. rename it or copy and rename it to match your new side. (ALL in this case).
5. in your newly renamed/copied ALL folder you will find another munge.bat file. open it and anywhere it says GAM, replace it with ALL.
also in the BFBuilder/modid/_build_pc/Sides/ folder there will be a clean.bat file. open it, and anywhere it says GAM, replace it with ALL.
6. ok, so far you've enabled and configured it so you can munge your new SIDE file.
7. the directory where you will put the side files is Modid/Sides/ . there will be a folder called GAM(again-lol). rename it ALL. in that folder there are subfolders for the ODFs MSHs and REQ files (as well as a .req file that needs to correspond to your new side).
[see the shipped sides for more detail in this area, and to get a feel for where things go and such]
8. you can then copy all the shipped side files and modify the ones you want, or you can just stick your modified files in. (remember though that sometimes you will have to call for your modified file in the mission lua, otherwise the game will look at the original file and read from that)
9. then when you have modified as desired, you can munge, and it should munge you a brand spanking new SIDE file.
the point of this was really just to show ppl how to configure the stuff so that it will munge a side file, and get a basic idea of where/what you will work with when creating a modded side file.
a helpful tip, look at and use the shipped assets often, most of the time you can learn alot by seeing how the original assets were set up.
like i said, fred's bfbuider pro will prob render most of this obselete, but i thought i'd put it out anyway in case it could be of some help to ppl.
this is only my first shot at something like this, so
questions, comments, complaints and praise are all welcome
hope this has helped
1. pick the side file you want to create- i'll use the ALL (alliance) side as an example.
2. go to the BFBuilder/modid/_build_pc/ folder of your project.
in this folder you'll find a munge.bat file, open it with notepad (or any other text editor).
there will be a section in it that looks like this:
cd Sides
REM STARTSIDES
REM cd GAM
REM @call munge.bat
REM cd ..
REM ENDSIDES
cd ..
3. remove the REM from the lines (the REM tells the program to ignore the lines) and replace the GAM with the side you want to munge, in this case, ALL. it should look like this.
cd Sides
STARTSIDES
cd ALL
@call munge.bat
cd ..
ENDSIDES
cd ..
4. go to the BFBuilder/modid/_build_pc/Sides/ folder. there should be a folder called GAM there. rename it or copy and rename it to match your new side. (ALL in this case).
5. in your newly renamed/copied ALL folder you will find another munge.bat file. open it and anywhere it says GAM, replace it with ALL.
also in the BFBuilder/modid/_build_pc/Sides/ folder there will be a clean.bat file. open it, and anywhere it says GAM, replace it with ALL.
6. ok, so far you've enabled and configured it so you can munge your new SIDE file.
7. the directory where you will put the side files is Modid/Sides/ . there will be a folder called GAM(again-lol). rename it ALL. in that folder there are subfolders for the ODFs MSHs and REQ files (as well as a .req file that needs to correspond to your new side).
[see the shipped sides for more detail in this area, and to get a feel for where things go and such]
8. you can then copy all the shipped side files and modify the ones you want, or you can just stick your modified files in. (remember though that sometimes you will have to call for your modified file in the mission lua, otherwise the game will look at the original file and read from that)
9. then when you have modified as desired, you can munge, and it should munge you a brand spanking new SIDE file.
the point of this was really just to show ppl how to configure the stuff so that it will munge a side file, and get a basic idea of where/what you will work with when creating a modded side file.
a helpful tip, look at and use the shipped assets often, most of the time you can learn alot by seeing how the original assets were set up.
like i said, fred's bfbuider pro will prob render most of this obselete, but i thought i'd put it out anyway in case it could be of some help to ppl.
this is only my first shot at something like this, so
questions, comments, complaints and praise are all welcome
hope this has helped
-
imp_strikeforce
RE: How to munge a SIDE file
r2-d2, this is most likely yur problem. the game is looking at the original side file instead of you modded one. (if i understand correctly)imp_strikeforce wrote:(remember though that sometimes you will have to call for your modified file in the mission lua, otherwise the game will look at the original file and read from that)
i tested this out myself while i was writing the tutorial and it didn't work at first. so i modified mission lua like this
ReadDataFile("SIDE\\all.lvl",
"all_inf_basicdesert",
"all_inf_smuggler");
ReadDataFile("dc:SIDE\\all.lvl",
"all_inf_lukeskywalker");
i removed the line about luke from the original and added the lines highlighted in blue so that when the game looked for luke's stuff, it looked at the ALL.lvl file with my world, instead of the original.
so i remunged and got it to work then, and luke died when i shot him
-
rebel_scum
RE: How to munge a SIDE file
thats cool
-
imp_strikeforce
RE: How to munge a SIDE file
maybe just for fun i'll release a minimod which makes all jedis killable 
-
R2-D2
Re: RE: How to munge a SIDE file
Ok thanks, but one question, how do you make the original maps with jedies killable. (I did that but probably fred miss something.)imp_strikeforce wrote:r2-d2, this is most likely yur problem. the game is looking at the original side file instead of you modded one. (if i understand correctly)imp_strikeforce wrote:(remember though that sometimes you will have to call for your modified file in the mission lua, otherwise the game will look at the original file and read from that)
i tested this out myself while i was writing the tutorial and it didn't work at first. so i modified mission lua like this
ReadDataFile("SIDE\\all.lvl",
"all_inf_basicdesert",
"all_inf_smuggler");
ReadDataFile("dc:SIDE\\all.lvl",
"all_inf_lukeskywalker");
i removed the line about luke from the original and added the lines highlighted in blue so that when the game looked for luke's stuff, it looked at the ALL.lvl file with my world, instead of the original.
so i remunged and got it to work then, and luke died when i shot him
-
imp_strikeforce
RE: Re: RE: How to munge a SIDE file
you have to copy all the shipped alliance files into yur project directory, and change the jedi odfs you want to change, then you remunge the entire file and replace the original all.lvl file in the C:\Program Files\LucasArts\Star Wars Battlefront\GameData\Data\_LVL_PC\SIDE\ folder.
(make sure you back up the original first though!)
(make sure you back up the original first though!)
-
Qdin
- Old School Staff
- Posts: 2059
- Joined: Wed Feb 23, 2005 9:54 am
- Projects :: No Mod project currently.
- xbox live or psn: No gamertag set
I HAVE the same problem, but I can't fix it. What did YOU do??? please tell me... I haven't played Multiplayer for 2-4 weeks now=(right now im re-installing bf cause whenever i try to get on most servers online it tells me i dont have the map :evil: )
I JUST want to play MultiPlayer again, so PLEASE help me... ok? thanks...
C ya guys
-
imp_strikeforce
-
Stellcat
Sweet Davy Jones!!!
I try to munge and always get this ERROR!!
I know it's something simple but what!
PLZ ASSIST!!!!!!!!!
PS:There is more to the error but I did not want to clog the page
eap_walk_atst_cannon_chin.class for output. DOS reports:
No such file or directory
[continuing]
Could not open (null) for output. DOS reports:
Could not open munged\imp_weap_walk_atst_cannon_chin1_exp.class for output. DOS reports:
No such file or directory
Could not open munged\imp_weap_walk_atst_cannon_chin1_exp.class for output. DOS reports:
No such file or directory
[continuing]
Could not open (null) for output. DOS reports:
Could not open munged\imp_weap_walk_atst_cannon_chin1_ord.class for output. DOS reports:
No such file or directory
Could not open munged\imp_weap_walk_atst_cannon_chin1_ord.class for output. DOS reports:
No such file or directory
[continuing]
Could not open (null) for output. DOS reports:
Could not open munged\imp_weap_walk_atst_cannon_chin2.class for output. DOS reports:
No such file or directory
Could not open munged\imp_weap_walk_atst_cannon_chin2.class for output. DOS reports:
No such file or directory
[continuing]
Could not open (null) for output. DOS reports:
Could not open munged\imp_weap_walk_atst_cannon_chin2_exp.class for output. DOS reports:
No such file or directory
Could not open munged\imp_weap_walk_atst_cannon_chin2_exp.class for output. DOS reports:
No such file or directory
[continuing]
Could not open (null) for output. DOS reports:
Could not open munged\imp_weap_walk_atst_cannon_chin2_ord.class for output. DOS reports:
No such file or directory
Could not open munged\imp_weap_walk_atst_cannon_chin2_ord.class for output. DOS reports:
No such file or directory
[continuing]
Could not open (null) for output. DOS reports:
Could not open munged\imp_weap_walk_atst_cannon_head.class for output. DOS reports:
No such file or directory
Could not open munged\imp_weap_walk_atst_cannon_head.class for output. DOS reports:
No such file or directory
[continuing]
Could not open (null) for output. DOS reports:
Could not open munged\imp_weap_walk_atst_cannon_head_exp.class for output. DOS reports:
No such file or directory
Could not open munged\imp_weap_walk_atst_cannon_head_exp.class for output. DOS reports:
No such file or directory
[continuing]
Could not open (null) for output. DOS reports:
Could not open munged\imp_weap_walk_atst_cannon_head_ord.class for output. DOS reports:
No such file or directory
Could not open munged\imp_weap_walk_atst_cannon_head_ord.class for output. DOS reports:
No such file or directory
[continuing]
Could not open (null) for output. DOS reports:
Could not open munged\imp_weap_walk_atst_launcher.class for output. DOS reports:
No such file or directory
Could not open munged\imp_weap_walk_atst_launcher.class for output. DOS reports:
No such file or directory
[continuing]
Could not open (null) for output. DOS reports:
Could not open munged\imp_weap_walk_atst_launcher_exp.class for output. DOS reports:
No such file or directory
Could not open munged\imp_weap_walk_atst_launcher_exp.class for output. DOS reports:
No such file or directory
[continuing]
Could not open (null) for output. DOS reports:
Could not open munged\imp_weap_walk_atst_launcher_ord.class for output. DOS reports:
No such file or directory
Could not open munged\imp_weap_walk_atst_launcher_ord.class for output. DOS reports:
Also this error
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_sprite_atatpilot.sprite
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_sprite_atatpilot.sprite.req
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_sprite_officer.sprite
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_sprite_officer.sprite.req
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_sprite_scout.sprite
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_sprite_scout.sprite.req
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_sprite_stormtrooper.sprite
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_sprite_stormtrooper.sprite.req
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_sprite_stormtroopersnow.sprite
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_sprite_stormtroopersnow.sprite.req
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_sprite_tiepilot.sprite
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_sprite_tiepilot.sprite.req
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_walk_atat.zaabin
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_walk_atat.zafbin
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_walk_atat1.zaabin
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_walk_atat1.zafbin
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_walk_atst.zaabin
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_walk_atst.zafbin
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\rep_hover_fightertank.zaabin
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\rep_hover_fightertank.zafbin
The system cannot find the path specified.
0 file(s) copied.
F:\Battle\BFBuilder\Datadt\_BUILD_PC\Sides\IMP>del Mungelog.txt
Could Not Find F:\Battle\BFBuilder\Datadt\_BUILD_PC\Sides\IMP\Mungelog.txt
F:\Battle\BFBuilder\Datadt\_BUILD_PC\Sides\IMP>odfmunge -sourcedir ..\..\..\Side
s\Imp -platformdir ..\..\..\_source_pc\Sides\Imp -platform pc -inputfile !*.odf
-outputdir munged\ -checkdate -continue
I try to munge and always get this ERROR!!
I know it's something simple but what!
PLZ ASSIST!!!!!!!!!
PS:There is more to the error but I did not want to clog the page
eap_walk_atst_cannon_chin.class for output. DOS reports:
No such file or directory
[continuing]
Could not open (null) for output. DOS reports:
Could not open munged\imp_weap_walk_atst_cannon_chin1_exp.class for output. DOS reports:
No such file or directory
Could not open munged\imp_weap_walk_atst_cannon_chin1_exp.class for output. DOS reports:
No such file or directory
[continuing]
Could not open (null) for output. DOS reports:
Could not open munged\imp_weap_walk_atst_cannon_chin1_ord.class for output. DOS reports:
No such file or directory
Could not open munged\imp_weap_walk_atst_cannon_chin1_ord.class for output. DOS reports:
No such file or directory
[continuing]
Could not open (null) for output. DOS reports:
Could not open munged\imp_weap_walk_atst_cannon_chin2.class for output. DOS reports:
No such file or directory
Could not open munged\imp_weap_walk_atst_cannon_chin2.class for output. DOS reports:
No such file or directory
[continuing]
Could not open (null) for output. DOS reports:
Could not open munged\imp_weap_walk_atst_cannon_chin2_exp.class for output. DOS reports:
No such file or directory
Could not open munged\imp_weap_walk_atst_cannon_chin2_exp.class for output. DOS reports:
No such file or directory
[continuing]
Could not open (null) for output. DOS reports:
Could not open munged\imp_weap_walk_atst_cannon_chin2_ord.class for output. DOS reports:
No such file or directory
Could not open munged\imp_weap_walk_atst_cannon_chin2_ord.class for output. DOS reports:
No such file or directory
[continuing]
Could not open (null) for output. DOS reports:
Could not open munged\imp_weap_walk_atst_cannon_head.class for output. DOS reports:
No such file or directory
Could not open munged\imp_weap_walk_atst_cannon_head.class for output. DOS reports:
No such file or directory
[continuing]
Could not open (null) for output. DOS reports:
Could not open munged\imp_weap_walk_atst_cannon_head_exp.class for output. DOS reports:
No such file or directory
Could not open munged\imp_weap_walk_atst_cannon_head_exp.class for output. DOS reports:
No such file or directory
[continuing]
Could not open (null) for output. DOS reports:
Could not open munged\imp_weap_walk_atst_cannon_head_ord.class for output. DOS reports:
No such file or directory
Could not open munged\imp_weap_walk_atst_cannon_head_ord.class for output. DOS reports:
No such file or directory
[continuing]
Could not open (null) for output. DOS reports:
Could not open munged\imp_weap_walk_atst_launcher.class for output. DOS reports:
No such file or directory
Could not open munged\imp_weap_walk_atst_launcher.class for output. DOS reports:
No such file or directory
[continuing]
Could not open (null) for output. DOS reports:
Could not open munged\imp_weap_walk_atst_launcher_exp.class for output. DOS reports:
No such file or directory
Could not open munged\imp_weap_walk_atst_launcher_exp.class for output. DOS reports:
No such file or directory
[continuing]
Could not open (null) for output. DOS reports:
Could not open munged\imp_weap_walk_atst_launcher_ord.class for output. DOS reports:
No such file or directory
Could not open munged\imp_weap_walk_atst_launcher_ord.class for output. DOS reports:
Also this error
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_sprite_atatpilot.sprite
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_sprite_atatpilot.sprite.req
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_sprite_officer.sprite
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_sprite_officer.sprite.req
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_sprite_scout.sprite
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_sprite_scout.sprite.req
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_sprite_stormtrooper.sprite
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_sprite_stormtrooper.sprite.req
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_sprite_stormtroopersnow.sprite
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_sprite_stormtroopersnow.sprite.req
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_sprite_tiepilot.sprite
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_sprite_tiepilot.sprite.req
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_walk_atat.zaabin
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_walk_atat.zafbin
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_walk_atat1.zaabin
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_walk_atat1.zafbin
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_walk_atst.zaabin
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\imp_walk_atst.zafbin
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\rep_hover_fightertank.zaabin
The system cannot find the path specified.
..\..\..\Sides\Imp\munged\rep_hover_fightertank.zafbin
The system cannot find the path specified.
0 file(s) copied.
F:\Battle\BFBuilder\Datadt\_BUILD_PC\Sides\IMP>del Mungelog.txt
Could Not Find F:\Battle\BFBuilder\Datadt\_BUILD_PC\Sides\IMP\Mungelog.txt
F:\Battle\BFBuilder\Datadt\_BUILD_PC\Sides\IMP>odfmunge -sourcedir ..\..\..\Side
s\Imp -platformdir ..\..\..\_source_pc\Sides\Imp -platform pc -inputfile !*.odf
-outputdir munged\ -checkdate -continue
-
Saturn_V
- Emperor's Hand
- Posts: 487
- Joined: Sun Dec 26, 2004 12:11 pm
- Projects :: No Mod project currently.
- xbox live or psn: No gamertag set
- Contact:
Does the munge actually fail to complete? And when you run SPTest does your BFront.log file say ? Does the level fail to start?
There are a lot of errors generated in the DOS window during the munge but not all of them affect the level being created.
Are you creating a custom side, or just adding assets from the shipped levels ?
If it's a custom side, have you copied all the assets that the units need (like weapon odfs, and the associated ordnance and explosion odfs) ?
There are a lot of errors generated in the DOS window during the munge but not all of them affect the level being created.
Are you creating a custom side, or just adding assets from the shipped levels ?
If it's a custom side, have you copied all the assets that the units need (like weapon odfs, and the associated ordnance and explosion odfs) ?
-
[SFI]Arthenik
How to get rid of "You do not have the map currently played":
1)Delete the Addon folder. Either that or move it somewhere else.
2)Then, reinstall your game.
3)Install the new (1.2) patch.
4)You can try turning your firewall off, but it really only helps when your post-game screen with either "Victory" or "we lost" or whatever freezes.
That should help.
1)Delete the Addon folder. Either that or move it somewhere else.
2)Then, reinstall your game.
3)Install the new (1.2) patch.
4)You can try turning your firewall off, but it really only helps when your post-game screen with either "Victory" or "we lost" or whatever freezes.
That should help.
-
Stellcat
-
Saturn_V
- Emperor's Hand
- Posts: 487
- Joined: Sun Dec 26, 2004 12:11 pm
- Projects :: No Mod project currently.
- xbox live or psn: No gamertag set
- Contact:
-
Stellcat
Ok here is preety much what I do.
(A day in Stellcats life)
Written by him
Lo de da de dah.
Hmmmmmmm I'll make a side today!
(Little birds start singing)
(Dog starts jumping)
OK happy day!
Ok let's see.
Mission lua...... what's that...Hmmmmmm I know it must be the lua file in the addons folder!
(Stupidly opens file)
Hmmmmm nope don't see any gams to chamge.
guess I'll skip that part.
Step 2
Changes all the gams to Imp because he is making Imp side.
Changes all the gams to imp in the BAT files.
La de dah de dah!!!
Step3
Basicly doe's everything in psychofreds tut.
Step 4...................................................
.......................
...............
It's MADNESS!!!!! MADNESS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
(Birds turn into dragons and start burning down my house)
(Dog becomes rabid and tears up my leg)
NNNNNNNNNNOOOOOOOOOO!!!!!!!!!!!!!!!
You have just spent a day in my life
As you can see I am in need of help.
(In more then one way)
(A day in Stellcats life)
Written by him
Lo de da de dah.
Hmmmmmmm I'll make a side today!
(Little birds start singing)
(Dog starts jumping)
OK happy day!
Ok let's see.
Mission lua...... what's that...Hmmmmmm I know it must be the lua file in the addons folder!
(Stupidly opens file)
Hmmmmm nope don't see any gams to chamge.
guess I'll skip that part.
Step 2
Changes all the gams to Imp because he is making Imp side.
Changes all the gams to imp in the BAT files.
La de dah de dah!!!
Step3
Basicly doe's everything in psychofreds tut.
Step 4...................................................
.......................
...............
It's MADNESS!!!!! MADNESS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
(Birds turn into dragons and start burning down my house)
(Dog becomes rabid and tears up my leg)
NNNNNNNNNNOOOOOOOOOO!!!!!!!!!!!!!!!
You have just spent a day in my life
As you can see I am in need of help.
(In more then one way)
