Hard Light Productions Forums
General FreeSpace => FreeSpace Discussion => Topic started by: FelixJim on June 26, 2011, 04:39:01 pm
-
Speaking as a FREDer who's curious as to how careful he ought to be about what shows up in the event log during the course of a mission, I'd be interested to know how many players actually make use of the event log (very few, I believe, but it does no harm to ask). Thanks for voting!
-
occasionally, the main usage I give it is to check if things went as I predicted them to, like a ship exploding at the right timing, correctly ordered messages, very rarely I find something that needs to be removed from the event log actually, and if I find it only because of the former practice.
-
Does it matter? Is it possible to remove things from the log?
I mean.. it barely shows what's going on.. but if people want to see what's going on under the hood of my mission, that's fine by me.
-
You can doctor a little... especially with #, ship-create and ship-vanish.
-
When I was younger, if one of my wingmates got shot down, I'd sometimes use the event log to find and punish the responsible party. Nowadays, I look at the event log to sort out something chaotic or unusual, like if one of my wings managed to quietly die, or a lot of things got wasted in a huge explosion.
-
No, I'm not going to hold it against you if the events log is a ledger of what's going on in your Pegasus farm. :p
-
Idea: Shivanville app for Facebook.
-
Does it matter? Is it possible to remove things from the log?
If not, this would be a good option to have...
-
Does it matter? Is it possible to remove things from the log?
If not, this would be a good option to have...
I was thinking this... but I don't know how difficult it would be to implement, or even how worthwhile.
-
Often, especially to check hard and fast what just jumped in/died/departed.
And to check what killed what in order to prioritise on the next playthrough.
Also WIH comms log :lol:
-
I use it all the time. I use it in most missions.
-
I use it often to check the messages (I often don't get through reading them), or to check my objectives, and their status of completion (I've been through a lot of s*** campaigns, it's better like that). I also check to see self destructs (to know if I could have done anything) to find who is killing my wingmen or the capships I'm escorting.
-
Is it sad that I didn't even know it existed? What key do I press to use it?
-
F4
-
I often check it if things go wrong while I'm playing a mission. It provides information to allow me to modify my strategy on the next attempt.
-
Mostly just to verify that an enemy wing is destroyed.
-
F4
Ah, so that's what that was.
-
If not, this would be a good option to have...
Not without quite a big rewrite of the log. The game uses the log quite heavily to tell if certain SEXPs can trigger or not. Start removing events from the log and you stand a good chance of buggering up mission logic or even crashing the game.
-
Souldn't it be possible to separate the textual display of the event log from the actual game-logic events themselves?
-
if it's my first time through a campaign, I almost always check it to read the messages between ships (partly to read any plot elements that might be coming through that way, and partly to see if there's any thought put into the chatter between ai pilots.) I always look through the event log itself when I'm failing a mission so I can see what I screwed up or missed.
-
I'm going to admit this is a lot more use than I expected.
-
Souldn't it be possible to separate the textual display of the event log from the actual game-logic events themselves?
It's possible, what I'm saying is that you'd have to do that significantly longer step before you could add a SEXP to hide events.