SPACE-NERDS-IN-SPACE(6)

📦 version 1.1.1, in nixos 26.05, nixpkgs unstable

💖 NAME 💖

Welcome to the SPACE-NERDS-IN-SPACE(6) page from the Games manual, bestie! This is the whole vibe for:

snis_multiverse — Multi player cooperative star ship bridge simulator (server wrangler)

🚀 SYNOPSIS 🚀

snis_multiverse [--autowrangle] -l lobby -n server-nickname, -L server-
       location [--exempt snis-server-location]

✨ DESCRIPTION ✨

Okay so snis_multiverse is a meta-server process for the game Space Nerds In Space, which is a multiplayer starship bridge simulator. The meta-server process tracks player ships between instances of the server process. It is what enables player ships to travel from one snis_server instance to another, possibly on a different host.

The "gameinstance" parameter is used by the game lobby process (ssgl_server) to distinguish one game instance from another running on the same host. The gameinstance should be a short human readable string to uniquely identify the game instance. The serverhost is the hostname of the server hosting the ssgl_multiverse process. The location is a human readable string giving some idea of the location of the server, or some other descriptive information.

Options: ✨

  • --acknowledgments — Prints out acknowledgments and license information and exits. 💅
  • --allow-remote-networks — By default, snis_server instances started by snis_multiverse will not allow clients to connect from remote networks, but only from the local network as determined by the netmask. With this option, snis_multiverse will invoke snis_server instances with the same --allow-remote-networks option so that such instances will allow clients to connect from remote networks. See also: the environment variable SNIS_ALLOW_REMOTE_NETWORKS below. 🌐
  • --autowrangle, -a — Automatically start snis_server processes within one warp-gate hop of any player, and automatically shutdown snis_server process not within one warp gate hop of any player. 🌀
  • --exempt, -e — Exempt a snis_server location from autowrangling. If you use autowrangling you need to exempt at least one snis_server location otherwise snis_multiverse will immediately shut down all snis_servers since, initially, there are no connected player ships anywhere. 😭
  • --lobby, -l lobbyserver — Specify the lobby server hostname or IP address. 🏨
  • -p port-number, --port port-number — Specify the port number to use for incoming connections from snis_server processes. If a port is not specified, a port is randomly chosen from the dynamic port range, 49152 - 65535. 🔌
  • --servernick, -n nickname — Specify the nickname of this multiverse process. (It's not really used for anything, nevertheless, it's required.) 🎀
  • --location, -L location — Specify the location of this multiverse process. (It's not really used for anything, nevertheless, it's required.) 📍
  • --snis-server-portrange min:max — By default snis_server processes will be started using the dynamic port range 49152 - 65535. This option allows specifying a different range, useful if you're running behind a firewall and want to restrict which ports you need to open. 🔥
  • --version — Print the program's version number and exit. 👑
⚠️ Bestie, the --exempt warning is real: if you use autowrangling and don't exempt at least one snis_server location, snis_multiverse will immediately shut down all snis_servers since, initially, there are no connected player ships anywhere. No cap. 💀

FILES 🗂️

  • ./snis_multiverse_log.txt — (Only if started via snis_launcher.) This file contains the stdout and stderr of snis_multiverse, Can be useful for debugging. This file can be relocated via the SNIS_LOG_DIR environment variable. 🪵
  • $SNIS_DB_DIR/snisdb,
  • $XDG_DATA_HOME/space-nerds-in-space/snisdb,
  • $HOME/.local/share/space-nerds-in-space/snisdb

Directory containing a database of bridge data. This database is used for verifying username/passwords for bridges and for storing bridge state to allow bridges to transition from one snis_server instance to another. 💾

If neither XDG_DATA_HOME nor SNIS_DB_DIR is set, then snisdb is stored in $HOME/.local/share/space-nerds-in-space. If the environment variable SNIS_DB_DIR is set, then snisdb is stored in $SNIS_DB_DIR. Finally if XDG_DATA_HOME is set, and is an absolute path, then snisdb is stored in $XDG_DATA_HOME/space-nerds-in-space. 🌸

ENVIRONMENT VARIABLES 🌱

  • SNIS_ALLOW_REMOTE_NETWORKS — If the value of this environment variable is "1" it has the same effect as the --allow-remote-networks option. 🦋

SEE ALSO 👀

GOOD LUCK 🍀

You'll need it.

AUTHOR ✍️

Written by Stephen M. Cameron

xoxo, your snis_multiverse server-wrangling bestie 💖 — Feb 2025, SPACE-NERDS-IN-SPACE(6), mwah 💋

📦 where this page comes from