Hard Light Productions Forums
Community Projects => The FreeSpace Upgrade Project => Topic started by: headdie on July 03, 2009, 04:37:00 pm
-
Hi
Not entirely sure where to put this as it could easily turn into a suggestion for later SCP builds.
Is there a way to get the game to output data from the expression as they work in real time to a HTML/txt file? which sumerises events and then shows the detail of each check against that event.
I imagine the output looking something like (where event # replace with the event name)
Summery of (Mission file name)
Mission Briefing
Event B1
condition
Times Evaluated - 1
Times true - 0
;---------------------------------
Mission Events
Event E1
condition
Action
Times Evaluated - 1
Times true - 1
Event E2
condition
Action
Times Evaluated - 1
Times true - 0
Event E3
condition
Action
Times Evaluated - 2
Times True - 1
;---------------------------------
Mission Objectives
Event O1
condition
Times Evaluated - 6
Times true - 1
;---------------------------------
Mission Debrefing
Event D1
condition
Times Evaluated - 1
Times true - 1
;---------------------------------
;---------------------------------
Details
Event B1
Evaluated – Briefing
Reason – Requested by briefing
Result – False
Reason - GTC_Minnow = 0 in campaign variable
Event E1
Evaluated – Mission Time 36 seconds
Reason – Run if GTT Harrison Destroyed
Result – True
Reason – GTT Harrison Destroyed
Event E2
Evaluated – Mission end
Reason – Run if GTT Harrison Departs
Result – Incomplete
Reason – GTT Harrison Depart = 0
Event E3
Evaluated – Mission Time 60 Seconds
Reason – Run event every 60 seconds
Reason – NTD Tyranny not Departed
Reason – NTD Tyranny not Destroyed
Result – False
Reason – Run event every 60 seconds
Reason – NTD Tyranny not Departed
Reason – NTD Tyranny not Destroyed
Evaluated – Mission Time 120 Seconds
Reason – Run event every 60 seconds
Result – True
Reason – NTD Tyranny Hits Remaining < 50%
Event O1
Evaluated – Mission Time 30 Seconds
Reason – Run event every 30 seconds
Reason – Beta Not Arrived
Result – False
Reason – Beta Not In system
Evaluated – Mission Time 60 Seconds
Reason – Run event every 30 seconds
Reason – Beta Not Arrived
Result – False
Reason – Beta Not In system
Evaluated – Mission Time 90 Seconds
Reason – Run event every 30 seconds
Reason – Beta Not Arrived
Result – False
Reason – Beta Not In system
Evaluated – Mission Time 120 Seconds
Reason – Run event every 30 seconds
Reason – Beta Not Arrived
Result – False
Reason – Beta Not In system
Evaluated – Mission Time 150 Seconds
Reason – Run event every 30 seconds
Reason – Beta Not Arrived
Result – False
Reason – Beta Not In system
Evaluated – Mission Time 180 Seconds
Reason – Run event every 30 seconds
Reason – Beta Not Arrived
Result – True
Reason – Beta In system
Event D1
Evaluated – Mission end
Reason – Requested by debrief
Result – True
Reason – NTD Tyranny Departed
End output
Any thoughts?
EDIT
Thanks The E for the tags
-
Yes. [code][/code] tags are nice. (Sorry)
Sounds like a good idea, but could get very ugly very fast when you have events with a sufficiently high repeat count (or every-time'd ones).
-
Yes. [code][/code] tags are nice. (Sorry)
Sounds like a good idea, but could get very ugly very fast when you have events with a sufficiently high repeat count (or every-time'd ones).
that was the big issue that came to mind while setting this up the only workaround I can think of is if the output throws them to the bottom of the file so at least you don't have to trawl through it to find something else.
-
Personally, I would much rather have some kind of online sexp debugger. Something where I can see the sexp execution in real time, and single-step or manipulate it when necessary.