DDraceNetwork - developer

DDraceNetwork

Development / developer

Development discussion. Logged to https://ddnet.org/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 2024-11-02 00:00 and 2024-11-03 00:00

Ewan

anyone here ever use the calamine crate justatest

justatest

whats that justatest

justatest

spreadsheet deserializing lib

sounds like office routine that was rated as 2 hour task but in reality will take 1 week due to some really fhnny circumstances

that is what it has turned into

05:28

i have a dilemma

05:29

i dont think there's a way for me to deserialize directly into my struct for every field i need

05:30

bcs the in memory copy would have some more structs nested within it but serde flattening doesn't handle duplicates of the same key like would happen with any 2 flattened fields of the same type

05:31

so i think i need to keep an intermediate struct and then maybe skip some fields & populate manually

05:31

but the person writing these spreadsheets is old so ive basically been told i can't rely on any set scheme for these xd

05:31

they want dynamic spreadsheet deserialization scheme switching from configs

05:31

like pls im a rust noob

you can specify de/ser and make it dynamic, i think

06:32

check serde documentation, i don't really know what you need to do xd

github-merge-queue[bot]

[ddnet:master] 2 new commits

b086b21 Change default Q bind to /spec - KebsCS 812da8e Merge pull request #9195 from KebsCS/pr-q-spec - def-

6

1

06:47

[ddnet/ddnet] Pull request closed: #9195 Change default Q bind to /spec

[ddnet/ddnet] Pull request opened: #9196 Fix player info being resent too fast/slow depending on FPS

The change info message was being resent too fast/slow because m_aCheckInfo was decremented every frame whereas it was intended to be decremented every tick. As m_aCheckInfo is set to Client()->GameTickSpeed() after sending the info, it's likely that this was intended as one second delay. With debug messages is can be confirmed that the change info message was previously resent more than 10 times per second with high FPS on a local server. Also fix the info resending delay not being ...

Is it just me or my crosshair is transparent? xd

Image attachment

21:56

It is

github-merge-queue[bot]

[ddnet:master] 2 new commits

2a39a1a Fix player info being resent too fast/slow depending on FPS - Robyt3 aa80bae Merge pull request #9196 from Robyt3/Client-CheckInfo-Delay-Fix - def-

22:36

[ddnet/ddnet] Pull request closed: #9196 Fix player info being resent too fast/slow depending on FPS

Exported 20 message(s)

Timezone: UTC+0