ProQuake Dedicated V2

[Baker]

[Baker]

[Baker]

[Baker]

Just changing the MAX_DATAGRAM does appear to work and should in theory be optimal. (Adjusting it per protocol.)

[Baker]

Host_Error Versus Sys_Error

Host_Error is anything that can safely be solved by dropping to console during a Host_Frame (disconnecting client + shutting down server).

This means:
1. QuakeC errors. All of them!
2. Server errors. All of them.
3. Client game errors. All of them.

Except: If some action can't be rolled back. An example would be any use of malloc followed by an error (never gets freed) or opening a file (never gets closed).

Some things are not obvious:

Sound errors can't drop to console because the menu has sound and using the menu does not require a map be loaded.

I think the original Quakeworld source code had this far better in the source code than NetQuake.

[r00k]

nice minimalist server exe
once i added protocol 666 i can not host a dedicated server yet qrack isnt a dedicated server engine
which sux as it has in the past been able to host a server
maybe some day ill fix this but pq works(required) for my mods so im not in a hurry. to fix qrack for that

im currently mimicing crmod and creating a rank command and saving match stats over level change if need be engine side ill provide sources

[Baker]

[Spike]

Baker, if you want a solution to datagram size limitations, you'll need something like:
http://sourceforge.net/p/fteqw/code/432 ... deltas.txt
Note that its not fantastically different from how DPP5+ sends entities.
That doc *should* give enough info to implement the extension, and will work fine as an upgrade over either protocol 15 or 666 (you may still want 666 as the underlying protocol to provide the svc_clientdata stat changes).
Note that nq support for this protocol is still fairly new in fte, so if you want to test it with an existing implementation be sure to use the current test build of fte.

Anyway, point is that retaining entity state from one frame to the next, resending only when something has changed (which 666 does not do - entities are resent from baseline even when they're idle) will save you both bandwidth and fragmentation-induced packetloss.

[Baker]