@haircode Nothing in networking is straightforward. While not having tried this using the #relayd , it is likely to be a standard firewalling destination NAT (see DNAT) capability, suitable for running a server inside a firewall protected LAN. . So I've configured firewalls to do this many times, including using IPTABLE rules on Linux.
Some useful notes linked, but note that in this example:
==========================
Packets destined for IP 10.1.1.7 will be forwaded to 192.168.1.2 UDP,TCP
Does NOT work with ping (ICMP) correctly, does not handle ICMP protocol WLAN IP reply on a ping without
iptables -t nat -A PREROUTING -p tcp -i wlan0 -d 10.1.1.7 -j DNAT --to-destination 192.168.1.2
iptables -t nat -A PREROUTING -p udp -i wlan0 -d 10.1.1.7 -j DNAT --to-destination 192.168.1.2
==========================
traffic on all ports are forwarded, while it's more likely you will want to forward traffic on specific ports for the Minecraft server port requirements, as that is more secure.
https://gist.github.com/tomasinouk/eec152019311b09905cd