Neo Angband v1.1.0

What you can download

Platform	File
Windows (installer)	Neo Angband Setup 1.1.0.exe
Windows (portable, one file)	Neo Angband-1.1.0-portable.exe
macOS	.dmg, or the .zip if you prefer to unpack it yourself
Linux	.AppImage (no install), .deb, or .tar.gz
Self-hosting	neo-angband-web-1.1.0.zip - static files, any web server

The portable Windows build and the AppImage need no installer: download, run, and the game keeps its saves in a folder beside itself.

These builds are not code-signed

There is no Apple Developer identity or Windows certificate behind this project yet, so your OS blocks the first launch.

Windows is one click: SmartScreen says “Windows protected your PC”, choose More info then Run anyway.

macOS is not one click, and the dialog it shows you does not contain the way through - it offers only Done and Move to Trash. Do this:

1. Drag the app out of the .dmg, then double-click it and press Done on the refusal. This step is required: it is what makes the permission below appear, and it expires about an hour later.
2. Open System Settings -> Privacy & Security and scroll to Security, near the bottom.
3. Press Open Anyway on the line naming Neo Angband, authenticate, and launch it again.

Or, the same decision in one command: xattr -d com.apple.quarantine "/Applications/Neo Angband.app"

The old right-click -> Open trick does NOT work: Apple removed that bypass in macOS 15 Sequoia.

On Apple Silicon take the arm64 build. The x64 one is for Intel Macs, not a fallback - Apple is withdrawing Rosetta 2, so on a current Mac it is likelier to refuse to launch than to run slowly.

If that trade is not one you want to make, build it yourself - docs/INSTALL.md - or play in the browser, which needs no trust decision.

Your save

Saves survive an update. Every save-format change ships the conversion that reads the version before it, and a save this build cannot open is left untouched rather than replaced.

---

Current state of the project at version 1.1.0 - mods can now reach the sidebar and play grid’s own display geometry, and mod settings are easier to navigate.

Added

• A display-geometry seam for mods: ctx.display.snapshot() and a runtime grid/camera/map-view/sidebar/tile-scaling control surface (GlyphTerm.setReflow, setGrid, setCamera, setMapView, setSidebarExtent, setTileScaling, repaint), plus a capture-phase key subscription mods can use for their own display controls. Deliberately policy-free: no zoom steps, no persistence, no gesture handling, and no UI - a mod builds those on top, the same “necessary in core, nice is a mod” split every other seam in this project follows. Automatic camera re-clamping after a resize is included, so a mod does not have to re-derive it.
• The standard Options (=) menu gained a Mod options entry: an “All mods” flat list of every installed mod’s settings, plus one entry per mod. The recommended-mods flow gained a single bulk action (enable/update all recommended mods, with an explicit follow-up choice about turning their options on too) instead of working through each mod by hand, and capability approvals for a batch now happen on one screen.
• @rpgm-tools/neo-angband-mod-sdk now packages the real mod-authoring documentation, including the beginner tutorials and API references, under docs/. The package generates that copy from docs/modding/ when it builds or packs, so the repository documentation remains the single source of truth.

Changed

• The Mods screen’s “Fixes & tweaks” and “Parts of this mod” are merged into one “Mod options” entry, matching the new = menu entry above.

Fixed

• The “Update installed mods” screen showed a mod’s internal codename instead of its real display name (neo-angband#132).
• A character that had ever handed the keyboard to an autoplayer mod (even once, even long ago) no longer silently resumes under its control on every later, unrelated boot. The warn-and-confirm prompt now runs every time, except on the one reload that immediately follows an explicit “yes” (neo-angband#138).

---

Found something that does not match Angband 4.2.6? Open an issue or come and say so in the Discord.