Licenses
Uses AI
Order
Advanced Search

Search will generally match any assets that contains all words from the search query. The words can be anywhere in the asset name, description or tags. All search queries are case independent.

To narrow down search results, you can use the following operators:

  • godot | engine
    will match if either "godot" or "engine" are found
  • godot MAYBE engine
    will match if "godot" is found, while ranking items higher that also match "engine"
  • godot -engine (alternative syntax: godot !engine)
    will only match if "godot" is found in an item that does not contain "engine"
  • @name godot @description engine
    will match if "godot" is found in the asset name, and "engine" is found in the asset description
  • =godot
    will match "godot" as a separated word, so it would not match "godotengine" while it will match "godot engine"
  • "godot engine"
    will match the exact string "godot engine" (so it won't match "engine godot")

Glitchless: Game Observability for Coding Agents 0

by Glitchless | MIT

See how your Godot game runs for the people playing it: every frame timed with each stutter's likely cause, errors with what the player did just before, and where players quit. Your coding agent reads it over MCP and fixes the next build

Glitchless times every frame on every player's device and names each hitch's likely cause, groups errors and crashes with what the player did just before, and shows where players quit. Your coding agent (Claude Code, Codex, Cursor and others) reads it all

Sentry 0

by Sentry | MIT

Real-time crash reporting for real gameplay across all platforms, including any game engine on any console, PC, or mobile device. See the right context on crashes and errors across your development and retail builds, so you can fix issues before they bring

Godot plugin to capture crashes and errors in native code and GDScript

loading more results...