Skip to content

Setup script fails to add npc-forge to path on macOS 26.6.2 #5

Description

@robisaacnz

(This is a minor packaging glitch rather than an issue with npc-forge specifically.)

The setup script reports a successful install of npc-forge, but after the installation completes, no npc-forge binary is present in the path (and $PATH seems unmodified after the script has run).

$ chmod +x setup.sh && ./setup.sh --dev

NPC-FORGE User Installation

🔧 Dev mode — symlinking from /Users/rob/Projects/termy/NPC-Forge

🙋 Installing for user: rob

 Copying sources to /Users/rob/.local/share/npc-forge...
 Configuring virtual environment...
 Setting up npc-forge terminal command...
 Configuring User Service...
macOS detected. Systemd is not available.

 Verifying environment $PATH...

✅ npc-forge installed successfully in user space

Note: Since Systemd is not available, you need to run the server manually:
Run 'npc-forge server' in a separate terminal before using the tools.

$ which npc-forge | wc -l
0

The user shell is fish, but testing on bash and zsh gives the same result. Examining the unused systemd service implies npc-forge start executes something like cd ~/.local/share/npc-forge && ./venv/bin/python3 ./server.py to start the server, but I haven't been able to discover what other arguments to npc-forge do.

Happy to submit a patch to add support for launchd on macOS once I understand what else npc-forge does or I can find where it is implemented.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions