DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to ask an AI chat questions about an Unreal level with Uebox

Use the built-in chat to query a level, such as counting lights, without writing code.

Credentials. Your model provider API key is stored encrypted on your machine, and requests go straight to the provider you set, so only add keys you are comfortable using with that provider.

Who it is forA level designer or artist who needs a quick count or check of what is in a level, and has an AI model key ready.

The problemChecking a level by hand for things like light count or actor layout is slow, especially in large projects.

The outcomeThe chat answers questions about the open level using engine tools, and the user sees each tool call that produced the answer.

What you need first

  • A Windows PC for the installer, with Unreal Engine 5.0 to 5.8 and a .uproject file
  • An API key from a model provider that supports tool calling, or a local model such as Ollama or LM Studio
  • Permission to install the UnrealAgentLink plugin into your Unreal project

Steps

  1. Install UE Box from the Releases page on Windows.
  2. Go to 设置 → 模型 → 添加服务商, enter your API key, then set 默认模型 → 对话 to that model. The model must support tool calling.
  3. Go to 项目库 → 导入项目, select your .uproject, install the UnrealAgentLink plugin, then click 打开项目.
  4. Open 侧边栏 → AI 对话 and ask a question such as "How many lights are in this level?"
  5. Check the tool calls shown in the chat to confirm the answer came from the open level.

Prompt for your agent

Using the ueboxai/uebox app with an open Unreal project, ask the AI chat how many light actors are in the current level and return the number. Verify the answer by checking that the tool call list shows a level query, not a guessed number.

Caveat. The README says the chat needs a model that supports tool calling, so a chat-only model without tool support will not query the level.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page