Makinom - Game Toolkit for Unity
  • Features
  • Showcase
  • Guide
    • Documentation
    • Tutorials
    • Extensions
    • API
  • Makinom 1
    • Tutorials
    • Plugins
    • API
  • Support
  • Forum
  • Get Makinom

Guide

Getting Started

  • Introduction
  • First Steps
  • Game Starters
  • Components Overview
  • Upgrading a Makinom 1 Project

Editor

  • Makinom Editor Overview
  • Node Editor
  • Asset Sources
  • Editor Section
  • Base/Control Section
  • Game Section
  • UI Section
  • Templates Section

Features

  • Schematics
  • Dialogue Importer
  • Schematic Nodes
  • Formula Nodes
  • Languages
  • Input Keys
  • Audio and Music
  • Game States
  • Pooling
  • Saving Game Objects
  • Scene Objects
  • Save Games
  • Variables
  • Selected Data

Machines

  • Machine Components Overview
  • Animation Machine
  • Animation State Machine
  • Application Machine
  • Auto Machine
  • Collision Machine
  • Global Machine
  • Interaction Machine
  • Render Machine
  • Tagged Machine
  • Template Machine
  • Tick Machine
  • Trigger Machine

UI System

  • UI System Overview
  • UI Layers
  • UI Layouts
  • UI Boxes
  • HUDs
  • Flying Texts
  • Text Codes
  • Unity UI Module
  • HUDs: Content Providers
  • HUDs: Conditions
  • HUDs: Click Actions

Scripting

  • Scripting Overview
  • Code Extensions
  • Custom Save Data
  • Custom Component Save Data
  • Custom Nodes
  • Starting a Schematic

Advanced Topics

  • Build Troubleshooting
  • Performance Optimizations
  • Home
  • Guide
  • Documentation
  • UI System
  • HUDs

HUDs

Table of Contents
  • HUD Types
    • Control
    • Information
    • Interaction
    • Tooltip
  • Display Conditions
  • Showing HUDs

HUDs are used to display information of the player and other things or add interactable functionality.

HUDs are set up in UI > HUDs.

Defining the actual position, size, style and content of a HUD depends on the used UI module, e.g. using the Unity UI module uses a prefab of the game object and component setup you created. Please refer the used UI module’s documentation for details.

HUD Types #

There are HUD types available for different purposes. Depending on the used UI module you’ll be able to mix functionality of different HUD types, e.g. the Unity UI module can mix individual components together as needed.

You can also create custom HUD types by deriving your class from the BaseHUDSetting class. Check out the included HUDs for examples and how to use UI system dependent setup.

Control #

Control HUDs are intended for creating virtual controls like on-screen buttons and joysticks.

Information #

Information HUDs are used to display information. They can either be displayed on their own or based on a user (e.g. a game object, the player, etc.) and display information based on that.

When the HUD has a user, it can also be displayed based on the user’s game object position on screen.

Interaction #

Interaction HUDs are used to display information of available interactions, either from within the player’s Interaction Controller or below the mouse cursor.

The HUD can optionally be displayed at the position of the interaction or player (i.e. on-screen position of their game objects). Information displayed within the HUD depends on the displayed interaction, e.g. using a Scene Object component on an interaction allows defining content information like name or description and use that in the HUD.

Tooltip #

Tooltip HUDs display information of the current tooltip content. The tooltip content is whatever is currently below the mouse cursor (or a locked content from some UI selection), e.g. a game object with content information (like Scene Object component) or a part of a UI that has a tooltip (e.g. a choice button).

Display Conditions #

Displaying a HUD can depend on certain conditions.

You can define Game State and Variable conditions that have to be valid to display the HUD.

Some HUD types can also have additional settings, e.g. interaction HUDs can be limited to certain interaction types.

Showing HUDs #

If a HUD is displayed automatically is defined by it’s Auto Display setting. Additionally, you can toggle displaying the HUD on/off using the Toggle Key settings.

When not displayed automatically, you can call a HUD using a Call HUD node in a schematic.

You can also use an Add HUD (to Game Object) component to add a HUD instance for the game object it’s attached to. E.g. use it to add health bars or other UI for enemies, automatically using them as the HUD’s user (e.g. displaying it at their position, using their variables for content information, etc.).

UI
Share This Article :
  • Facebook
  • Twitter
  • LinkedIn
  • Pinterest
Updated on December 16, 2020
Table of Contents
  • HUD Types
    • Control
    • Information
    • Interaction
    • Tooltip
  • Display Conditions
  • Showing HUDs
Sitemap
  • Features
  • Showcase
  • Guide
    • Documentation
    • Tutorials
    • Extensions
    • API
  • Makinom 1 Hub
    • Tutorials
    • Plugins
    • API
  • Support
  • Forum
  • Get Makinom
  • Contact
  • Blog
  • ORK Framework
  • gamingislove.com
Categories
  • Makinom 1 (97)
    • Tutorial (97)
      • 2D Platformer (14)
      • 2D Roguelike (8)
      • Breakout (6)
      • How-to (34)
      • Match 3 (6)
      • Schematic (4)
      • Scripting (6)
      • Space Shooter (11)
      • Survival Shooter (8)
  • News (11)
  • Release (68)
Search

© 2015 Gaming is Love e.U.

Disclosure: This site may contain affiliate links, which means I may receive a commission if you click a link and purchase something that I have recommended. While clicking these links won’t cost you any money, they will help me fund my development projects while recommending great assets!