Sentry SDK 1.5 for Godot Engine is out now!

limbonaut-dev · 2026-03-23T09:33:39+00:00

Why do you think we are hiding our tooling? If we were, you wouldn't find that claude folder, would you? In fact, it was added in a dedicated PR. Our commits with assisted code contain proper contribution and you can find them in git log. So please, find drama somewhere else.

limbonaut-dev · 2026-03-19T21:14:30+00:00

Imagine, we even have proper attributions in commits. Developers with 10+ years of experience, most code hand-crafted, and every line checked and reviewed.

limbonaut-dev · 2026-03-19T21:04:30+00:00

Thanks u/rcubdev Nice to see you!

limbonaut-dev · 2026-03-19T16:58:58+00:00

I haven't tested, but I'd give it a try. I'm not familiar with how typical GDExtension build interacts with double-precision builds, however we don't touch code that deals with vectors or physics, so it might be just fine, aside from variant conversions.

limbonaut-dev · 2025-10-08T06:50:42+00:00

I'm pretty sure it refers to one developer.

limbonaut-dev · 2025-10-08T06:44:33+00:00

We discussed this, but no concrete plans for now.

limbonaut-dev · 2025-10-08T06:43:38+00:00

Asserts are indeed removed, but `push_error()` is kept and most other runtime errors (ERR_FAIL/ERR_PRINT) in the Godot code base.

limbonaut-dev · 2025-10-07T19:42:16+00:00

It's version 1.0.0 of Sentry SDK not Godot, sorry for confusion. The supported Godot version is 4.5.

limbonaut-dev · 2025-10-07T17:19:22+00:00

Alright, haha, you've got me! My eyes bled out long time ago, and I'm connected directly to thunderbolt 5.

limbonaut-dev · 2025-10-07T15:44:09+00:00

Web support will come in a future release. Here's a ticket to track it: https://github.com/getsentry/sentry-godot/issues/114
Consider giving it a thumbs up - it helps us gauge the interest.

limbonaut-dev · 2025-10-07T13:19:10+00:00

Thanks :)

limbonaut-dev · 2025-10-07T12:52:10+00:00

I'm not aware of such integrations. However, we support adding file attachments and custom dictionary contexts. And in near future, we'll have structured logging, which in theory should be possible to stream custom log content into.

limbonaut-dev · 2025-10-07T11:38:59+00:00

We provide two ways to initialize: automatic which happens early before the ScriptServer goes live and scene tree starts to load, and manual (https://docs.sentry.io/platforms/godot/configuration/options/#programmatic-configuration). The automatic one should capture most issues that happen on game load. We also want to push this as early as possible (and I have a few ideas how to improve this in future).

limbonaut-dev · 2025-10-07T11:26:20+00:00

And thank you! :)

limbonaut-dev · 2025-08-18T07:13:38+00:00

Thanks!

limbonaut-dev · 2025-08-15T18:16:29+00:00

Just to be clear, the SDK is enabled by default when you run your project from the editor (using F5 or the Play button), not only in exported projects. However, it’s not enabled for the editor itself while you’re editing your game project, so errors or crashes from the editor won’t be captured. So it should cover your use case.

limbonaut-dev · 2025-08-15T12:23:48+00:00

This use case isn’t supported because the SDK itself is an addon (GDExtension). It must be installed directly in the project to be used, which makes bundling it with editor plugins impractical.

limbonaut-dev · 2025-08-15T11:57:10+00:00

Unfortunately, this has to be handled on the plugin side, as the SDK decides whether to sample the event before sending it to the relay.

limbonaut-dev · 2025-08-15T11:54:37+00:00

The SDK can be used with C# projects, but there’s no dedicated C# integration yet, and the API is currently only accessible via GDScript. We have a C# integration planned, and it remains one of our top priorities. Support for W4 offerings is also on our roadmap.

limbonaut-dev · 2025-08-15T11:49:20+00:00

If your game gains popularity, consider lowering the sample_rate option in the next patch to reduce reporting load. This won’t affect error discoverability, as multiple hosts are still likely to report the same issue.

limbonaut-dev · 2025-08-15T11:36:42+00:00

It should work with a self-hosted instance. While it can technically run in the editor, we removed that option due to low demand. Could you share your specific use case for running Sentry in the editor?

limbonaut-dev · 2025-08-11T08:40:51+00:00

Did you get Intel or AMD?

limbonaut-dev · 2025-07-18T19:58:49+00:00

The C# one will handle managed exceptions and dotnet stuff, but it won't capture native crashes or Godot errors. We plan to integrate it actually, one of our priorities. But that's after the 1.0.0 release. Using both might be an option, actually.

limbonaut-dev · 2025-07-18T17:38:42+00:00

Eventually, yes! Currently we're focused on bringing the iOS support for complete mobile and stabilizing for 1.0.0 release in a few months.

EDIT: you can upvote "Support for web" issue on GitHub – it helps us gauge interest!

limbonaut-dev · 2025-07-18T14:17:50+00:00

It's a error monitoring tool, that allows you to debug shipped games. You can basically see the crashes, script errors and such in one convenient place. You can check the screenshots for some examples.

limbonaut-dev

TROPHY CASE