My guide (Networking and SINS) is all over the place, most notably linked-to from my sticky in the "Technical" forum OR the very bottom of the "Technical FAQ". Make sure you use the "Networking and SINS" guide and not my more generic other guide.

the Monk

I second that vote.
All things aside the monk goes above and beyond for the sins community.
We should all learn from the example.

   Showing your age here I guess.....hehe (no offence meant.....just an observation)


Anyway, If you chose to read more forum posts instead of blindly posting you'd also know the answer to your question.


1. SINS is P2P, not client-server. It is P2P because each player runs the ENTIRE simulation on their own PC, the HOST (doesn't really "host" anything) but rather SYNCS all of the player's games together.

2. Patch 1.1 will introduce an optional NAT-T (NAT traversal) type netcode which will "tunnel" past routers/firewalls. This is necessary for those people at university dorms etc. where they don't have control over forwarding traffic etc and/or those who don't care enough to somewhat "control" game traffic (by forwarding specific traffic).

I for one, will never allow anything to simply "tunnel" past my network controls and am glad the DEVS took the approach they did, and are even in changing things making it an "option" to keep one's networks under tighter controls. A sign of smart developers!   


the Monk

You're welcome, and it is always nice to talk to people voice-to-voice via my TeamSpeak server (I like to know the people who are going to kick my ass in-game someday!..hehe    )


the Monk