tibia/querymanager/src/connections.cc, branch masterTibia 7.7 compatible query managerhttps://kaplar.net/tibia/querymanager/atom?h=master2025-11-18T18:17:29Zfix problem with connection input + allow login server to query worlds2025-11-18T18:17:29Zfusion32marcopuzziello@gmail.com2025-11-18T18:17:29Zurn:sha1:8c2a8461db64e92ac09f202589009ee05c69626d
There was a small problem with how we computed the size of the
packet "header". It was unlikely to manifest tho, because it's at
the beginning of a TCP message and TCP segments aren't that small,
unless the whole message is that small.
I'm also allowing login servers to query for world information
to allow a basic form of `STATUS` to be implemented.
lower monotonic uptime resolution from MILLISECONDS to SECONDS2025-10-16T04:46:10Zfusion32marcopuzziello@gmail.com2025-10-16T04:35:10Zurn:sha1:95022ca95b1d2792bae447d90694dcc0d67b9de2
The monotonic uptime was used exclusively with caches and having
a resolution of SECONDS allows it to be stored as an int without
risk of wrapping (~68 years). Using MILLISECONDS meant that it
would wrap after ~25 days which is totally possible and EXPECTED.
Just as an example, the small test server I ran for about 1 month
had ZERO downtime on the QueryManager except for when I manually
restarted it. It was probably very close to wrapping when I took
it down.
organize database configs and schema files + compilation guards2025-10-10T18:22:27Zfusion32marcopuzziello@gmail.com2025-10-10T18:14:02Zurn:sha1:46c653293381dcc1188013d3e2c3f7587a199dc4switch to blocking poll + fix config, signals, time, non-game login2025-10-10T05:17:19Zfusion32marcopuzziello@gmail.com2025-10-10T05:17:19Zurn:sha1:cc4873e33866ba86561774a7e55449d59367661eupdate sqlite driver + impl INTERNAL_RESOLVE_WORLD2025-10-09T06:45:58Zfusion32marcopuzziello@gmail.com2025-10-09T06:45:58Zurn:sha1:9f151fa13022e345e45aa5673e0e168b0ce96cb6
With this change the game server is able to login again but we
still need to re-implement/re-fit the other queries for it to
properly startup.
worker initialization robustness + query processing2025-10-08T02:37:24Zfusion32marcopuzziello@gmail.com2025-10-08T01:28:46Zurn:sha1:708bd2e3cf0a7aa825e6da96caaec55bd271f896make connections properly handle async queries2025-10-07T21:50:02Zfusion32marcopuzziello@gmail.com2025-10-07T21:50:02Zurn:sha1:aa31732158d3e457dfe630f3b2e56f53de89e2b1
This moves queries from `src/connections.cc` to `src/query.cc` and
adds a few missing details. The only thing left is to review query
processing and tie database operations to the `TDatabase` struct.
sketch out new query queue/worker for async queries2025-10-06T22:41:32Zfusion32marcopuzziello@gmail.com2025-10-06T22:41:32Zurn:sha1:f3c2d53f1837a7bd8e9e1517579b7354af91ef8cfix RIGHT check with notations and ip banishments2025-09-13T13:30:50Zfusion32marcopuzziello@gmail.com2025-09-13T13:30:50Zurn:sha1:875b584b090680858393bb24dc58fa85e1a434ceremove ParseOptionalIPAddress2025-09-13T05:20:28Zfusion32marcopuzziello@gmail.com2025-09-13T05:20:28Zurn:sha1:748f676ea6474053e592f47804da27d4b9e49041
I had just added it in the last commit but it made its use case
non-obvious. Checking whether the string is empty before trying to
parse an IP address is clearer than calling some function that has
its own concept of what an empty address is.