-= Gametoast.com =-

i have been having this munge log error that has ruined at least 3 of my mods. it takes out the engineer, sniper, and the magnaguard from my cis side. i have no idea what it means by missing bracket but can someone help me with fixing this please.

here is those dreaded errors please help.

Well it's quite simple, there's a bracket missing somewhere in that file. Find and post that file here and someone might be able to find it for you.

@Dakota: When asking a question please try to use a question mark (?) with it.

sim-al2 wrote:Well it's quite simple, there's a bracket missing somewhere in that file.

Expecting bracket errors usually mean something other than a missing bracket the majority of the time.

@Dakota again: It would help if you provided the exact details on how you executed this mod of yours; it will help anyone looking over your problem help you. The same goes for any future problems you may post. Please keep this in mind.

AQT wrote: Expecting bracket errors usually mean something other than a missing bracket the majority of the time.

Oh... that's news to me... I've never really payed attention to the rest of the phrase when it had "bracket" in it.

I think what it comes down to is that something is wrong with your cis_inf_sniper and in the req while compling visual munge sees "{" but then your cis_inf_sniper is bad and it can't read it then it sees blank and because it's blank it doesn't read on to the "}" and thus you get that error. Either way I used to get this error alot, I don't now, I fixed it, but I don't remember how

CalvaryCptMike wrote:I think what it comes down to is that something is wrong with your cis_inf_sniper and in the req

sim-al2 wrote:Well it's quite simple, there's a bracket missing somewhere in that file.

AQT wrote:Expecting bracket errors usually mean something other than a missing bracket the majority of the time.

did you mean the same thing as sim-al2? because AQT already corrected that assumption.


you can get these req bracket errors when something the units uses like a model, skin or odf cant be read correctly and therefore the unit as a whole cant be created.

ok well this problem seemingly happens at random. i had the snipe working and then i decided to add another weapon on him that i made. it was a detonation pack that i made that would play my custom effect of a black hole and then suck anyone who gets near it in and then kill them. i had added the weapon and then munged and when i did that i got the munge error then looked ingame. that when i noticed that only the driodeka, rocketeer, and super battle driod were there. i made the weapon just a weapon in the common folder since i added in the "ordanencename" and "explosionname" odf codes in their respective places. i was thinking that this would work because this is exactly what they do with force powers. now i only have those three units and can't munge anything new untill i fix this.

did that clear anything up or is there something else that you wanted?

This may work

Go into data_ABC > _BUILD > Sides > Your side name which ever had cis_inf_sniper > MUNGED > PC and delete anything with cis_inf_sniper and all his weapons.

Then re-export his custom weapons or models then remunge it.

agentsmith38 wrote:This may work

Go into data_ABC > _BUILD > Sides > Your side name which ever had cis_inf_sniper > MUNGED > PC and delete anything with cis_inf_sniper and all his weapons.

Then re-export his custom weapons or models then remunge it.

ok i did that for the sniper but i still get this message
i tryed doing this for the engineer and magna guard but it didn't really work so now i am wondering what to do.

EDIT: ok i looked in game and the sniper is still missing, so are the engineer and magna still.

if you changed odfs a unit uses and you get the bracketerror afterwards, you edited it wrong and should undo the changes. adding commands that may not belong into an odf of this label (you cant use odflines from units in weaponodfs because they have a different label) may cause this problem. if you arent sure whether the command can be used or not, take a look at the odfparameters.txt on psych0fred's site

well i was just searching my odfs again for problems and found that in the det ord file i had put
"ordanencename" instead of "explosion" so i guess thats why i shouldn't mod at 2:00am

thanks for your help everyone and sorry to waste your time on a mistaken word...