Gaugeworks: Health, Shield, Mana and Stamina Bar Kit
README.md
barsKit 1.4.7
Health and resource bars for any world: one kit, lots of looks. You pick a look and say what the bar shows. To change the look later you change one word, live, and nothing else gets rewritten.
- 21 looks of its own, plus Lifeline's 13 as
lifeline:<style>, in 8 theme families: sci-fi, fantasy, cartoon, pixel, minimal, realistic, horror and cozy. Each look says its shape, whether it is a screen or world bar, and its size, so you can pick one without trying them all. - Works with the SecondWind health kit (formerly healthKit) out of the box: your health, shield, armour, hearts and lives, and the health of any enemy, NPC or prop.
- Not tied to health: it can show stamina, mana, energy, XP, a boss, or any number your game keeps. The
Resourcecomponent gives you a pool that drains and refills if you don't have one yet. - Feels good: the value eases to its new level, the lost chunk lingers as a ghost before draining, the bar pulses when low, numbers are optional, and each kind of resource has sensible colours.
- Fits any screen: the HUD scales with the screen and respects safe areas, so it stays readable on a phone as well as a desktop. Bars never leave the screen, and the gallery or a panel of yours and the HUD never cover each other.
- Leaves nothing behind:
BK.removetakes a bar down along with the entity it was made on, and closing or removing the gallery takes its screens with it. - Multiplayer: your HUD bars always show your body. Bars over other players, enemies and props read synced SecondWind health, so everyone sees the same value.
- Two guides inside: How to add a health bar to my game (what the pieces are and what to do first) and Health bar above enemies and a stamina bar for my game (a small game from an empty world, step by step). Both install with the kit, in
barsKit.package/guides/.
It depends on SecondWind (the health kit formerly called healthKit; 1.2.0 or later; built and tested on 1.4.4, which a new install gets) and, through it, Lifeline 1.0.1 and MatchFlow. They install with it.
Install and use
Install the package into your world with zeromind_install (search ZeroMind for "barsKit"). SecondWind, Lifeline and MatchFlow come with it. You can install SecondWind yourself as well, before or after barsKit, to have its README and guides at the top of your world: you still end up with one SecondWind, and the bars use it.
New to the kit? Read the guide How to add a health bar to my game (barsKit.package/guides/how-to-add-a-health-bar-to-my-game) first, or follow Health bar above enemies and a stamina bar for my game (barsKit.package/guides/health-bar-above-enemies-and-a-stamina-bar-for-my-game) to build a small game with a health bar, enemy bars and a sprint stamina bar.
1. Give your player health first
A health bar shows the health the health kit keeps, so the player's body needs health before any health, shield, armour, hearts or lives bar can show anything. Without it, the bar finds no health to read and is hidden entirely. You get no error, just no bar. The same goes for an enemy or prop you put a bar on.
The health kit installs with barsKit. It is SecondWind (it used to be called healthKit: same package, same guid). Installed with barsKit alone it sits in deps/7a497fbf-1b4e-4655-8abf-e588fa7caa5c/SecondWind.package; installed by you as well, it moves to the top of your world. Either way, reach it by its short name, SecondWind.Vitals or SecondWind.api, as below. (The old name healthKit.api doesn't exist in a new world.)
Add these lines to your scene's build.luau, inside content(), after the default player setup (body is the player body it makes):
-- the health kit (SecondWind, formerly healthKit)
local VITALS = asset.resolve("SecondWind.Vitals", "component")
body.component.add(VITALS, { maxHealth = 100 }) -- every joining player gets health
-- or with a regenerating shield, the way this world's own scene does it:
-- body.component.add(VITALS, { model = "shield", maxHealth = 100, maxShield = 40 })
-- anything else that should have a health bar: here, an enemy to hit
local enemy = entity.spawnSynced("Grunt")
enemy.component.add("Asset", { source = asset.resolve("@builtin::avatars.humanoid", "avatar") })
enemy.localPosition = { 0, 0, 6 }
enemy.component.add(VITALS, { maxHealth = 250, displayName = "Grunt" })
Adding the Vitals component gives the entity SecondWind's health and Lifeline's Health with it. In build.luau, add the component as above rather than calling HK.attach: the scene rebuilds every time you edit the file, and a second HK.attach on the same body stops the rebuild with "already has a Vitals component". From game code that runs while you play, use the API: local HK = require("SecondWind.api"), then HK.attach(entity, { ... }), HK.damage(...) and HK.heal(...). See the SecondWind README for health models (hitPoints, shield, armor, hearts, lives), death styles and teams.
To check it worked, press Play: require("barsKit.api").read("health", entity.find("Grunt")).ok is true and its max is 250. (In edit mode SecondWind hasn't started yet, so max can read the default 100.)
If your game keeps its own health instead of using SecondWind, skip this step and point the bar at your number (show = "value" with bar:set, or BK.bind; see Pointing a bar at something). Stamina and mana bars need a Resource instead (see No stamina or mana yet?).
2. Put bars on screen
This is game code: it runs while you play. Put it in your scene's entrypoint.luau, inside localPlayerReady (uncomment the function there), so it runs once your player is in the game:
function localPlayerReady(player)
local BK = require("barsKit.api")
local enemy = entity.find("Grunt") -- the enemy from step 1
-- your health in the top-left corner
local hp = BK.bar({ look = "ghost", show = "health" })
-- a little bar over the enemy's head (the enemy needs health too, step 1)
BK.bar(enemy, { look = "overhead" })
-- a boss plate across the top, for the same enemy
BK.bar({ look = "boss", target = "Grunt", anchor = "topCenter", phases = "0.66 0.33" })
-- switch the look: one word, live
BK.setLook(hp, "pixel")
BK.setLookAll("hologram") -- every bar at once
BK.setLookAll("ornate", { placement = "screen" }) -- just the HUD
end
Bars that are always there (your HUD, the bar over every enemy) can live in the scene instead, added in build.luau like the health: entity.spawn("HealthBar").component.add(asset.resolve("barsKit.Bar", "component"), { look = "ghost", show = "health" }), or enemy.component.add(asset.resolve("barsKit.Bar", "component"), { look = "overhead", placement = "world" }). Every field below is also settable in the editor's inspector, and changing look there redraws the bar at once.
Pointing a bar at something
show says what the bar shows, and target says whose it is. With no target, a screen bar reads the local player and a world bar reads the entity it sits on.
show | reads |
|---|---|
health (default) | SecondWind health (works on players, enemies and props) |
shield, armor, hearts, lives | the matching SecondWind value |
stamina, mana, xp, anything else | the Resource of that name on the target |
value | a number you set with bar:set(value, max) |
You can also bind any function, or point at any component field:
BK.bind(bar, function() return myGame.energy, myGame.maxEnergy end)
BK.bind(bar, { component = "Turret", field = "heat", max = 100 }) -- or maxField = "maxHeat"
BK.bar({ look = "segmented", show = "value", kind = "ammo" }):set(12, 30)
No stamina or mana yet? Make a resource
BK.resource(player, "stamina", { max = 100, regenRate = 25, regenDelay = 0.8, drainRate = 35, drainKey = "ShiftLeft" })
BK.resource(player, "mana", { max = 120, regenRate = 8 })
if BK.spend(player, "mana", 30) then castFireball() end -- false (and nothing spent) when there isn't enough
BK.gain(player, "mana", 10)
BK.bar({ look = "orb", show = "mana", anchor = "bottomRight" })
A Resource regenerates after regenDelay seconds without spending, and drains while drainKey is held or draining is true. demo = true makes it drain and refill on its own, for showcases. The owner of the entity is the authority; other peers' spend/gain calls are sent to it, and the value syncs to everyone.
Note: a second Resource on one entity is a named component instance. On player avatars, add it at runtime with BK.resource(...) (for example in localPlayerReady) rather than on the PlayerPrototype, because named second instances don't carry over when the prototype is cloned.
The looks
Where is screen (HUD only), world (over an entity only) or both. Size is the HUD size in points at scale 1, and the size class is in brackets: small, medium, wide or tall.
| id | name | shape | where | size | families | suits |
|---|---|---|---|---|---|---|
line | Thin line | line | both | 240×22 (medium) | minimal | health, stamina, xp, energy |
segmented | Segmented | segmented | both | 264×36 (medium) | realistic, sci-fi | health, armor, energy, ammo |
ring | Radial ring | ring | both | 88×88 (small) | sci-fi, minimal | health, shield, energy, cooldown |
hearts | Heart containers (full, half and empty; blue shield hearts) | hearts | both | 180×52 (medium) | fantasy, cozy, pixel | health, lives, hearts |
boss | Boss bar (name, phase marks, phase count) | bar | screen | 560×62 (wide) | fantasy, horror, realistic | boss |
overhead | Over-head bar | bar | world | 180×34 (medium) | minimal, realistic | overhead, enemy, npc |
pip | Unit pip | bar | world | 30×5 (small) | minimal | overhead, unit, rts, health |
ghost | Ghost bar (the lost chunk lingers, then drains) | bar | both | 280×30 (medium) | realistic, minimal | health, boss, shield |
stacked | Shield on health | stacked | both | 272×44 (medium) | sci-fi, realistic | health, shield, armor |
arc | Crosshair arc | arc | screen | 76×76 (small) | minimal, sci-fi | stamina, energy, ammo, crosshair |
orb | Glass orb | orb | screen | 108×126 (small) | fantasy, realistic | mana, health, energy |
gauge | Vertical gauge | vertical | screen | 58×176 (tall) | realistic, sci-fi | fuel, heat, oxygen, energy |
pips | Pips / dots | pips | both | 194×32 (medium) | minimal, cozy, cartoon | lives, charges, ammo, combo |
pixel | Pixel art | bar | both | 248×34 (medium) | pixel, cartoon | health, mana, stamina, xp |
hologram | Sci-fi hologram | bar | both | 300×52 (medium) | sci-fi | shield, energy, oxygen |
ornate | Ornate fantasy frame | bar | both | 312×50 (medium) | fantasy | health, mana, boss |
bubbly | Bubbly cartoon | bar | both | 272×46 (medium) | cartoon, cozy | health, xp, stamina |
blood | Blood vial (drips, flickers near death) | bar | both | 270×48 (medium) | horror | health, sanity, boss |
monitor | Heart monitor (ECG that flatlines at zero) | trace | screen | 214×62 (medium) | realistic, horror, sci-fi | health, stress |
stitched | Stitched felt | bar | both | 262×44 (medium) | cozy, cartoon | health, hunger, warmth |
megabar | Tick column (retro platformer meter) | vertical | screen | 30×150 (tall) | pixel, cartoon | health, energy, weapon, boss |
The eleven shapes are line, bar, segmented, stacked, ring, arc, hearts, pips, orb, vertical and trace.
Lifeline's own styles are there too, each with the same labels: lifeline:classic, segmented, ring, hearts, boss, overhead, minimal, stacked, scifi, fantasy, cartoon, pixel, orb.
Asking the kit
BK.looks() -- every look: { id, name, families, suits, description,
-- shape, placement, size = { w, h }, worldSize = { w, h }, sizeClass }
BK.looks({ family = "horror" }) -- blood, monitor, boss
BK.looks({ suits = "mana" }) -- orb, pixel, ornate
BK.looks({ family = "cozy", suits = "health" })
BK.looks({ placement = "world" }) -- looks that can float over an entity ("both" counts)
BK.looks({ size = "small" }) -- ring, pip, arc, orb (or "medium", "wide", "tall")
BK.looks({ shape = { "ring", "arc" } }) -- one shape or several
BK.looks({ family = "pixel", shape = "bar" }) -- filters combine
BK.looks({ includeLifeline = true })
BK.families() -- { { id, name, looks } } for the 8 families
BK.shapes() -- { { id, name, looks } } for the 11 shapes
BK.suits() -- everything looks say they suit
BK.render("orb", { frac = 0.4, kind = "mana" }) -- draw a look inside your own UI tree
Bar fields
| field | default | what it does |
|---|---|---|
look | ghost | Which look. Change it any time. |
show | health | What it shows (see above). |
target | (empty) | Whose value: an entity name or id. Empty means the local player (screen) or this entity (world). |
placement | screen | screen = HUD; world = floats over the target. |
anchor | topLeft | Screen corner or edge: topLeft, topCenter, topRight, left, center, right, bottomLeft, bottomCenter, bottomRight, crosshair. Bars on one anchor stack by order. |
label | (empty) | Caption. Defaults to the resource's name (or the boss's name). |
kind / color | auto | Colour by resource kind (health, shield, armor, stamina, mana, energy, xp, boss, rage, oxygen, heat, ammo, lives, hunger, generic), or a hex override. |
numbers | auto | value (75 / 100), percent, none or auto. |
lowWarning | 0.25 | Below this fraction the bar pulses. 0 turns it off. |
size | 1 | Scale on top of the screen-size scale. |
phases | (empty) | Boss phase marks as fractions, e.g. "0.66 0.33". |
segments | auto | Cell, pip or heart count, where the look uses one. |
worldHeight, range | 2.2, 30 | World bars: height above the target, and how far from the camera they still show. |
hideWhenFull, hideOwn | false, true | Hide while full; don't draw a world bar over your own body. |
offsetX, offsetY, visible | Fine placement and on/off. |
Methods on a Bar (call them with a colon): bar:setLook(id), bar:cycleLook(dir), bar:bind(fn | spec), bar:set(value, max), bar:sample(). On a Resource: res:spend(n), res:gain(n), res:set(v), res:fraction(). The API mirrors them: BK.setLook, BK.bind, BK.sample, BK.read(show, target), BK.bars(), BK.barOf(entity), BK.localPlayer().
Multiplayer
- Bar settings are local (not synced). Each peer runs its own HUD, so your screen bars always read your avatar.
- World bars and boss bars read SecondWind's synced state, so every player sees the same value over the same enemy.
Resourcevalues are owned by the entity's owner and synced.BK.spend/BK.gainfrom another peer are sent to the owner.- Damage and healing go through SecondWind (
HK.damage,HK.heal), which already routes them to the authority.
The gallery (barsKit.Showcase)
Add the Showcase component to any entity to get the gallery:
- Every look side by side, all following one value that drains and refills. Each card is labelled with the look's name, its id and families, and a gold line giving its shape, where it goes and its size.
- Filter chips for families, recolour chips for resource kinds, a numbers toggle, and Lifeline's looks.
- A switcher that flips your own health bar through every look. Use
[/]or the ◀ ▶ buttons;Ghides or shows the gallery.
The gallery and the HUD never cover each other, at any screen size:
- The panel takes the largest part of the screen the HUD leaves free (
BK.freeRect), clear of every screen bar and the touch buttons. - While the gallery is open the switcher sits inside it. When it is closed, the switcher stands alone and screen bars step clear of it.
- Bars that would land under the panel (the crosshair arc, world bars) are hidden until it closes.
- Cards are dealt into even rows. Rows differ by at most one card, and every row is stretched to fill the width, so there are no empty spots.
On a desktop-sized window, every look and its label is on screen at once, with no scrolling. The gallery tries every column count from 3 to 8, splits the panel's height evenly between the rows, and picks the grid that draws the looks largest without shrinking any one of them too far (BK.layout.fitGrid). A 1080p window and a shorter 1280×682 window both come out as three rows of seven. The cards get compact there: the family line shortens or drops families ("+2") instead of being cut off. A panel too small to fit every card at a readable size scrolls instead, with the larger cards. That covers a phone in either orientation, where the touch buttons and the boss plate leave the gallery a small panel. On a phone the cards reflow to two columns, and a card's labels shorten rather than get cut off.
local g = entity.find("BarsGallery").component.get(asset.resolve("barsKit.Showcase", "component"))
g:gridInfo() -- the grid it drew last: { fits, scrolls, cols, rows, cellH, gridH, minScale, cards, panel }
g:layoutFor(1920, 1080) -- lay it out for another screen size without drawing: info, widget tree
G toggles the gallery, as does setting the component's open field. Removing the component or despawning its entity takes down both of its screens.
Phones and touch screens
- Bars scale with the screen but never drop below 0.85 on a phone, so text stays legible.
- Corner bars are laid out first. A centred bar (a boss bar) that meets one first slides sideways, and only then steps a row down (or up, for a bottom bar), so nothing overlaps on a narrow screen.
- A bar never leaves the screen. On a tiny screen with no clear row left, it shrinks into the widest gap of a row it tried.
- While the player is on touch, screen bars step clear of the on-screen buttons (Jump, Sprint, …). Top stacks move down past them and bottom stacks move up.
- World bars (over heads) draw under screen bars, with the nearest on top.
Your own panels and the HUD
All of these use UI points, the same space as ui.screenSize(). Pass nil as the rect to clear a key.
-- keep screen bars out of a rect (a minimap, a chat box): the bars move
BK.keepOut("minimap", { x = 1100, y = 10, w = 170, h = 170 })
-- a panel of yours covers a rect (an inventory): bars that would land under it are hidden until you clear it
BK.cover("inventory", rect)
-- or let the HUD tell you where there is room: the largest rect clear of every bar, touch button and keepOut
local sz = ui.screenSize()
local rect = BK.freeRect(sz.width, sz.height, { pad = 8, margin = 6, minW = 300, minH = 200 })
BK.screenRects() -- where the HUD drew its screen bars last frame: { { x, y, w, h, anchor, look, hidden } }
BK.layout -- the pure helpers the gallery uses: largestFree, evenRows, rowWidths, packLines, fitGrid, overlaps
Removing bars
local hp = BK.bar({ look = "ghost", show = "health" }) -- makes an entity for the bar
BK.remove(hp) -- removes the bar and despawns that entity; true when it took a bar down
BK.remove(hp) -- false: the bar is already gone (calling it again is harmless)
local tag = BK.bar(enemy, { look = "overhead" })
BK.remove(tag) -- removes only the Bar component; the enemy stays
BK.unbind(bar) -- undo BK.bind: the bar goes back to its `show` field
BK.isBound(bar) -- is a function or field spec bound right now?
Removing a Bar component by hand, despawning its entity or removing a Resource cleans up the same way. No HUD entries, bindings, covers, keepOuts or screens stay behind; the tests check this.
Known limits
Checked on 2026-11-03 in the desktop app, on the current engine and built-in library: Gaugeworks itself, a brand-new world with only barsKit installed from ZeroMind, and a brand-new world with markersKit (which depends on barsKit). barsKit loaded in full and played with no script errors, the README's first example worked, and the tests passed in both places.
- barsKit 1.4.0 doesn't play in a new world (#20491): update to 1.4.1. 1.4.0 came in through a merged contribution, and that route loses the record of what scripts depend on. Its looks catalog, API and test suite came out with no dependencies listed, so a new install brought Lifeline without its bar styles, and pressing Play was refused with "could not resolve require(... Lifeline.bars)". 1.4.1 is published from this world's own main line, and those scripts list their dependencies again. Until #20491 is fixed, barsKit releases are published this way, never through a merged contribution.
- Web browser version: not checked for this release (#20946). An agent can't start a web browser engine itself, so the web check is done by someone else. 1.3.0 worked for one player in a web browser on 2026-10-18. The gallery's frame rate in the web browser version is tracked as #20750.
- Reinstalling after deleting (#19474). If you delete barsKit and its
deps/from a world and install it again there, the install is refused ("is not installed, because it does not run ... names a version this world holds nowhere"), andzmcan't bring the deleted files back either. Install into a fresh world instead.
Version
1.4.7. require("barsKit.api").VERSION. Tests: barsKit.testSuite, 70 tests (run with the tests toolbox).
-
1.4.7: SecondWind 1.4.7 (with MatchFlow 1.4.0 and Lifeline 1.0.4), the release abilitiesKit, weaponsKit, markersKit and arpgKit ship with, so a world holds one SecondWind and one MatchFlow; files naming SecondWind recorded again; current engine library; no bar code changed.
-
1.4.6: Lifeline 1.0.4 for the Lifeline looks, so an install no longer pins an older copy of Lifeline's bars module; no bar code changed.
-
1.4.5: SecondWind 1.4.5, so an install brings Lifeline 1.0.4 and the current MatchFlow instead of older copies; no bar code changed.
-
1.4.4: Its tests find the package's own files wherever it is installed (at /source, or under /source/deps when another package installs it). In a world where platformer3dKit installed it, 5 of its tests failed because they read README.md, package.yaml and source files from a fixed /source/barsKit.package path.
-
1.4.3: if you installed 1.4.0, 1.4.1 or 1.4.2, update. Pointing a bar at a field on a component (
show = { component = ..., field = ... }) now works in a new install: before, the bar came back empty (not ok, max 1), and the test suite reported 69 of 70 in every brand-new world. The cause: barsKit was published against an older SecondWind than the one a new install puts in your world, so a new world held SecondWind's health component at two releases, and the bar looked the component up by its short name, which reaches only one of them. 1.4.2's change to the test did not fix this; it only passed in a world where a file had been edited. barsKit is now built and published against SecondWind 1.4.4, the release a new install gets, so a new world holds one SecondWind; and a field spec reads the component instance it is given, falling back to the name and then to a matching component on the entity, so it finds the field whichever release the entity carries. No call or setting changed. -
1.4.2: if you installed 1.4.0 or 1.4.1, update. Fixes the test suite in a new world: one test looked SecondWind's health component up by its short name, which in a new install is a different release from the one the kit's own SecondWind calls attach, so it failed there (69 of 70) while passing in Gaugeworks. It now uses the component SecondWind's API attaches. The test suite also no longer lists the old
healthKit.apiname among its dependencies (it only checks that the name is gone). Everything 1.4.1 fixed is in it. No call or setting changed. -
1.4.1: if you installed 1.4.0, update. 1.4.0 came in through a merged contribution, and that route lost the record of what three of its scripts depend on (the looks catalog, the API and the test suite; engine issue #20491). A new install of 1.4.0 brought SecondWind without Lifeline's bar styles, and pressing Play was refused with "could not resolve require(... Lifeline.bars)". 1.4.1 is published from Gaugeworks' own main line, and those three scripts list what they depend on again. The
piplook now says it is a world bar everywhere: the catalog saidbothwhile this README saidworld. Every count now says 21 looks (the package description, the guide and the gallery scene still said 20), andBK.looks({ size = "small" })lists the pip. Every script passes the strict type check with no warnings. Two new tests check the pip, and that this README's looks table and every look count agree with the catalog. No call or setting changed. -
1.4.0: a
piplook, a tiny 30 by 5 bar for crowds (hundreds of RTS units or swarm enemies) that turns from green to yellow to red as they are hurt; draw it yourself withBK.render("pip", { frac = hp })over each unit, with no component per unit. The sources test names SecondWind's Vitals by its short name, so it passes wherever SecondWind is installed. -
1.3.1: two guides now ship inside the package: How to add a health bar to my game and Health bar above enemies and a stamina bar for my game (a small game from an empty world, followed step by step in a new world). The README uses SecondWind's short names (
SecondWind.Vitals,SecondWind.api), which now reach installed packages and keep working when you install SecondWind yourself as well; the old fulldeps.…names stopped resolving once SecondWind moved to the top of a world. The README's step 2 now says where its code goes and points the boss bar at the step 1 enemy. Known limits are re-checked on the current engine: #19201, #19260 and #19449 no longer happen and are gone from the list. Checked on SecondWind 1.3.1, which a new install now brings. No call or setting changed. -
1.3.0: the release where barsKit behaves differently: it runs on SecondWind 1.2.0 (formerly healthKit) and draws a backing plate behind numbers over bars. Both came in 1.2.1; this version number says so. No call or setting changed. Known limits now name the platform they were checked on (the desktop app; the 1.2.1 notes wrongly said the web browser version) and add #19449: a second
Resourceon one entity reaches other players mixed into the first. A new test checks that the version agrees inpackage.yaml,BK.VERSION, the README's title and its Version line. Heart containers now draw real heart shapes at 180×52, with all five hearts inside the card, even in a session where Lifeline's heart renderer has not loaded yet. It used to fall back to 100×46 solid red squares with the fifth one cut off, seen in the phone gallery. barsKit now keeps trying to load Lifeline's renderer and switches to it once it loads.BK.removenow returns false for a bar that is already gone, as documented; it used to return true again. Known limits describe what #19260 really leaves on a fresh install: old LifelineapiandHealthcopies and an old MatchFlowrulescopy. -
1.2.1: tidy-up release; no call or setting changed. barsKit now uses the health kit by the name a fresh install gives it: SecondWind 1.2.0 (formerly healthKit, same package and guid), loaded by its full name. Before this, barsKit and its README's first example failed to load in a new world. The first example now works pasted as-is into a new world with only barsKit installed, and keeps working when you edit the scene again. The gallery's sample value and screens run only while the gallery is placed on an entity and the game is playing, not when its script loads. The gallery panel and switcher are opaque, so nothing in the world shows through their labels. A number drawn on top of a bar (over-head, ghost, pixel art, ornate, bubbly) sits on a backing plate, so the pale ghost trail can't hide it. The heart monitor's readout lines no longer touch. Gallery components get
sample()andisRunning(). Known limits now list only what still happens on a fresh install. -
1.2.0: every look is on screen at once on desktop-sized windows, labelled and without scrolling: the gallery picks its column count and card size to fit the panel (
BK.layout.fitGrid,BK.layout.packLines), and addsgridInfo()andlayoutFor(). Phones scroll as before. The shared value, boss bar, overhead dummy, ghost bar and look switcher are unchanged. The README now says to give your player health first, and how, and lists the known limits. -
1.1.0: every look says its shape, where it goes (screen, world or both) and its size, and
BK.looksfilters on all three (BK.shapes()lists the shapes). The gallery places itself in the room the HUD leaves free and hides bars under it, keeps the switcher inside it while open, and deals cards into even rows. A centred bar slides sideways before stepping down and never leaves the screen, and world bars draw under screen bars. New:BK.remove,BK.unbind,BK.isBound,BK.cover,BK.screenRects,BK.freeRectandBK.layout. Removing a bar, unbinding or closing the gallery leaves nothing behind. -
1.0.2: lighter gallery: virtual scrolling (only the rows in view are laid out and painted), the look switcher is redrawn only when it changes, and the gallery rebuilds 20 times a second on phones (30 on desktop). On a phone the open gallery now costs about 3ms a frame instead of about 9.5ms.
-
1.0.1: phone layout: a legible minimum scale, no overlap between corner and centre bars, bars and the gallery keep clear of touch buttons, and
BK.keepOut. -
1.0.0: first release.