Hello. I got this error munging: I'm sure it's to do with my campaign lua (ctf) where I haven't done it right. Please help me. Here is my lua. Ty in advance.

What's the problem, and why is it strange? It's telling you exactly what's wrong, unlike some other errors that just point you in the right direction.

..\..\common\scripts\WW2\WW2g_ctf.lua:186: <eof> expected near `end'

186
This occurs around line 186. I saw you put a "<eof>" in near there, but you take it too literally. <eof> means end of file.
<eof> expected near `end'
The compiler expects the end of the file, but it instead gets an "end". That means you have an extra "end" somewhere that is screwing up your code. In your case, it's the one before Oh, and remove the <eof>.

oh, lol, thanks. i'll try it now.
it worked, but none of my objectives are showing. Why? Please help Fris or anyone else. Here's the lua again. Can someone do it up for me so it works? Thank you ever so much

The objectives never start because you never told them to. BeginObjectives() is never called. Maybe you wanted to call it when the beginobjectivestimer ends? If so, that code isn't written.

so do i need to add BeginObjectives() to the lua? Where? Please help..

You could look at a stock map for reference.

good idea

It's ok, I've had those moments before too.

I didn't have any inspiration - the stock campaigns are set up really difficultly..

[RDH]Zerted wrote:...BeginObjectives() is never called...

Oops, sorry. I skimmed over one of the lines. Ignore my last post.

Scatter print statements throughout your code so when you run it, you can visually see in the debug log which sections of code are running and which sections aren't being run.

Example Print Statement: print("Just entered function ScriptPostLoad()")

i cannot do that, sorry. Please could you do that. I do not understand what you mean.

No, that is something you must learn to do. It's called debugging. You are having problems with parts of your code not running, so you need to figure out which sections of your code are running. One way to do this is to put print statements throughout your code so you can see what is running. Print statements are functions that take a string. The string gets written to the debug log.

Put an informative print statement, say, at the start of each function then munge and run the map. Play the map until an objective is supposed to start. When it doesn't, pause the game and look at the debug/error log. The log will contain some of your print messages. This allows you to see which sections of the code were being run by the game. Trace/follow through the messages and the code until you come to the first message that isn't printed. You now know that the error is most likely in the code that runs between those two print statements (between the one that printed and the one that didn't).

If you don't understand anything about coding, such as functions, strings, or basic scoping rules, then you should go to the main Lua web site and read their intro to programming tutorial.

Also, your conquest objective has no CPs added to it. Fix that then post a debug log.