search

Teardown-Issue-Tracker-Maintainers / Teardown-Issue-Tracker

A public repo for the community to track issues/bugs/feature requests in Teardown.
11 stars 6 forks source link

[Bug?] Calling `DebugPrint()` in main menu scripts outputs nothing on screen #531

Closed YuLun-bili closed 2 months ago

YuLun-bili commented 2 months ago

Describe the bug

as described in title

Steps to reproduce the behavior

call DebugPrint() in main menu scripts and watch screen outputs

Expected behavior

DebugPrint() messages got printed if not intended to behave like this I guess? (same as pre 1.5.4 versions)

Environment

Additional context

Combined with #527 it made life of those changing some main menu scripts (such as me) much harder :(

On the other hand, I'm not sure why DebugWatch() still behaves normally if removal of DebugPrint() output in main menu is intended.

Gregory-Gregory commented 2 months ago

@YuLun-bili hi,

Thank you for this bug report.

I have forwarded it to the QA team. If they need any additional details, I will let you know.

Gregory-Gregory commented 2 months ago

@YuLun-bili hi again,

I have received a response from the team regarding this issue:

Currently, only errors from local mods are displayed on the screen. If you need to see errors from the game script, you can view them in the logger window.

YuLun-bili commented 2 months ago

@Gregory-Gregory Then should DebugWatch() output hidden or not? They currently still shows when called in game scripts

Gregory-Gregory commented 2 months ago

@YuLun-bili hi!

Regarding your last question, the team replied:

The DebugWatch doesn't print errors, so we don't hide them.