Announcing Studio Deep Links on Stack Traces for Server Logs

This topic was automatically opened after 10 minutes.

Gryphscribe: image1 1317×475 28.8 KB image11317×475 28.8 KB In this image, it doesn’t look like there’s a way to quickly copy a stacktrace without manually highlighting it and copying the text. Would it be possible to add a “copy to clipboard” button for the stacktrace? This would be handy when quer

This is pretty cool! Opening the exact place version where the error happened seems incredibly useful, since the scripts might have changed by the time you investigate it. Not sure how often I’ll use this yet, but I appreciate making server errors easier to track down!

awesome! this makes fixing errors less tedious, thank you for this. hoping to see more updates that are this good cough cough, such as EditableMesh support for PromptCreatePlatformContentAsync

Can you please add accurate trace back to coroutine.wrap() ? The error message always points to the line asserting coroutine.wrap() instead of the line inside it actually causing the error. When debugging, I have a bool to not use coroutine.wrap() just so I can see what line is erroring. It would be

is there a way to access game wide error logs (server and client) from the OpenCloud API? (similarly to the Error logs section in Creator Hub)

We needed this to improve debugging, good update!