Teeworlds - development

hey

00:29

can someone help me with cmakeerror

00:29

message.txt

4.14 KB

00:29

i have wavpack.h

00:30

but he say

C:\Users\cen940k\source\repos\cen94ok\xpanic\build\CMakeFiles\CMakeTmp\CheckSymbolExists.c(2): fatal error C1083: Не удается открыть файл включение: wavpack.h: No such file or directory,

00:30

Не удаётся открыть файл включение is the same as could not open the include file

00:31

@Assa maybe you know

00:31

may i ask you

https://github.com/teeworlds/teeworlds/tree/master/src/engine/external, compare with local repository

1

Why was the channel volume control float Vol removed in CSounds:: Play, CSounds::PlayAt? Were there any mistakes? or removed it earlier because of no need? https://github.com/teeworlds/teeworlds/blob/master/src/game/client/components/sounds.cpp#L161 (edited)

teeworlds/teeworlds

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

@Deleted User looking at matricks' commit 12 years ago, this parameter was never used

12 years... so long. lol

16:05

also, pitching an idea: have server broadcast team scores so that they can be viewed in the server browser

sounds good to me

Please let's not do that until we have a nice long chat about the serverinfo protocol

it's currently broken for too many players btw

Currently it doesn't fit all 64 clients, so it needs at least some chunking. While at it we should probably leave space for extensions

17:12

Maybe adopt @heinrich5991's version with or without everything being strings

then have a nice long chat about the serverinfo protocol

Well I'm not the one merging it so it's Oy that should be around for that chat

Oy is pretty merge-happy nowadays, especially when you fix a bug

Well yes but this would be a rather large change and could involve backwards compatibility code

I don't see any other way

Well then it'll have to be a bit snuck in the request somewhere to indicate that this client can read new serverinfo messages that wouldnt break the request for old servers and another bit snuck in the response to indicate that this is a new serverinfo message

17:51

Both the client and the server will need compatibility code to support the old response and the old request respectively

17:53

I'd use heinrich's format, but not sure if we want the replies to only contain strings or packed ints too

server info messages are a bit performance critical aren't they

Yes but now they cost quite a bit to request with the large size of the token message

17:57

Ratelimited with a token I doubt the str formats would ever be a critical overhead

17:58

Atleast they dont show up on our profiles, albeit we cache very aggressively now

17:59

But on the other hand, the packed ints do indeed perform better, I think @heinrich5991's intention was interoperability

interesting arumbaThink

so it's not worth the effort to pack the ints

or convert ints to chars