Is there a troubleshooting PRINT technique? debugging

in python for instance — even if its objects, you can print it and it will cast to a string

so the first time i tried to print out a return ‘code’ i was surprised that i cant

i dont have a troubleshooting method set up
so im trying to wrap my head around it

because using append/print text every time seems like a horrific way of doing things?

any resources for how to engage this properly
and i am pretty sure i wont be using the logs because they seem slow or too much
unless i could make a new log or something separate

question is a bit unclear.

You’ve indicated this as a blueprint question. In blueprints, you use the print string, print text, or breakpoints. You also have the blueprint debugger tool.

If you want to format text you can use format text node. That can plug into a print string so that you can easily input variables and it will auto-convert them.

There is several plugins on the marketplace that open up a little more functionality for logs to blueprint, though it’s minor convenience stuff.

You can enter verbosity commands into the print nodes as well, such as Error : my message, Warning: my message, etc.

1 Like

Not sure how you tried it but:

Also Draw Debug String with Test Base Actor plugged in is handy:

image

1 Like

over the years, geez like 30 years now ---- i prefer something similar to this
i can greatly extend this example i just threw it together to give vague idea

from what i see i have to build this stuff by hand every time and like 35 nodes maybe

text location … ! ha ha ha ----- thats the kind of thing i like to hear
scalable stuff, like 50,000 debug messages just, everywhere D:
shock and awe