Taskbar

The Taskbar in AVE II facilitates switching between game modes. This guide explains how to implement mode requests via BPI_CoreAPI, assign Points of Interest (POIs) to specific taskbar buttons, and handle the resulting logic within the Game Instance.

📂 Location: AVEII > UI > Panels

Sending Mode Requests

To initiate a mode switch, the Taskbar widget must send a request to the Game Instance (BP_AVE_GI) via the Blueprint Interface BPI_CoreAPI when a button is clicked.

  1. Open WBP_Taskbar_Main.
  2. In the Event Graph, find the OnClicked event for the desired mode button.
  3. Call the relevant Blueprint Interface function from BPI_CoreAPI (e.g., RequestAmenitiesMode).
    Optional: Call RequestSelectPOI (via BPI_CoreAPI) to define the pawn/camera transform and constraints for the target mode.

Assigning POIs to Taskbar Buttons

Although the buttons exist within the Taskbar widget, the actual assignment of POIs happens inside the parent WBP_Game_Menu.

  1. Open WBP_Game_Menu.
  2. Select the WBP_Taskbar_Main widget reference in the hierarchy.
  3. Locate the BP_POI array in the Details panel.
  4. Assign the relevant POI Soft Object Reference from the level to the array index that corresponds to the specific taskbar button.

Handling Requests in Game Instance

Once a request is sent, BP_AVE_GI (Game Instance) handles tasks such as toggling POIs and loading streaming levels.

Example: Dollhouse Mode Implementation

The following workflow demonstrates handling a request to switch to Dollhouse mode, which requires loading a specific streaming level and registering its POIs.

💡 Note: Check Game Instance Implementation Examples for the capabilities of BP_AVE_GI.

  1. Open BP_AVE_GI.
  2. Implement the Event RequestDollhouseMode.
  3. Load the required Stream Level.
  4. After the level loads, use GetAllActorsOfClass to retrieve BP_POI_Generic actors.
  5. Pass these actors to the CategorizePOIsbyTags function to register them with the Game Instance.
  6. Toggle POI visibility based on their type.

related documentation

Configuring Project Settings

Configuring Project Settings To ensure AVE II functions correctly, you must verify specific project settings. These configurations establish the communication backbone between the UI and your Blueprint logic. Note: The BP_AVE_GI class is essential for handling global communication and persistent data between the UI and gameplay elements.

Read more >

Getting Started

Welcome to AVE II, a real‑estate visualization experience built in Unreal Engine 5. This guide helps you quickly understand the core systems, navigation, and workflow so you can begin integrating AVE II into your project or exploring its features. Overview AVE II provides an intuitive, high‑quality exploration system designed for

Read more >

POI Basics & Custom Tags

Get started with interactive navigation in AVE II. This beginner-friendly guide covers the essentials of placing BP_POI_Generic actors, customizing info panels with text and images, and organizing your locations into simple categories using tags.

Read more >

Framework

This section explains the core structure of AVE II. It covers which systems manage data, how responsibilities are split up, and how different parts of the project communicate with each other. These pages are designed to help you understand where to modify or add Blueprint logic. They explain which classes

Read more >

Game Instance (BP_AVE_GI)

The Game Instance (BP_AVE_GI) acts as the central mediator in AVE II. It owns a persistent runtime state, coordinates communication between systems, and ensures that gameplay logic, UI, and data remain decoupled. Roles and Responsibilities The BP_AVE_GI manages high-level orchestration across the framework. Its primary duties include: Implementation Examples The

Read more >