so i munged my map after adding objects to it, and it came up with this error:

ERROR[levelpack shell.req]:Input file shell.req does not exist. [continuing]
1 Errors 0 Warnings

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

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

ucft <--
[continuing]
2 Errors 0 Warnings

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

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

ucft <--
[continuing]
2 Errors 0 Warnings





I tried putting brackets where it says they were missing but it just created more errors. I removed the objects but it didn't fix it. Iv'e been working on this map all year and i don't want to lose it if someone can please help i'd much appreciate it

1. When you ran VisualMunge, did you make sure to only check the Common check box?

2. Did you try cleaning?

3. Which objects did you add to the map?

1. When i first ran a munge, I only had world selected, after it came up with the error i munged common, however the same error occurred. After that i munged everything, but the error occurred again.

2. Yes iv'e cleaned my mod at least 3 times, however it didn't fix the error.

3. The Objects were;
hoth_prop_trench_short
hoth_prop_trench_turrets
tur_bldg_hoth_laser_mortar
tur_bldg_hoth_dishturret

However the turrets shouldn't be the problem because their script is added to common and I already have some placed down.

The ones with "ERROR...Expecting bracket, but none was found." mean that while editing those files you may have deleted a necessary bracket or have a comma before the end bracket. at least that's what it usually means. make sure if you edit these files you munge common as Samee3 stated. (I'm new at the mod tools, but in my experience in coding that's what compilers say when you're missing a bracket or improperly using one)

One more question: did you put said objects (the odfs) in the map's odf folder, or did you add them from somewhere else? Adding objects from a location other than the world's own object folder can cause problems.

Atephious wrote:The ones with "ERROR...Expecting bracket, but none was found." mean that while editing those files you may have deleted a necessary bracket or have a comma before the end bracket. at least that's what it usually means. make sure if you edit these files you munge common as Samee3 stated. (I'm new at the mod tools, but in my experience in coding that's what compilers say when you're missing a bracket or improperly using one)

The culprit files are not edited manually; they are written by the Zero Editor when the map is saved. Stable as it may seem, every piece of software has its bugs, and Zero Editor is no exception. I have actually encountered this problem in the past while editing a stock map. All I did was move a couple objects around, and then surprise!: munge errors just like these.

My solution was to start over, but if nothing else works, try making a new project, and see if you can re-create the problem.

Samee3 wrote:One more question: did you put said objects (the odfs) in the map's odf folder, or did you add them from somewhere else? Adding objects from a location other than the world's own object folder can cause problems.

Atephious wrote:The ones with "ERROR...Expecting bracket, but none was found." mean that while editing those files you may have deleted a necessary bracket or have a comma before the end bracket. at least that's what it usually means. make sure if you edit these files you munge common as Samee3 stated. (I'm new at the mod tools, but in my experience in coding that's what compilers say when you're missing a bracket or improperly using one)

The culprit files are not edited manually; they are written by the Zero Editor when the map is saved. Stable as it may seem, every piece of software has its bugs, and Zero Editor is no exception. I have actually encountered this problem in the past while editing a stock map. All I did was move a couple objects around, and then surprise!: munge errors just like these.

My solution was to start over, but if nothing else works, try making a new project, and see if you can re-create the problem.

I'm afraid I won't be much help to you OP, seeing as others have already asked the vital questions, but I will give you 1 piece of advice:

Always make a back-up file, ALWAYS. If nothing else, get in the habit of doing this after every successful munge and test.