NodeRunner

v1.1.0

🆕 New Features

• Multiple Bot Support — Run more than one Node.js bot at the same time. Define a bots: list in config.yml, each with its own name and entry file. Each bot gets its own process, log file (bot-<name>.log), and independent crash recovery. Falls back to single-bot config automatically — no breaking changes.
• Node.js Version Pinning — New node-version config option (e.g. "20", "22") lets you pin a specific Node.js major version instead of always downloading the latest LTS.
• stdin Passthrough — New input bar at the bottom of the web dashboard lets you send text directly to the bot's stdin without restarting it.
• Memory Monitoring — The web dashboard now shows live RSS memory usage of the bot process (Linux only, reads from /proc/<pid>/status).
• TunnelMC Integration — If TunnelMC is installed and has an active tunnel on the dashboard port, NodeRunner now prints the public URL to console when the bot starts. Configurable via integrations.tunnelmc-suggestion in config.yml.

🛠️ Changes

• /nodebot commands now accept an optional [name] argument to target a specific bot when running multiple bots
• Bot log files are now named bot-<name>.log per bot when using multi-bot mode; single-bot mode still uses bot.log
• Webhook messages now include the bot name in brackets (e.g. Bot [modbot] started) when running multiple bots
• Thread names now include the bot name for easier debugging

🐛 Bug Fixes

• Fixed npm install failing on Pterodactyl panels due to PATH not being set correctly — node binary directory is now explicitly injected into PATH before running npm