-= Gametoast.com =-

So I was just minding my own business, working on a custom unit, right?

Right. So I set everything up, have my side all put together, and finally I'm ready to test. So I go, and munge it. Well look what happens to pop up once it finishes munginng:

ERROR[levelpack rcm.req]:Expecting bracket, but none was found.
File : munged\pc\rcm_inf_commando.lvl.req(1)...

ucft <--
ERROR[levelpack rcm.req]:Expecting bracket, but none was found.
File : munged\pc\rcm_inf_commando.lvl.req(1)...

ucft <--
[continuing]
2 Errors 0 Warnings

Obviously, rcm is the three-letter ID for my side. Supposedly there's something wrong with the REQ. I've looked it over at least a dozen times; there's absolutely NOTHING wrong with it. It's set up perfectly.

See for yourself:

ucft
{
REQN
{
"lvl"
"rcm_inf_commando"
}
}

ucft
{
REQN
{
"class"
"rcm_inf_commando"
}
}

I've used REQs from the assets as templates and just filled in my unit's name (rcm_inf_commando). But even doing that hasn't worked. I made an entirely new side and gave it a different name, but still no luck. I even created an entirely new map, and it still doesn't work. I even tried putting my unit into an already existing side I had, but still, the minute I so much as change the REQ, it won't work.

The map itself doesn't crash. But the unit just doesn't show up. It makes absolutely no sense. There's no reason why it shouldn't work, really.

Here's what I got in the error log, but it doesn't help at all:

Message Severity: 3
.\Source\LoadUtil.cpp(1010)
Data in C:\Program Files\LucasArts\Star Wars Battlefront II\GameData\AddOn\JTE\Data\_lvl_pc\SIDE\rcm.lvl is not a binary UCF file.

Message Severity: 3
.\Source\LoadUtil.cpp(829)
Unable to find level chunk reb_inf_commando in C:\Program Files\LucasArts\Star Wars Battlefront II\GameData\AddOn\JTE\Data\_lvl_pc\SIDE\rcm.lvl


Message Severity: 3
.\Source\LoadUtil.cpp(1019)
Unable to find level chunk in dc:SIDE\rcm.lvl

Not a binary UCF file, eh? What a load of bull. I freaking used REQ files from the assets, for Pete's sake.

This has me absolutely confused as to what's going on. There's nothing wrong with the side as far as I can see. The REQs are set up perfectly. The mod tools were working perfectly yesterday. There's no reason for this kind of crap. Sometimes modding this game really ticks me off.

Can someone help? Or at least give me any insight as to what may be causing my problem?

EDIT: Okay, I just realized that this is now happening with any custom side I try to munge, regardless of what map. I tried munging a side from a completely different test map from a long time ago that worked perfectly. And it gets the same exact error. I haven't even touched it. This is really starting to piss me off now. I might just have to reinstall the mod tools... again... for like, the third time, because of stupid stuff like this.

ucft
{
REQN
{
"class"
"rcm_inf_commando"
}
}

Double closing bracket. huh?

This is a stupid question, but you never know. Have you added the side to _BUILD/Sides?

The double closing bracket is supposed to be there.

And yes, I did add the side to the _BUILD/Sides folder.

I've done basically everything needed to make a new side. The only problem is, is that that side isn't working. Niether are any other ones. Even ones I've already made and used in maps. Something's wrong with the actual munge itself. I may need to reinstall the tools. I've had stupid problems like this before. The kind of problem that just comes about for absolutely no appearent reason, and there's absolutely no way to fix it other than reinstalling the tools. Of course, there's always the chance that reinstalling the tools won't work, and then I'll be really screwed. That's what worries me.

That error actually has nothing to do with your req files. When it builds sides it creates req files in the _BUILD/side/myside folder. The reason that req is not being built is that there is an error in your side itself.

1-Did you stop a munge? NEVER do that if you did. I dunno why Pandemic even put that in there, it screws stuff up. If so, clean and re-munge.
2-If you are munging the converted Republic Commando model it can take quite awhile to munge because it's like 3x the amount of polys it should be. Best to munge overnight if that's the case.

Nope, never stopped a munge. You've warned me about that before.

I'm actually just using a reskinned Rebel soldier. But I can't really test out his weapons and such if I can't get him to work. I really don't see why my side would have an error. I haven't done all that much to it. A few custom weapons, a custom skin, and that's pretty much it. Unless I screwed something up in an ODF or something and didn't realize it. In that case, it'll take a long time to find.

Though that still doesn't explain the fact that any custom side I try to munge, even ones that I know work, get the same exact error.

You're not alone. It doesn't help though. Yeah, it happened to me. NO idea at all why.

You do have the mod tools installed in a directory that has no spaces, correct?

hah! theres my question that I was about to psot answered! stopping a munge = bad, but why?

But I'm fairly certain everything is fine. I've basically tried everything, even using an REQ file from the assets. I don't see why it wouldn't work. Especially when trying to munge a side that I know already works, and I've used in the past. I get the same bracket error, even when I haven't touched the side at all. I don't see why that would happen. Maybe some key file somewhere got moved or overwritten somehow during the munge that may be affecting it?

Schizo -- if you're still having trouble I'll be on XFire tonight.

I actually HAD this happen the other day too Schizo! It was with one of the sides you helped me with (which are coming along nicely now). I was getting errors outta nowhere and couldn't find a problem in any of my files.

The problem with mine was the files themselves. For some reason my files weren't saving with timestamps. Check to make sure there's a date modified on all of your recently-edited files...even ones that have nothing to do with the error. Probably not what your issue is, but worth checking out.

Have you done a full clean and a remunge yet?

I fixed the problem. Turned out I made a stupid mistake while putting together my weapon ODF. The reb_weap_inf_command_pistol was calling for itself as the ordanance file. I also made a bunch of other little mistakes, but nothing as serious.