tibia/querymanager/src/querymanager.hh, 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.
modify how automatic SQLite patches/upgrades works + overall cleanup2025-10-18T05:35:24Zfusion32marcopuzziello@gmail.com2025-10-18T05:32:59Zurn:sha1:601ce32ee8d0cee32b66c87b0bfefa7424a5b8c8world startup/shutdown timestamps + adjust a few column names2025-10-17T19:12:31Zfusion32marcopuzziello@gmail.com2025-10-17T19:12:31Zurn:sha1:d92f642810dc3125515d64f953d2bee840de1cc1properly handle text encoding differences with QueryManager clients2025-10-17T02:04:00Zfusion32marcopuzziello@gmail.com2025-10-17T01:51:58Zurn:sha1:63705942a366d39308251549a018451808c20ac8move ResolveHostName outside of GetCharacterEndpoints2025-10-16T07:23:52Zfusion32marcopuzziello@gmail.com2025-10-16T07:23:52Zurn:sha1:01a6e8dbe42fb6571ad846bee5e1d8cc7c9fba5eallow 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.
make config.cfg a distribution template2025-10-16T03:47:01Zfusion32marcopuzziello@gmail.com2025-10-16T03:47:01Zurn:sha1:85b75f77376b5e6cf571bb6ebc34d11c167ca9cf