Address: 192.160.0.1 11000000 .10100000.00000000.00000001
Netmask: 255.0.0.0 = 8 11111111 .00000000.00000000.00000000
Wildcard: 0.255.255.255 00000000 .11111111.11111111.11111111
=>
Network: 192.0.0.0/8 11000000 .00000000.00000000.00000000 (Class C)
Broadcast: 192.255.255.255 11000000 .11111111.11111111.11111111
HostMin: 192.0.0.1 11000000 .00000000.00000000.00000001
HostMax: 192.255.255.254 11000000 .11111111.11111111.11111110
Hosts/Net: 16777214
As Dag Nabbit stated, a Minecraft server does not talk http. You would typically do this via NAT. A proxy server needs to know the protocol, because as the name suggests, it acts on behalf of the the client. Nginx knows various protocols, not just http, but Minecraft is not one of them. You can however write a proxy module for this protocol and use the existing nginx infrastructure. Since I'm not familiar with the protocol, I can't comment on the fact that this would have any advantages over NAT.
host = Host()
parser = init_parser(host.location())
content = host.list()
print_highlight(*content)
const list = await pop3.UIDL();
console.dir(list);
/**
* [
* ['1', 'ZC0113-H8wi_YChVab4F0QTbwP4B6i'],
* ['2', 'ZC0114-3A9gAn8M2Sp1RhVCGTIII6i'],
* ...
* ]
*/