# Install highball with Homebrew Cask

Tool to run Windows games. Version 0.10.23 via Homebrew Cask; verified from local package data.

## Install

```sh
sudo av install cask:highball
```

Additional install commands:

### macOS

- Homebrew Cask (100%):

```sh
brew install --cask highball
```

  Evidence: local Homebrew cask metadata

## Package facts

- **Package key:** cask:highball
- **Package manager:** Homebrew Cask
- **Package manager page:** <https://formulae.brew.sh/cask/highball>
- **Version:** 0.10.23
- **Source summary:** Tool to run Windows games
- **Homepage:** <https://github.com/gauthierpiarrette/highball>
- **Repository:** <https://github.com/gauthierpiarrette/highball>
- **Source archive:** <https://github.com/gauthierpiarrette/highball/releases/download/v0.10.23/Highball.dmg>
- **Generated:** 2026-11-04T12:20:42+00:00

## Install behavior

- Post-install hook: not defined
- Bottle: not available

## Freshness

- Page generated: 2026-11-04
- Package-manager version: 0.10.23
- Local data: ok
- Upstream repository: https://github.com/gauthierpiarrette/highball
- info: No package-manager update timestamp was available.
- info: No cached GitHub release or tag data was available.
## Project history and usage

Highball is a free, open-source native macOS application and CLI for creating Wine-based environments and running Windows games on Apple silicon. It combines managed compatibility engines with renderer recommendations from an open game database.

### Project history

Highball was designed as an open-source macOS app and CLI around HighballKit, Wine prefixes, interchangeable renderers, declarative recipes, and a separate compatibility database. Its README presents engine independence and public, reusable data as safeguards against the fragility of earlier Mac gaming wrappers.

### Adoption history

Highball targets Apple-silicon Mac users who want to run Windows games without being tied to a single Wine build. It combines a native macOS interface and CLI with Steam support, Epic integration through Legendary, and an open compatibility database.

Community game reports can be submitted with the CLI and incorporated into the separately maintained Highball database, where verified results, community reports, and predictions are distinguished.

### How it is used

Users install an engine, create a Wine environment from a recipe, install or connect a game launcher, and launch games with a database-recommended renderer. Advanced users can perform the same operations through the `highball` CLI.

The application stores its engines, environments, settings, and other runtime data under `~/Library/Application Support/Highball/`.

### Why package nerds care

Highball treats engines, renderer selection, recipes, and compatibility results as inspectable data. Engines are assembled from pinned upstream components, while game recipes and compatibility data are maintained separately under CC0.

Its explicit response to the 2025 archival of Whisky makes Highball especially relevant to Mac compatibility-layer enthusiasts concerned with project longevity, reproducibility, and reusable compatibility knowledge.

### Timeline

- 2025: Whisky was archived, an event Highball explicitly cites as a design caution for Mac gaming wrappers.

### Related projects

- Wine supplies the Windows compatibility layer.
- DXMT, D3DMetal, DXVK, and WineD3D provide alternative rendering paths.
- Legendary supplies Epic Games integration.
- highball-db stores recipes and compatibility reports.
- Whisky is cited by Highball as a related project whose 2025 archival influenced its design.

### Sources

- <https://github.com/gauthierpiarrette/highball>
- <https://github.com/gauthierpiarrette/highball/blob/main/CONTRIBUTING.md>
- <https://github.com/gauthierpiarrette/highball/security>


## Security Notes

No matching local secret-handling manifest was found for highball. Package metadata is still published here so future coverage has a stable package URL.



## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- macOS: ~/Library/Application Support/Highball/
## Source Database Details

- **Source Database:** Homebrew cask API
- **Tap:** homebrew/cask
- **Full Token:** highball
- **Names:** Highball
- **Depends On:** Arch: {'type': 'arm', 'bits': 64}, Macos: >=: 14
- **Artifacts:** App: 1, Target: 1, Zap: 1
- **Auto Updates:** yes
- **Deprecated:** no
- **Disabled:** no


## Related links

- [Homebrew Cask packages](https://pkg.so/homebrew-cask-packages/) - Generated from Homebrew Cask package-manager metadata.
- [Homebrew Cask applications](https://pkg.so/homebrew-cask-applications/) - Cask artifact metadata includes an app bundle.
- [Desktop app packages](https://pkg.so/desktop-app-packages/) - Matched curated package taxonomy and local package facts.
- [regipy](https://pkg.so/brew/regipy/) - Local package facts share a topical domain. Shared terms: run, windows.
- [bit-slicer](https://pkg.so/cask/bit-slicer/) - Local package facts share a topical domain. Shared terms: games.
- [crystalfetch](https://pkg.so/cask/crystalfetch/) - Local package facts share a topical domain. Shared terms: windows.

## Combined YAML source

View the package source record on GitHub. [combined/highball.yml](https://github.com/mxcl/pkgdb/blob/main/combined/highball.yml)


## Sources

- package-page enrichment
- curated configuration and credential file locations
- curated package history
- package version freshness
- package relationship graph
- cross-ecosystem install command graph
