dark place s

[l33t]

If I were able to connect to cheatfree servers with darkplaces I would use it 24/7. I can see where a problem would be though with the custom models and what not, but really who gives a fuck. catch someone cheating, just ban there ass. end of story. kinda like skil using wallhack. ban him.

[Canadian*Sniper]

http://www.quakeone.com/forums/showthread.php?t=2066

here's a good discussion on cheatfree servers In a nutshell, the only thing proquake cheatfree servers are preventing is the use of other clients. People can still bypass the cheatfree with aimbots and wallhacks. And DarkPlaces servers (which can run under the Quake protocol) disallow wallhacks altogether.

[l33t]

does it also stop bots?

[l33t]

if so I might want to run it on my server, but can normal clients connect or is it just darkplaces?

[Canadian*Sniper]

There's really not much you can do to stop aimbots. There are companies selling programs which aimbot for you. If someone suspects an aimbot, have them record a demo (recording from the suspected bot's perspective would be best) and send the demo to the admin for inspection

When you start darkplaces, the default sv_protocolname is "DP7". DP7 is an advanced protocol which not very many quake clients support. So you need to change the protocolname to "QUAKE" so any netquake client can connect. You also can't host more than 16 players if you want them to connect.

So when you start a server, make sure you have this in the autoexec.cfg:

sv_protocolname "QUAKE";
sv_cullentities_trace 1;

Here's a sample server start command line:

darkplaces.exe -game whitehot -dedicated 16 -port 26001 -condebug

I heard rumours about this annoying pingreport message popping up in non-darkplaces clients. LordHavoc made a quick fix in the current DarkPlaces beta download. Check it out if you need to

[spooker]

so i thought i'd give Darkplaces another try, and I found I can't connect to any servers; it looks likes its going to connect, for a few seconds, then I get Connection Timed Out. Any ideas how i might fix this? (Win XP, wireless, behind netgear router, and yes i let it past my firewall zonealarm)

[foq]

-ip yourip?

[Baker]

yes i let it past my firewall zonealarm)

Well, I quit using ZoneAlarm because it managed to mess up my Quake connection regardless of what I told it to do. It would give me lag, sometimes it would entirely block my connection and sometimes the little system tray icon disappeared on me and it stopped all internet traffic. This was on my Win98 machine (my XP machine it gave me blue screens on boot).

To my knowledge, FOQ dumped ZoneAlarm because of the same problem, except he had it with Battlefield 1942 or something.

The only way you can rule out ZoneAlarm as the source of the problem is by completely uninstalling it and then trying to connect and see if it works well or not.

-ip yourip?

That only works if you have 2 network connections (like a LAN + dialup modem) or 2 network adapters and in that case, the -ip parameter is for when you can't connect at all because it is trying to use the internet with the wrong net address.

[Canadian*Sniper]

try connecting right when you start the game (as the demo plays).

[spooker]

I have never had any problems with zone alarm before. but i did shut it down and tried what snipes said; only thing that happened different was i got a different error message:
"LHNET_read: recvfrom returned error: WSAECONNRESET"

wtfudge?

[scar3crow]

I used to experience the connection timed out bit from DP, trying a second or third time and it would get through. Or just exiting and restarting DP would get it in. It was just fickle for me for a while (though never on DP7 severs).

[Monster]

I used to have that problem too, with the timing out. I downloaded the latest beta and it worked fine. Instant connectivity.