HTSW v1.0.3 (VS Code v2.1.3)

HTSW now recognizes all 689 sounds currently shown in Housing's sound picker. Newer sound selections export as valid sound keys, preventing invalid HTSL and recurring false differences after imports.

HTSW v1.0.2 (VS Code v2.1.2)

Fixed exports failing when a Remove Item action has no item selected. Unconfigured actions now export as , so htsw check clearly flags them.

HTSW v1.0.1 (VS Code v2.1.1)

Fixed VS Code error messages dropping diagnostic labels.

HTSW v1.0.0 (VS Code v2.1.0)

What should I download?

What you want	Download or command
In-game Housing importer	HTSW.zip
VS Code editing tools	htsw-plus-plus-2.1.0.vsix
Command-line checker and simulator	Use the installer command below

In-game mod (Minecraft 1.8.9)

1. Install ChatTriggers.
2. Download HTSW.zip.
3. Extract it into your Minecraft instance's config/ChatTriggers/modules/ folder.
4. Confirm the resulting path is config/ChatTriggers/modules/HTSW/metadata.json.
5. Start Minecraft or run /ct reload if it is already open.

VS Code extension

1. Download htsw-plus-plus-2.1.0.vsix.
2. In VS Code, open Extensions, select the ... menu, then choose Install from VSIX....
3. Select the downloaded file and reload VS Code when prompted.

CLI (optional)

Install Node.js 20 or newer first.

macOS, Linux, or Git Bash:

curl -fsSL https://legendarygames.dev/htsw/cli/install.sh | sh

Windows PowerShell:

irm https://legendarygames.dev/htsw/cli/install.ps1 | iex

The installer verifies the download and installs htsw into ~/.local/bin. Update it later with htsw upgrade.

What are the other assets?

• htsw-ct-1.0.0.zip is the package used by HTSW's automatic in-game updater. Use HTSW.zip for manual installation.
• htsw-cli-1.3.15.mjs is the CLI payload fetched by the installer.
• htsw-*-latest.json files are machine-readable update manifests.
• install.sh and install.ps1 are downloadable copies of the CLI installers used by the commands above.
• LICENSE.txt and THIRD_PARTY_NOTICES.txt contain licensing information.
• GitHub generates the two source-code archives automatically; they are not installers.

HTSW 1.0.0

HTSW is officially stable. This is the first production release of the complete Housing workflow across the language, CLI, VS Code tooling, and ChatTriggers importer.

• Distribution packages now carry consistent licensing and third-party notices.
• Diagnostics infrastructure now has stricter upload validation, rate limits, storage limits, and safer file handling.
• Package, CI, documentation, and release tooling have been reorganized so each surface builds and verifies independently.

HTSW v0.14.0 Beta (VS Code v2.1.0)

HTSW 0.14.0

• NPC imports can now set Look at Players, Hide Name Tag, and skin. NPC equipment remains intentionally unsupported; declaring it stops that NPC before any Housing changes are applied.
• Function imports and exports now support descriptions, including clearing an existing description.
• Region bounds are now required consistently by validation, simulation, and live import.
• Auto-Track now reconciles its queue as tracked projects change, and bound-house cleanup keeps tabs, sources, and export destinations in sync.
• Diagnostic sharing now asks for consent before uploading error or performance reports and can be changed from settings.
• Fixed item comparisons after restored parse snapshots and stopped empty server-stripped lore from causing false item changes.
• Replaced the partial importables guide with a generated, complete reference covering every importable type and shared import behavior.

VS Code 2.1.0

• The project explorer can create linked starter HTSL files while adding functions, events, commands, regions, and NPCs.
• Standalone HTSL files now appear in a dedicated, searchable project-tree section with folders, Git decorations, and direct file opening.
• Clicking anywhere on a standalone-HTSL group or folder row now expands or collapses it.
• Added dedicated VS Code extension and CLI tooling documentation.

CLI 1.3.15

• Update checks now stay silent in non-interactive commands and only show an upgrade notice immediately after a fresh check, avoiding repeated notices from the cache.

HTSW v0.13.2 Beta (VS Code v2.0.1)

HTSW 0.13.2

• Made overlay scrolling reliable when Forge and render input arrive in either order, without double-scrolling or passing handled wheel input through to Minecraft.
• Kept long input hints inside their fields instead of drawing over neighboring controls.
• Kept house-lock item snapshots faithful to captured live data instead of filling missing captures from source files.

CLI 1.3.14

• htsw check and htsw run now tell you when a newer CLI is available and point you to htsw upgrade.
• Update checks are cached for 24 hours and never prevent commands from running when offline.

The VS Code extension remains at 2.0.1, and the HTSW language package is unchanged in this release.

HTSW v0.13.1 Beta (VS Code v2.0.1)

HTSW 0.13.1

• Fixed HTSW failing to load after updating to 0.13.0 and running /ct reload.
• Kept the import-reliability improvements from 0.13.0 while making the decimal comparison compatible with ChatTriggers.

HTSW v0.13.0 Beta (VS Code v2.0.1)

HTSW 0.13.0

• Improved import reliability: fixed several cases where imports could re-edit actions that hadn't changed, and false "Housing changed since last import" warnings.
• Item fields now accept vanilla item names like white_wool, red_wool, or lime_stained_clay directly — no need to declare plain vanilla items in your project. See the vanilla item names reference in the docs.
• Faster imports when an action changed heavily: the importer rebuilds it instead of editing field by field when that's quicker.
• The live import view shows faded change markers on lines with planned changes before they're applied.
• Chat typed while an import has Housing's value prompt open is held and sent after the prompt closes instead of being lost.
• New debug tools: /htsw debug codeview records the live import view into a shareable replay, and /htsw debug diffcapture records import comparisons for offline analysis.

HTSW v0.12.6 Beta (VS Code v2.0.1)

Improvements

• Housing conflicts are now much easier to review before importing. Choosing See changes keeps the live Housing snapshot without applying anything or updating house.lock.json, opens the changed code in the View tab, and writes htsw-diff/latest.diff with the project source, live Housing version, and last-import baseline when available. That file is designed so your coding agent can explain exactly what changed.
• The live import view now shows the operation HTSW is performing. Adds, edits, moves, and deletes have distinct markers, nested operations keep the correct focus, and a new follow button lets you pause or resume automatic scrolling. Scanning and hydration progress are also separated more accurately, with less misleading phase and ETA output.
• Slow-project diagnostics now identify where parse time is spent. Redacted reports break parsing into source loading, file checks, hashing, snapshot work, callback delay, and derived indexes, while session diagnostics retain more useful context for tracking memory or performance problems.

Fixes

• Messages typed during a Housing chat-value prompt are no longer mistaken for the imported value. HTSW temporarily queues your unrelated chat, sends its own prompt value, then replays your messages in order after the prompt closes. It also prevents import-overlay scrolling from changing the hotbar during the no-menu prompt gap.

HTSW v0.12.5 Beta (VS Code v2.0.1)

Fixes

• Exporting actions and conditions that hold a custom item works again. Hypixel renames the item preview shown in condition editors (like Has Item), which made HTSW unable to recognize the item it was capturing - exports failed with "can't capture item", and a failed capture could leave items missing from your inventory. HTSW now reads the item from the copy Housing places in your inventory instead of the preview, and it no longer deletes matching stacks from your inventory first, so there is nothing left to lose if something goes wrong mid-export.
• Failed exports and deep reads now upload a diagnostic report, the same way failed imports already did. If an export breaks for you, the details reach us automatically - no video needed. Cancelling a task does not upload anything.