Containers Window

Your whole pack as one collapsible tree — every bag, every nested pouch, with weights and capacities lined up in a column so you can see which container is about to overflow.

What it’s for

You know roughly what you’re carrying. What you don’t know is which of your five bags the spare gems went into, or which one is 2 lbs from full. Asking the game means a command per container and a screenful of scrollback per answer.

A containers window answers all of it at once. It takes one structured snapshot of everything you own, draws it as a tree you can open and close, and prints each container’s item count, carried weight, and capacity in aligned columns. A bag past 90% of its capacity turns its weight red — you see the problem before you try to stow anything.

⚠️ This is not the Container Windows widget (singular container). That one opens a separate window per bag, session-only, and you turn each bag on by ticking its row. This page is containers (plural): one window holding the whole inventory as a tree. They have similar names and do different jobs. If you want a dedicated window pinned to your gem pouch, you want the other page.

Set it up

Common setups

A “what’s in which bag” column you refresh once per stop

The tree is a snapshot, not a live feed, so it pays to treat it like a map you re-draw when you arrive somewhere rather than something you watch.

1. Add Containers from the catalog’s Character group and send it to a tall zone — the Right Bar suits a 20-row window.
2. Sync once when you sit down to sort loot: click ⟳ Refresh, or type .invsync.
3. Collapse the bags you don’t care about. Only the bag you’re working out of stays open.

You’ll see: one column where every bag you own shows its item count and its weight against its capacity, and the bag you’re filling turns its weight amber as it crosses 70% and red past 90%.

Digging through one bag without the rest in the way

1. In the GUI, right-click the bag you’re working out of and choose Focus.
2. The window swaps to that bag alone — its whole subtree flattened and sorted by name, with a header reading <bag name> — 34 items · 41.2 lbs. Anything nested deeper than the bag itself gets · in <holder> appended so you know which inner pouch it sits in.
3. Click ◀ All containers to come back.

You’ll see: one alphabetical list of everything inside that bag and nothing else on screen, with each entry’s weight in parentheses.

Tips & gotchas

⚠️ Without the extended feed the window stays empty forever, and it is not broken. .invsync asks the game a question only the extended feed answers, and the game only opens that feed for a client that sent the WRAYTH banner. Direct mode sends it; Lich can too. Connect some other way and .invsync prints its request line, the server never replies, and you are left looking at no snapshot yet. This is the single most common reason this window looks dead. The window says so itself, under the empty state.

⚠️ There is no auto-refresh, and that is deliberate. The window is read-only over the last snapshot. Pick something up, drop something, or stow a gem, and the tree does not notice — it keeps showing the world as it was at the last sync. Refresh when you want the truth.

⚠️ Two syncs cannot overlap. Ask for a second refresh while one is running and you get [invsync] refresh already in progress. and nothing else happens. Wait for the first to finish.

⚠️ Room items disappear when you walk away, on purpose. The snapshot records which room it was taken in. Move to a different room and the Room containers and On the ground sections are suppressed, because they describe scenery you have left. The GUI says Room items are from another room - Refresh here to load them.; the TUI says room items omitted (synced elsewhere - .invsync). Sync again where you are standing.

⚠️ The terminal build shows the tree and nothing more. Clicking, the verb menu, Focus, the Item inspector tab, and the ⟳ Refresh button are all GUI-only. In the TUI you drive everything from the command line with .invsync, .viewitem, and .drag.

A snapshot can be incomplete. Both frontends say so — the GUI header appends (incomplete) after the item count, the TUI puts , incomplete in the title. It means the continuation-following did not reach the end. Refresh again.

Locked containers report locked where the count would be. The game does not tell you what is inside a container you cannot open, so the window does not guess.

Item actions go through .drag, which waits for proof. Right-click ▸ To right hand, To left hand, Drop, and Wear each fire a .drag that is confirmed against your hand updates rather than against prose. A move that the game silently refused does not report success.

Left-clicking an item jumps to the Item tab. In the GUI, clicking any non-container row runs .viewitem for it and switches the window to the Item tab, where the look, inspect, analyze, and read results stack under their own headings. Right-click ▸ Inspect does the same.

Collapsed is the default. Every container row starts closed the first time you see it, so a large inventory opens as a short list of bags rather than a wall of gems.

Weight columns use one decimal on every row — item rows included — so the decimal points form a single rail down the window and you can compare two bags by eye.

.find <name fragment> searches the snapshot and prints each match’s container path, with closed containers flagged. It reads the same snapshot this window draws, so run .invsync first.

See also

• Container Windows (per-bag) — the singular container widget: one window per bag
• Inventory Tools — .invsync, .find, .viewitem, and .drag in full
• Inventory — the plain carried-items feed
• Reserve — what the game is holding aside for you
• Items — what’s on the ground rather than what’s yours

[[windows]]
name = "containers"
widget_type = "containers"
row = 0
col = 100
rows = 20
cols = 40
show_border = true
title = "Containers"