Teeworlds - bridge

Is the client id and player id two different things?

wavi: nope

08:12

client id is the only id given to a client

08:12

I'm not aware of a player id being used anywhere

ok, if I connect as a player I see this "[server]: player has entered the game. ClientID=0" and "[game]: team_join player='0:wavi' team=0"

08:15

is the id 0 in 0:wavi the same id as clientid?

yes

Thanks!

08:26

so if player id isn't used for anything, what is it for?

what is player id ?

i dont know, does it even exist? :D

There is no player id, that second message you sent prints the clientid

cheers

this will make my code easier to follow..

11:10

I

11:11

*I've been using "cid" and "player_id" but I guess i'll just call it "client_id" everywhere for clarity

cid and ClientID and id:nickname are the same.

great

11:13

I'm working on a super simple nodejs econ lib that just parses and emits events. I'll then build a game state manager on top of that (keeping track of deaths, killstreaks, etc).

Sounds fun

yeah, so far I already have it parsing (almost) all the events and emitting them so it should be trivial to listen to those events and maintain state

named groups is really helpful to have with regex. I can do stuff like this and get the matched groups directly as an object with named properties /pickup player='(?<client_id>\d{1,2}):(?<player_name>.*)' item=(?<item_id>\d+)/

hmm, maybe I shouldn't chill here via two different networks

Especially not with different nicknames :)

Learath2: anything left in https://github.com/teeworlds/teeworlds/issues/1120 ?

some issues with the code · Issue #1120 · teeworlds/teeworlds

CServer::RegisterCommands sets m_pConsole, m_pGameServer, m_pMap, m_pStorage, which it shouldn't do, it looks like a dirty fix someone did to make it work, whatever it was. network_server.c...

Yeah, NETCTRL_MSG_ACCEPT, I couldn't figure out what that one meant, couldn't figure out the extra projectile thing either. m_Hooktick neets a NETVERSION bump, OnDirectInput I think is fine as is, CDataFile I couldn't understand, also didn't know how to fix the code not sending all non-acked

15:30

the rest are fixed

In regard to the whisper messages. If someone has turned off receiving those on the client side and someone else tries to send that person a message, is there some response from the server that that person turned off their whispering?

15:38

like: Could not deliver message, player has turned off whispering.

no

15:43

same when u mute someone

https://github.com/teeworlds/teeworlds/commit/06db9bf53fd2df9ae3c251e9435cc7e9a8bc7df5 i think default tuning was correct here. it's basically the counterpart for https://github.com/teeworlds/teeworlds/blob/5e995d23a2be251498380282c13f982acf2f43d0/src/game/server/entities/character.cpp#L553 which uses default tuning aswell

maybe that should use the correct tuning too?

that might break dead reackoning for old clients =\

does it work correct right now when the tuning isn't the default one?

when tuning is not default, the reckoning core differs from the real core, so the server does not use dead reckoning at all -> the client does not use evolve