AmigaOS Version Badges

Many pages in this wiki carry a small badge such as 2.0+ or 3.2+. A badge tells you the first AmigaOS release in which the item is available. Items include functions, structure fields, constants, tags, packets and whole articles. Use the badge to decide whether your code needs a version check (OpenLibrary(name, version) or SysBase->LibNode.lib_Version) before using the item.

Badge values

Badge AmigaOS release Library version
1.3+ 1.3 or earlier V33–V34
2.0+ 2.0 V36
2.04+ 2.04 V37
2.1+ 2.1 (disk-only update) V38
3.0+ 3.0 V39
3.1+ 3.1 V40
3.5+ 3.5 / 3.9 V44
3.1.4+ 3.1.4 V45–V46
3.2+ 3.2, 3.2.x V47

The wiki covers AmigaOS 3.x, so material that exists only in later systems is not documented and carries no badge.

Where badges appear

  • Structure pages (library-reference/types/): each structure has a Since line. A field added after the structure itself has an inline marker such as [3.0+] at the end of its line. Fields without a marker are as old as their structure.
  • Autodoc pages (library-reference/): each function has a Since line under its heading, and the function index shows the badge next to each name.
  • Articles: in tables of functions, constants, tags and packets, the badge follows the symbol in the first column.
  • Index: articles about features of a particular release carry the badge next to their title.

How the badges were determined

The badges were computed by comparing four Native Developer Kits:

  1. NDK 1.3: Kickstart 1.3, V34.
  2. NDK 2.0: V36/V37.
  3. NDK 3.1: V40.
  4. NDK 3.2 Release 4: V45–V47, covering 3.1.4, 3.2 and 3.2.x.

For every symbol, the first NDK whose headers, FD or SFD files define it gives the base release. The base is then refined with the version tags the NDK itself states:

  • (V39) and similar tags on the NAME line of an autodoc;
  • New for V37 style comments next to a structure field or #define;
  • the ==version blocks of the 3.2 SFD files.

A tag is only used when it falls inside the range of NDKs between the last one that lacks the symbol and the first one that has it.

When no tag is available, the badge names the NDK release that first documents the symbol, which is a safe upper bound. For example, a constant first seen in NDK 3.1 with no V39 note is marked 3.1+, although it may already have worked under 3.0. The same applies between 3.1.4 and 3.2. Some symbols appeared in the system before the NDK documented them; for those, the badge reflects documentation, not the first ROM that contained them.

Structures that existed privately in 1.3 but were published later keep 1.3+, and their public fields are marked individually. struct GadgetInfo is an example.

See Also

Sources: NDK 1.3, NDK 2.0, NDK 3.1, NDK 3.2 R4 (headers, FD/SFD files, autodocs) Updated: 2026-11-13