Frontend logs

gbandit logs frontend and the Frontend tab on the project's Logs page show what went wrong in your players' browsers. The platform can't see into a browser, so these entries come from the gbandit runtime, which your game loads in its <head>. Games scaffolded from the gbandit template already load it. Backend logs need nothing: whatever your container writes to stdout shows up under gbandit logs backend.

What the runtime reports

• Uncaught errors and unhandled promise rejections, with their stack.
• Everything passed to console.log, console.warn and console.error. The original still runs, so DevTools is unaffected.
• Whatever you pass to gbandit.reportError().

Each entry records the page's URL and, when the player has a token, which player hit it. Entries from a burst (a render loop that throws every frame) go out together, up to 20 at a time.

A new frontend starts the environment's log over (a deploy for dev, a promote for prod), so what you read always belongs to the code that is live. Under a local dev server the runtime reports nothing; your browser's DevTools has it all.