tibia/querymanager, branch masterTibia 7.7 compatible query managerhttps://kaplar.net/tibia/querymanager/atom?h=master2026-02-09T17:25:21Zfix small issue with TransferHouses query2026-02-09T17:25:21Zfusion32marcopuzziello@gmail.com2026-02-09T17:25:21Zurn:sha1:edea08d11cc306955d8d732164ec383d37ea1f62fix problem with EvictExGuildleaders query2026-01-17T03:50:58Zfusion32marcopuzziello@gmail.com2026-01-17T03:50:58Zurn:sha1:6052f2452409c2d1560984b2d2c5cfc3517742f4fix 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.
turn error codes into enums + check empty credentials before login2025-10-31T01:15:57Zfusion32marcopuzziello@gmail.com2025-10-31T01:15:57Zurn:sha1:093e1563df314c661bb1b73524309fd154001ce2
Using enums instead of hard coded numbers for error codes should
help with readability, even though they're local to the functions
that use them to avoid flooding the namespace.
Checking whether credentials are empty before login will prevent
error messages such as "account disabled" from showing up when no
account is specified, which may look weird. It'll also avoid any
database reads although this shouldn't really make a difference
torwards performance or security since it's only an edge case.
prevent password brute force (#4)2025-10-30T04:03:01Zfusion32marcopuzziello@gmail.com2025-10-30T04:03:01Zurn:sha1:d36b26307d55602e2116ce3fcfa767693c266d7a
Prevent blocked IP addresses and accounts from returning anything
other than a blocked error message. Previously, further attempts
would first check the password which enabled brute force attacks
to use the "invalid account/password" message as an oracle.
adjust character death indexes for common queries2025-10-28T00:44:13Zfusion32marcopuzziello@gmail.com2025-10-28T00:44:13Zurn:sha1:6aa13394a12c1931990b91e62210cba72706920dchange 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:ebf536a7910f6e8d5bff569d2d717287ad3ba716