tibia/querymanager/src/querymanager.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.
change how guild data is stored2025-10-23T07:26:11Zfusion32marcopuzziello@gmail.com2025-10-23T07:26:11Zurn:sha1:27a0df43b33b712462ab5be65462162b9e4bcd29add include path for PostgreSQL + overall cleanup2025-10-19T22:17:37Zfusion32marcopuzziello@gmail.com2025-10-19T22:17:37Zurn:sha1:0ff6217227ce551d6c91524c8e7fd37352e20490
Some distributions place libpq headers under /usr/include/postgresql
which is why it's added to the include path. And even though we don't
support it yet, the same happens with MariaDB, with headers being
placed under /usr/include/mariadb.
update documentation + wrap the few SQLite scripts2025-10-18T21:21:31Zfusion32marcopuzziello@gmail.com2025-10-18T21:21:31Zurn:sha1:eba55f8361fc36179e36bf8a3cea5067b5341e37properly handle NULL values with postgres result helpers2025-10-18T06:40:40Zfusion32marcopuzziello@gmail.com2025-10-18T06:40:40Zurn:sha1:ebf536a7910f6e8d5bff569d2d717287ad3ba716modify how automatic SQLite patches/upgrades works + overall cleanup2025-10-18T05:35:24Zfusion32marcopuzziello@gmail.com2025-10-18T05:32:59Zurn:sha1:601ce32ee8d0cee32b66c87b0bfefa7424a5b8c8properly handle text encoding differences with QueryManager clients2025-10-17T02:04:00Zfusion32marcopuzziello@gmail.com2025-10-17T01:51:58Zurn:sha1:63705942a366d39308251549a018451808c20ac8allow all database config options to be loaded, even when not used2025-10-16T04:53:03Zfusion32marcopuzziello@gmail.com2025-10-16T04:53:03Zurn:sha1:0a82003d870b901b09e25ec29c432af034b1e255lower 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.
postgres interval helpers + a few more queries2025-10-15T07:13:13Zfusion32marcopuzziello@gmail.com2025-10-15T07:13:13Zurn:sha1:7a2358c859dfe5251b709e63f35bc3ed5658e3e2