-
-
Notifications
You must be signed in to change notification settings - Fork 4
FAQ
Quick answers to the questions that actually come up. For deep dives, follow the links instead of expecting the answer here.
Aphotic was previously known as Noctis-Hypr.
A Hyprland desktop built for four identities at once — developer environment, gaming rig, AI-assisted workflow, and security research box — on top of a minimalist tiling foundation. See Supported Features for everything that ships, or Profiles & Layers for how you pick which identities you actually want.
Most rices are a snapshot you copy over your own config and hope for the best. Aphotic is built to keep moving: package sets are declarative TOML (not bash arrays buried in a script), profiles and layers compose instead of forcing one fixed setup, every install snapshots your configs first, --dry-run shows the entire plan before anything touches your system, and ./uninstall.sh reverses it. See Design Principles for the full reasoning.
It assumes an Arch/AUR base throughout the installer, but that covers more than plain Arch. Omarchy and EndeavourOS (installed with Desktop Environment: None) are both tested and supported directly. See Compatibility for exactly what's supported and what each distro needs, if anything.
Yes. The installer snapshots your existing configs before touching anything (unless you pass --no-backup), and ./uninstall.sh restores that snapshot if you want to back out. At the "Deploying configs" step it asks whether to actually copy Configs/ over ~/.config/ — answer yes, or packages install but your Hyprland config stays untouched. See Installation.
Start from minimal and add only the layers you want, or edit profiles/custom_apps.lst before installing. Profiles and layers are just TOML — nothing stops you from forking one to fit exactly what you need. See Profiles & Layers.
cd Aphotic-Hypr
git pull
./install.shThis re-resolves your saved profile/layers against any upstream changes and snapshots your configs first, same as a fresh install. Once installed, aphotic update does the same thing from anywhere. See Installation for the config-only fast path (--config-only) that skips packages entirely.
./uninstall.shThis restores your most recent backup. Add --purge-packages if you also want it to remove everything your profile installed (behind its own separate confirmation).
A profile (minimal or full) is the base package set; a layer (gaming, dev, ai, exploit and its sublayers) is an optional add-on merged on top. See Profiles & Layers for the full breakdown.
Anything listed in profiles/custom_apps.lst is folded into the resolved package list automatically at install time — no separate prompt needed.
Add your own bindings to ~/.config/hypr/custom.lua. The installer never overwrites this file once it exists, so your customizations survive updates and re-runs. See Keybindings for the full default reference.
Firefox theming depends on the Pywalfox extension — install it and reload Firefox.
aphotic theme list # list available themes
aphotic theme set <name> # apply a specific theme
aphotic theme next / prev # cycle themes, or Super+./,See Theming for how the palette is actually generated from your wallpaper and applied across the stack.
aphotic play hangman
aphotic play snake
aphotic play guessThree small games built into the aphotic CLI, each tracking its own stats in ~/.local/state/aphotic/game-scores.json. See CLI Reference for every other command.
The project is hosted at T-Crypt/Aphotic-Hypr — issues, pull requests, and feature suggestions are all welcome there. See Contributing.
See Project Status for shipped-vs-open at a glance, or GitHub Issues for the current backlog.
- Supported Features — everything shipped, at a glance
- Installation — the full install/update/uninstall walkthrough
- Profiles & Layers — the base-profile/layer merge system in detail
-
Theming — the wallust pipeline and
theme.tomlschema - Compatibility — supported distros, GPUs, and known limitations
-
CLI Reference — every
aphoticcommand - Troubleshooting — debugging installation and runtime issues
-
Security — the
exploitlayer's authorized-use disclaimer