Help w/ scenario

[Theben]

I tried modding an existing events file and get the message:

Error "-3" in module "12" data: 15 8

File open failed: MODULES.DB
Most recent DOS error: 2

I ran debug and it shows after "endevents". It's also a multi events/rules scenario.

Ideas?

[Arthedain]

Create a new events-file and copy/paste in all events in that one, ONE BY ONE, and run the scenario and check the events. That way you will see which one is wrong It's the hard way, but I guess, the only way.

[N35t0r]

You can cpoy-paste them in larger batches (10 or 5) and then start making the batches smaller when you have found a faulty one.

[techumseh]

In my experience, this is almost always a misplaced comma or semi colon. Before you start recopying everything, just have a real close look at you @UNITS field.

[MagyarCrusader]

Originally posted by Arthedain
Create a new events-file and copy/paste in all events in that one, ONE BY ONE, and run the scenario and check the events. That way you will see which one is wrong It's the hard way, but I guess, the only way.

You guys have no idea how many times I had to do this for my ToT stuff...

[Boco]

Yeah, I've skipped more commas than I'll ever admit. If you have Excel, just load Rules.txt using commas and semi-colons as delimiters. Omissions in the various @ sections stick out like a sore thumb.

It's an easy check to do before the painstaking events testing.

Another possible culprit could be GIF files of the wrong format. Don't they give a similar error?

[N35t0r]

also, i used to get errors when i annotated the rules by adding semicolons and then notes to fileds which did not originally have semicolons (such as the cosmic principles...)

[Theben]

Thx, guys, but it's not the rules.txt. When I put back in the old events file it works fine. So apparently I need to follow Arthedain's procedure.

[Boco]

Also means your GIF files are okay.

I ran debug and it shows after "endevents".

This stumps me. That means you saw:

@ENDEVENTS found

remaining heap space: 771 bytes

Rules out syntax errors, incorrect coordinates, unit and placenames.

What is your remaining heap space? If it's high, ignore the following.

Usually when the heap space is depleted, I think the crash error message indicates something like a stack overflow, but IIRC once in a blue moon too many events can trigger a crash without a useful error message. It's a very long shot but you might have luck deleting the last 1-2 events and retrying.