I munge the map, unaware of its faults at the time. I open Battlefront 2, hoping my map will play like an innocent map, but then..everything starts to get dramatic, the load bar reaches the end, and then...! BAM! The map is revealed for the baddy it is...! It freezes BF2 and nearly outruns the Windows Task Manager! The Task Manager was finally able to put an end to the busted maps reign of freezing! Little did I know, that wasnt the only time the map was going to reveal itself for being a baddy....and the 1st time, it took the MungeLog down with it...!

In other words, MY MAP FREEZES.
As soon as it reaches the end of the load bar, it freezes.


BFront2Log:
No Severity 3's...what could be wrong...

Simple question, what was the last thing you changed? Also is there perhaps an error window behind the load screen? Try Alt-Tab to see if one pops up.
There no are sev 3's but there are some missing attach odf and missing effects error you should fix. Either by making sure the things that are being asked for are there of commenting out the lines in the odf if you don't want them.

I readded godrays, everything else missing was already there.

It still freezes, theres just 1 new error: Exceeded maximum number of godrays (0) is the only new error.

Assuming you are using godrays in your map do you have something like this in your .fx file in the world1 folder
This still may not be the cause of the crash but is required if you are going to use godrays

Alright. I copied fel1 FX file into my world1 so that should be covered now.

EDIT: Its still freezing. What do I do if it says there are things missing that are already in the worlds folder?

The only time I've ever had freezing errors were due to missing or bad fx. Go through and make sure you get every single effect working. If that's not the cause of the crash at least it'll narrow it down.

Well I just copied the fel1 FX file into my world 1 and put the other effects in but ok.

There's still a number of effects in that log, just make sure you got em all. It'll save you trouble later. Also be sure you have all the textures you need for a particular effect.

I copied everthing from FEL's effects folder into mine and it still freezes.

Right, but you've still got some missing effects in your log that don't have anything to do with the FEL folder.

Alright, I put the rep_walk_atte_exp with the busted atte so that files not missing anymore. No more files are missing except fungal patch. The only abnormal error is that missing fungal patch odf...its in the correct folder, and yet its still saying that the odf is missing.

I have in my mind the last 3 things that could be causing the freeze:
1. The fungal patch odf that the program doesnt seem to be able to read...
2. I placed rep laats vehicles as objects.
3. I tried editing a Bespin texture and it screwed up. (now it looks like a carpet with little rainbows inside and big black streaks every 7 feet)

And just as things for you to think about:
I used a rep commandcenter from rep sides as a cp, along with a droid dispenser.

Post another log.

Did you change any localization? If you did, did it complete it's save normally?
The first error (the core one) can be caused by a localization error but not always.
try doing a manual clean, or if nothing else delete the core.lvl from your maps directory in the addon folder

Did you get any errors during the munge?

I didnt do any localizing and I dunno if there were errors, I always go do something else while its munging and look at the mungelog when the process is done, and the mungelog wont come up anymore.

it could be the fx file
some months ago i edted a sky file and the map froze too, i couldnt save the map, even the terrainfile etc. were infected
(i copied the into another world and the same thing happened)

Still freezes.

Well, what have you done for the last 9 days to try to fix it?

What duck was going about. I just got rid of the FX file. And the sky file cant be messed up, I took the felucian sky and fx file and put them in my world folder and renamed them.

Just keep working backwards until it's fixed. That's why it's so incredibly important that you test often. And by often, I'm talking every 1/2 hour of work at the very most. That way if something happens you remember the last changes you made, and can get rid of them one by one until the map works again. At this point you may be out of luck unless you know all of the changes you made since the last time your map worked and work backwards to fix them.