> For the complete documentation index, see [llms.txt](https://docs.otherside.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.otherside.xyz/platform-documentation/creation/unreal-development/features-and-tutorials/web-browser/debugging-issues.md).

# Debugging issues

{% hint style="success" %}
verified: 2025-11-20 version: v39
{% endhint %}

When you run into issues, there's a few ways you can better understand the problem.

### Console log events

You can replace the console log events and send to `ue5("log", args)` to print them to console.

### Chromium Devtools

Using Chromium Devtools allows you to inspect the browser just like `F12` in Chrome.

First make sure you can interact with your browser; if it's in 2D-space in the viewport this is fine. If it's in 3D-space using a Widget Actor Component, make sure to enable `Receive Hardware Input`.

<figure><img src="https://970394512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ft3SBfOIsRz4GCNFFpae7%2Fuploads%2Fgit-blob-246f81ea3e74cd2ad8ea955b3f35a6517d5f11f9%2Fimage%20(1513).png?alt=media" alt=""><figcaption></figcaption></figure>

Select the browser and use the shortcut `Ctrl + Shift + L` which will open the Devtools.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.otherside.xyz/platform-documentation/creation/unreal-development/features-and-tutorials/web-browser/debugging-issues.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
