mirror of
https://github.com/godotengine/godot-website.git
synced 2025-12-31 09:48:43 +03:00
Huge thanks to JohnVeness, AThousandShips, and Meorge for their great help rewording my broken English.
1.1 KiB
1.1 KiB
type, section, rank, importance, anchor, title, blockquote, text, contributors, read_more, image_alt, image_src, image_src_2x, position, media_position
| type | section | rank | importance | anchor | title | blockquote | text | contributors | read_more | image_alt | image_src | image_src_2x | position | media_position | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| entry | highlights | 2 | 2 | script-backtracing | Script backtracing & custom loggers | Down the rabbit hole | Script backtracing, gives developers the exact details on where an issue happened in the code. Even in "Release" builds.[^script-backtracing-enable] Custom loggers allow developers to intercept log messages and errors. That makes it possible to create a tool for reporting bugs within your game. Developers and players will now be able to report issues containing more accurate information of its origin. [^script-backtracing-enable]: Make sure that the _Debug > Settings > GDScript > Always Track Call Stacks_ project setting is enabled. |
|
https://github.com/godotengine/godot/pull/91006 | Screenshot of a terminal displaying script backtraces (one error, one warning). | /storage/releases/4.5/images/godot_script-backtracing.webp | /storage/releases/4.5/images/godot_script-backtracing_2x.webp | center-left | top |