Teeworlds - development

[teeworlds/teeworlds] Issue opened: #2872 General structure of the code?

Hi, sorry if it's not the appropriate place, but when I tried asking my question in forums, I keep getting errors, and IRC chatroom is empty. The game got my interest and I decided to study its code. Now, I get what individual line is doing but I can't put the whole thing together. Could anyone provide me a general explanation on how the code works, or something like a diagram of the code structure?

unexploredtest

[teeworlds/teeworlds] Issue closed: #2872 General structure of the code?

In Teeworld's source code, what's the role of src/engine/client ? Is it used when one's connecting to a server?

src/engine contains parts of the code that don't have anything to do with gameplay, it handles the lower levels of the protocol (such as joining, leaving, rcon, map downloads, serverinfo requests) etc. (edited)

14:21

Parts of the engine and the game(src/game) interact with each other through interfaces defined in src/engine

Learath2

src/engine contains parts of the code that don't have anything to do with gameplay, it handles the lower levels of the protocol (such as joining, leaving, rcon, map downloads, serverinfo requests) etc. (edited)

Thanks! It makes much more sense now, somehow I thought src/engine was were the graphics engine was coded

14:23

Also, src/base contains the laws and physics of the game right?

no

14:24

src/base abstracts away the platform

14:24

src/base/tl is a (imo misguided) implementation of some data structures in an attempt to avoid the STL

14:25

src/base/system.c is where all the platform specific stuff happens

And where is the physics of the game coded in? (edited)

src/game/gamecore.cpp is where the physics are

14:26

Careful, changes there will break prediction for clients. Unless carefully considered

(edited)

Learath2

src/game/gamecore.cpp is where the physics are

Ok thanks! That's really help

Learath2

Careful, changes there will break prediction for clients. Unless carefully considered

(edited)

XD

14:27

Actually, I wonder what happens if it goes all wrong

14:27

Let me check...

If the client prediction does not match the server it can cause things like snapping, jittering, rubber banding

Learath2

If the client prediction does not match the server it can cause things like snapping, jittering, rubber banding

How can I test locally? Like some sort of single player?

If you are an old player, you might be familiar with ddrace's freeze tiles where you can't move but it used to look like you could on the client, causing a weird feeling.

unexploredtest

How can I test locally? Like some sort of single player?

You host a server?

Learath2

You host a server?

No,

14:30

Is it possible to play without joining/hosting servers?

The ? was supposed to imply that I don't understand why you'd have such a question

Oh

14:30

Sorry

You compile, you run the server executable and you get a local server

Learath2

You compile, you run the server executable and you get a local server

Aha

14:31

Gonna test...

If you want to experience the prediction failure, make sure you don't use the client you compile yourself

Learath2

If the client prediction does not match the server it can cause things like snapping, jittering, rubber banding

This won't happen then right?

use the official client to join the server you compiled with different physics (edited)

1

14:34

Most mods use trickery like sending fake tunes to clients to get the prediction to match better. DDNet client supports protocol extensions which we use to actually send more information about the entities to get better prediction on servers that implement the extended objects

Learath2

If the client prediction does not match the server it can cause things like snapping, jittering, rubber banding

there's a whole lexical field to lag!

Shoot... That did not go well

Ok, so one last question, src/game/client 's job is to render and animate stuff right? (edited)

sure

Makes sense, thanks