---
layout: "docs_machine_readable"
page_title: "General Types - Machine-Readable Reference"
description: |-
  These are the machine-readable types that can appear in almost any machine-readable output and are provided by Packer core itself.
---

# General Types

These are the machine-readable types that can appear in almost any
machine-readable output and are provided by Packer core itself.

<dl>
	<dt>ui (2)</dt>
	<dd>
		<p>
		Specifies the output and type of output that would've normally
		gone to the console if Packer wasn't running in human-readable
		mode.
		</p>

		<p>
		<strong>Data 1: type</strong> - The type of UI message that would've
		been outputted. Can be "say", "message", or "error".
		</p>
		<p>
		<strong>Data 2: output</strong> - The UI message that would have
		been outputted.
		</p>
	</dd>
</dl>

---
layout: "docs_machine_readable"
page_title: "General Types - Machine-Readable Reference"
description: |-
  These are the machine-readable types that can appear in almost any machine-readable output and are provided by Packer core itself.
---

# General Types

These are the machine-readable types that can appear in almost any
machine-readable output and are provided by Packer core itself.

<dl>
	<dt>ui (2)</dt>
	<dd>
		<p>
		Specifies the output and type of output that would've normally
		gone to the console if Packer were running in human-readable
		mode.
		</p>

		<p>
		<strong>Data 1: type</strong> - The type of UI message that would've
		been outputted. Can be "say", "message", or "error".
		</p>
		<p>
		<strong>Data 2: output</strong> - The UI message that would have
		been outputted.
		</p>
	</dd>
</dl>

Fix statement in machine-readable 'ui' type docs.
Fix statement in machine-readable 'ui' type docs.

The text previously stated that "ui"-type messages represent messages that would be shown if Packer is *not* running in human-readable mode.

This is rather talking about what would happen when Packer *is* using human-readable mode.