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 2020-06-02 00:00:00Z and 2020-06-03 00:00:00Z
...because why not? (both the tee wanting to join the team, and the team being joined, can be already passed the starting line)
Usual lock/invite rules still apply tho ofc...
d3b6df9 Fix team rejoin logic for sv_team 3 - def-
88b65b6 Newly joined player should not immediately be subtracted from team 0 - def-
3cd35de Merge #2236 - bors[bot]
I guess he'd have a unique_ptr owning the character, which is actually not really correct. With ddnet7 I tried moving towards better ownership semantics, but it's hard to decide who owns an entity
13:51
Usually the only owner of an entity is the world, however the character is owned by the player too, so maybe shared ownership semantics would be better, but that's extra overhead for every other entity that doesn't need shared ownership
13:53
Overall the way teeworlds is designed isn't really great for this kind of thinking, entities kinda own themselves at this point but they are tied to the lifetime of the world. It's like someone wanted entities to be independent but then decided it'd be too much work in the middle of coding it
This PR intends to make the database interaction thread safe and optimizes some SQL queries. This is still a WIP, but since it is a rather big PR I wanted to get feedback early on.
Benefits:
remove race conditions leading to undefined behavior and potential crashes
logging game related database results in teehistorian would be possible
Behavior change:
/top5team prints ranks in reverse order when passing a negative number (like /top5, /top5points)