Event Text Dump Problems

[Raindem]

I searched but didn't find anything so my apologies if this is a duplicate.

I'm using the new text dump feature (F6) I've encountered the following issues:

- The number of all events is off by 1. Event #1 becomes Event #0 and so forth.
- The number of all Turn triggers is reduced by 1 also.
- The delay is not displayed in the text file

I've only tried to use F7 once but it seems jacked up as well. Event #1 was repeated into Event #2 so then the remainder of the event list was off by 1. The more I look at the event list imported in with F7 the more errors and discrepencies I see. Ralph, I can send you some sample files if you like.

Curt

[Raindem]

I've been doing some more work using F7 to read a formatted text event list back into the scenario. It seems that if the scenario already has defined events this doesn't work, or works eratically / unpredictably. If the scenario has a blank event list then F7 seems to work OK. I know this can't be the intended effect so I must be missing something.

[Raindem]

It looks like the problems I encountered earlier were due to formatting errors in the text file. The system is VERY picky about this. But with a bit of care it's workable. Some events, for no explicable reason, just won't transfer in. But even with these drawbacks it is still a lot easier than working in TOAW's own event editor.

Also found a new bug. When you dump an event list into a text file it will insert a blank space at the end of each line. If you import that file back into TOAW it creates an empty news string. You have to go to each event line and delete the last 2 empty spaces before importing.

Edit: in some cases the above doesn't work and you have to use TOAW's event editor to null out the news string.

[Legun]

Really important news! Go on with the tests - I'm just going to start designing of event mechnisms for my Tannenberg...