Yelo Debug Output

Fleabag77 · Post by **Fleabag77** » Sat Apr 14, 2007 11:00 pm

What exactly is it? I guess it shows skulls you pick up and whatnot, but what else?

killgore333 · Post by **killgore333** » Sat Apr 14, 2007 11:12 pm

Actually, it shows what current script is running as it starts. Something as simple as music being started and stopped, to events happening, activating or being terminated, or character dialog being activated as they are supposed to say it. You will notice that the dialog text will cut off. That is because of the 80 character limit that almost all C++ programs and scripts should keep each line of code to a minimum of.

If I am wrong in any way, please correct me.

Fleabag77 · Post by **Fleabag77** » Sat Apr 14, 2007 11:22 pm

So it does show scripts? Great, that's exactly what I need. Thanks alot!

ali954 · Post by **ali954** » Sun Apr 15, 2007 10:32 am

no ur wrong sorry =]. there is a command called "print"

Code: Select all

(print "THIS SHOWS ON THE SCREEN WHERE IT SAYS 'YOU KILLED DEFAULT' ETC...")

doesnt work for the mainmenu tho idn y

killgore333 · Post by **killgore333** » Sun Apr 15, 2007 10:55 am

No no no no no no no no no no, It shows what script is being run. It will execute the code, then it will "print" the which means display text of which script is running on screen.

Edit: The 10 "no's" were for fleabag. Ali described what I was saying.

kornman00 · Post by **kornman00** » Sun Apr 15, 2007 12:28 pm

Its for allowing easier debugging of your scripts in your custom maps, however not limited to that [debugging].

It doesn't show what script is being ran, it only displays what you want it to display via the string argument. However if you say (print scripts_name_poop) and that is actually the name of the script the print macro is in, then yes it will print the script that is running (scripts_name_poop)

xbox7887 · Post by **xbox7887** » Sun Apr 15, 2007 2:37 pm

killgore333 wrote:Actually, it shows what current script is running as it starts. Something as simple as music being started and stopped, to events happening, activating or being terminated, or character dialog being activated as they are supposed to say it. You will notice that the dialog text will cut off. That is because of the 80 character limit that almost all C++ programs and scripts should keep each line of code to a minimum of.

If I am wrong in any way, please correct me.

The "debug output" option simply enables the print script...I actually hijack the call and substitute my own print code since the original stuff is nonexistant in retail builds. The text is limited to 64 chars for no particular reason, it's surely not a programming limitation

Fleabag77 · Post by **Fleabag77** » Sun Apr 15, 2007 3:13 pm

Oh, alright.