[karajorma]

How hard would it be to export the events and messages lists (that you can get to in-game by pressing F4) to a file?

I see it being a very useful funtion for playtesters and FREDders. I've lost count of the number of times a bug has slipped past me because one I was out of the mission I didn't remember it. I've jumped out of a mission only to wish I'd checked the event list a similarly large number of times)

Can someone check? Cause I've got a horrible feeling that this might turn out to be a few lines of code that everyone will kick themselves for not thinking of/adding earlier

[Goober5000]

*kicks karajorma*

Yes, this is a few lines of code.  But you realize that I'm going to be the one who adds this, right?

[phreak]

only since you're the only one that can complile fred.

[Goober5000]

This doesn't need FRED at all.  It can be activated with a command-line that dumps text to a file.

[karajorma]

Originally posted by Goober5000


*kicks karajorma*

Yes, this is a few lines of code.  But you realize that I'm going to be the one who adds this, right?

Yeah but the playtesters working for TVWP and FSPort will love you for it.

Hell you'll probably use it yourself next time you playtest

Quite frankly I'm surprised no one thought of this one before. I didn't think of it myself. It was Singh complaining that FS2 couldn't do it that got me wondering why the hell it didn't

[Singh]

Originally posted by karajorma


Yeah but the playtesters working for TVWP and FSPort will love you for it.

Hell you'll probably use it yourself next time you playtest

Quite frankly I'm surprised no one thought of this one before. I didn't think of it myself. It was Singh complaining that FS2 couldn't do it that got me wondering why the hell it didn't

Actually, FSCZ did ask for this a long time ago, as it would help with keeping track of the kills/scores in a MP session and over the long term

[phreak]

Originally posted by Goober5000
This doesn't need FRED at all.  It can be activated with a command-line that dumps text to a file.

hmm must have been thinking of the other events list then.  although if you can print both of them, you can check off whether an sexp worked correctly or not

[Goober5000]

I just found out that this is already in the source, saving me some work. Just run a debug build, enter cheat mode, and hit ~E.

[ShadowWolf_IH]

Damn, and we were hoping to make you do some ACTUAL work

[karajorma]

Originally posted by Goober5000


I just found out that this is already in the source, saving me some work. Just run a debug build, enter cheat mode, and hit ~E.

Useful. Any chance you could enable it from the command line too? Like I said the most annoying times are when you've just jumped out and then wish you'd checked something.

[Goober5000]

Not really.  Even if I went with my original idea, I'd only enable it in debug builds.  It's a lot of extra computation.

[Singh]

what does ~E do?

should it be hit after the mission or before?

Will it spew out evil coding lingo at me or actual events and stuff?

[Goober5000]

Use it during the mission, like any cheat key.  It displays a list of events (with their status) that you can scroll through.

[karajorma]

Originally posted by Goober5000
Not really.  Even if I went with my original idea, I'd only enable it in debug builds.  It's a lot of extra computation.

Fair enough I might give it a try myself when I finally get some free time and finally get around to learning some more C++ though.

Would it really be that big an overhead? I suppose the I/O might slow things down now I think about it.

Now I need to go look up the cheat mode (I only tried it a couple of time and never could get it to work)

[phreak]

i don't think the player would notice if the events list gets dumped as the player enters debriefing.  even if its a 20 minute mission, the I/O should be significantly less than taking a screenshot.

[Goober5000]

This happens during the mission.