One pointer: If you find out your own IP address, you can broadcast a message to all computers in the same subnet by sending a message to the broadcast IP -- typically .255 in your subnet.
e.g. if your own IP happens to be 192.168.17.4, you can reach all computers in your subnet by sending a message to 192.168.17.255
(Note: If you have divided your subnets into smaller chunks, the broadcast IP will be different and you need to know the netmask for your segment to find out what it is... Not sure how to obtain your netmask from within Blitz)
Anyway, if you broadcast a message to .255, every computer on your lan segment will receive it. If you are looking at making some kind of network game, you can have a computer that hosts a game server broadcast itself to .255, and have the client computers listen for the incoming signal, and report back their respective info to the gameserver host. It can then arange the direct peer-to-peer communications from there on out.
e.g. if your own IP happens to be 192.168.17.4, you can reach all computers in your subnet by sending a message to 192.168.17.255
(Note: If you have divided your subnets into smaller chunks, the broadcast IP will be different and you need to know the netmask for your segment to find out what it is... Not sure how to obtain your netmask from within Blitz)
Anyway, if you broadcast a message to .255, every computer on your lan segment will receive it. If you are looking at making some kind of network game, you can have a computer that hosts a game server broadcast itself to .255, and have the client computers listen for the incoming signal, and report back their respective info to the gameserver host. It can then arange the direct peer-to-peer communications from there on out.