Development discussion. Logged to https://ddnet.tw/irclogs/ Connected with DDNet's IRC channel, Matrix room and GitHub repositories β IRC: #ddnet on Quakenet | Matrix: #ddnet-developer:matrix.org GitHub: https://github.com/ddnet
Between 2019-09-30 00:00:00Z and 2019-10-01 00:00:00Z
You don't quite seem to understand what it means to block this server-side
06:18
the heuristic we decide to use could end up eating your input, is that preferable to losing some bragging rights?
06:22
Also you don't always know that someone is spamming the hammer at the time, what if we know after the hammer hits? Do we ban them for cheating?
06:24
Anyway if we don't merge this we might aswell disallow the hammer spam. I'd love to see how you feel about it when konsti starts cheating all the deepfreeze parts smashing records
It's installed basically everywhere and just increases release size.
They're serious about backward compatibility and haven't had a breaking
change in ages.
It's installed basically everywhere and just increases release size.
They're serious about backward compatibility and haven't had a breaking
change in ages.
This uses version 2 of the teehistorian file format which has support
for extra chunks, i.e. rarely used chunks that need not be standardized.
teehistorian records all network messages and inputs f...
Is/was there a reason why we have this awkward combination of record_race and record_teamrace in our database with all the redundancy but still no way to clearly match stuff from record_race with a teamrace?
I got a little time the last days and in light of ddnet7 did some experiments to implement an rpc-service that is used to communicate with a database. Things are mostly working already but now i am creating a python script to do the actual sql-queries and it is not so nice. To clarify how it works right now: DDNet-Server calls my pythonscript or whatever implements the rpc-service which is then responsible to store and retrieve ranks etc.
19:50
About the db-scheme: I was thinking of a table for finishes storing map, time, gameuuid etc. but not the playernames or checkpoints with an uuid and another table linked via this uuid with the players and their checkpoints.
19:51
Maybe checkpoints should even be another table, so we keep only the best.