You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i just came from the suggestions section on discord , one of the admins asked me to post it here , there is a special type of the print() function called print_debug() and it outputs much more info that are very beneficial for developers during debugging , so far we don't have it at orchestrator , is it possible to implement it in the future ? thank you very much im such a big fan of this truly amazing project
Implementation ideas
No response
The text was updated successfully, but these errors were encountered:
As pointed out on Discord, the print_debug function is a GDScript-specific function defined in gdscript_utility_functions.cpp inside Godot. There are several utility functions defined here, which include:
type_exists
_char
range
inst_to_dict
dict_to_inst
Color8
print_debug
print_stack
get_stack
len
is_instance_of
These are functions exposed by the GDScriptLanguage as get_public_functions(). Such functions are not exposed as part of the extension_api.json and are therefore not bound by the Scripting API, but are only bound within the context of GDScript. This would make defining unique, internal Orchestrator functions quite easy to expose perhaps?
Description
i just came from the suggestions section on discord , one of the admins asked me to post it here , there is a special type of the print() function called print_debug() and it outputs much more info that are very beneficial for developers during debugging , so far we don't have it at orchestrator , is it possible to implement it in the future ? thank you very much im such a big fan of this truly amazing project
Implementation ideas
No response
The text was updated successfully, but these errors were encountered: