core 2.3.0 API

Packages
Package
Description
Myriad's public API: what addons build on.
An addon's entrypoint (MyriadAddon), what it can register (AddonContext) and its own storage (AddonStorage).
The threading contract, as annotations on API types and methods: RenderThread (call it on the game's own thread only, the default for everything) and AnyThread (safe from any thread, or an event that may arrive off it).
Blueprints for Myriad.building(): describe a shape as Targets and the planner breaks and places what's in reach.
Combat helpers: finding targets, damage after armour, dangers around you, crystal placement and projectile paths.
Commands (Command, built on Brigadier) and argument types for them.
Argument types for commands: block positions, registry entries, modules, settings, players, durations and choices.
Profiles and saving (ConfigManager).
Control panels: named sets of modules switched together by one bind, each module optionally with settings it takes while the panel is on (Controls, Myriad.controls()).
Tools for developing and testing Myriad and addons, present only in dev runs.
Elytra flight: Elytra (Myriad.elytra()) with No Durability, chest swaps, the glide hold and pilots, shared by every flight module.
The event bus (Myriad.events()): Subscribe handlers on a subscribed object or class, lambda listeners, priorities and cancellable events.
Every event Myriad posts.
Hooks: places where an addon can change how Myriad (or another addon) behaves, without changing its code.
Keys and binds: Keybind (a key or mouse button with modifiers, as settings store it) and KeyAction (a named global key, registered with AddonContext.registerKeyAction).
Other mods, driven when they're installed and quietly absent when they're not, so a module can offer them to everyone without depending on them: Baritone.
Items: ItemInfo answers what features keep asking about a stack (enchantments, food, contents, durability, gear), ItemMatch says when two stacks are the same item for a layout, and Slots converts inventory indexes to menu slot ids.
Jobs: long-running work as Steps, run by Myriad.jobs() for a module, with a state, a reason when they're stuck (Why) and progress.
The map mods players fly by: waypoints from Xaero's Minimap, when it's installed (Myriad.maps()).
Help for addons' own mixins, such as mixins that only apply when another mod is installed.
Modules: toggleable features with settings, their tags and the groups they show in.
Talking to the server and the web: Packets sends packets (silently, or counted against the server's limits through Myriad.limits()), Http makes web requests off the render thread.
The local player's actions and reach, measured and done the way the server sees them: Interactions (use, attack, swing, the way vanilla does them), Reach (what you can reach and see, from the eyes), Movement (which way the keys point, speed along it) and Mining (break times as the server works them out).
Ids and registries: MyriadId names everything an addon registers (namespace:path, the namespace being its mod id), and a Registry lists one kind of thing (modules, commands, panels, themes...), read-only to addons, which register through their AddonContext.
Drawing in the world: highlights and the standard look options (RenderSettings, HighlightStyle, RenderMode), shapes for one frame (Renderer3D) or kept on the GPU (WorldMesh), merged boxes, fades, labels over the world, entity groups, ghosts and model shapes.
The services addons share instead of fighting over the same state: rotations, inventory, placing, breaking, building, containers, packet limits, tick speed, server facts, notifications, friends and enemies, and the anti-cheat profile.
Settings: typed, saved values grouped per module or panel, with the builders to declare them and SavedSettings to migrate them across versions.
Shared configs: a set of modules (and control panels, a theme) with their settings, turned into a short code (myriad_JS3k4d) others take in, or view on the website.
The UI: Myriad's tiling window manager, modelled on Hyprland.
2D drawing for panels, HUD elements and screens: the Canvas (shapes, gradients, shadows, frosted glass, text), its fonts (FontFamily, and ThemeFont for text Minecraft draws), animation helpers (Animated, Easing, Bezier) and the MyriadLogo.
HUD elements: panels that live on the UI's HUD workspace and are drawn in game, sized to their content.
Tiling layouts for workspaces: a Layout makes one LayoutState per workspace, which places its tiled windows.
Widgets for building panels (WidgetPanel): labels, buttons, toggles, sliders, text fields, pickers, foldable sections and the boxes that lay them out.
General helpers with no better home: threads and timing, colours, formatting, search and chat text.
The world around you: what blocks and entities are (BlockInfo, Entities), positions around a point (Positions), per-chunk caches and fast searches (ChunkCache, BlockScan), holes and surrounds (Holes), freshly generated chunks (ChunkAge) and dummy players for testing (FakePlayers).