aboutsummaryrefslogtreecommitdiff
path: root/src/communication.cc
Commit message (Collapse)AuthorAge
* fix RETRIEVE action, used with ropingfusion322025-08-17
|
* wrapping up for a public releasefusion322025-08-15
|
* fix some critical bugsfusion322025-07-19
| | | | | | Aside from obvious gameplay bugs pretty much everywhere, the game is finally in a PLAYABLE state. It should be smooth sailing to get it stable for an initial test server.
* THREADING: upgrade from LinuxThreads to NPTLfusion322025-07-19
| | | | | | | | | | | | This was a required change to make the server run on a modern GLIBC version without resorting to shady shared libraries or compatibility tricks. It is very straightforward but we should always keep an eye out for possible bugs. There was also a problem with the Z loop on field sending functions that was causing the server to hang in an infinite loop and should now be fixed. With these changes it is now possible to login into the game for a split second before the client asserting.
* small cleanup + fix sigaction flagsfusion322025-07-18
|
* fix most init and parsing bugs + critical bug with dynamic stringsfusion322025-07-16
| | | | | | With an appropriate query manager, the server now starts up and seems to work but won't properly handle connections until we fix the problem with threads and signals described in `TODO.md`.
* implement `crypto.cc` with OpenSSL + fix config loadingfusion322025-07-03
| | | | | | | | | | | | | | | | I considered reversing the original `vlong` implementation but OpenSSL is just simpler, more secure, and most importantly, is already there. I also made it so the key is now stored in a PEM file (`tibia.pem`) so it can be easily swapped without re-compiling. This was the last piece to build and run a working executable, except that we now need to implement a query manager for the server to communicate with. I was able to fix a small problem with loading the config before hitting the problem with the query manager, which was expected. The next task should be getting a query manager up and running before starting phase two of upgrading and fixing the server itself.
* `query.cc`fusion322025-07-02
|
* beginning of `query.cc`fusion322025-07-01
|
* `writer.cc`fusion322025-06-30
|
* `receiving.cc`fusion322025-06-23
|
* `connections.cc`fusion322025-06-21
|
* finish `communication.cc`fusion322025-06-20
|
* small change to `ReceiveCommand` for increased connection reliabilityfusion322025-06-20
|
* more work on `communication.cc`fusion322025-06-20
|
* beginning of `communication.cc`fusion322025-06-19