Teeworlds - development

https://github.com/teeworlds/teeworlds/issues/2172

Client: Add basic race support · Issue #2172 · teeworlds/teeworlds

show times instead of points seperate race timer finish msg (as kill message), localized, icon start/finish/checkpoint supprt automatic demo recording of the race

14:21

What is needed?

14:21

In order to implement the automatic demo recordings, there need to be snapshots for race beginning?

wouldn't that break netcode / compatiblity?

Weren't snapshots for race implemented already in a similar vein?

14:38

Like, snapshots informing client of current race data

No idea, been forever

14:43

This is really in the polishing realm

https://github.com/teeworlds/teeworlds/blob/master/datasrc/network.py#L455-L468

teeworlds/network.py at master · teeworlds/teeworlds

A retro multiplayer shooter. Contribute to teeworlds/teeworlds development by creating an account on GitHub.

Race start time is send in PlayerInfoRace object and the Sv_RaceFinish message is send on finish

O

14:44

Hmm

Finishes are shown in the killmessage area (infomessages.cpp), so the backend should be available already

So technically making a demo for recording would include recording everything, then cutting it to match the RaceStartTime and Finish Time?

I'd add multiple demo recorders for different systems, like it's done on ddnet

14:46

The manual recorder for using the ingame Record-button (or the record-command) and another recorder for automatic race recordings

Makes sense

14:47

Would contribute to conflicts without that

Yeah, different recorders means there are no conflicts if race is finished while a manual recording is in progress or vice versa