In C/C++ we have access to useful macros like func, file, line, etc that are extremely useful for debugging and prints. Is there anything like that in Blueprints? I’ve just been manually adding the event node and blueprint name to the prints/logs for my error cases.
Or is there some better way of tracing where in code a print/log occurs in blueprints?