diff options
| author | ultramage <ultramage@54d463be-8e91-2dee-dedb-b68131a5f0ec> | 2007-04-05 18:49:57 +0000 |
|---|---|---|
| committer | ultramage <ultramage@54d463be-8e91-2dee-dedb-b68131a5f0ec> | 2007-04-05 18:49:57 +0000 |
| commit | 88a5d0cdda513357496b9d53878618e1620f47e8 (patch) | |
| tree | 4f3c2bedbac4b715ff783de5e1c8d1aefe4395af /Changelog-Trunk.txt | |
| parent | a7fd6bfe9bcce1862b554f5841d9ff1aedf473e3 (diff) | |
| download | hercules-88a5d0cdda513357496b9d53878618e1620f47e8.tar.gz hercules-88a5d0cdda513357496b9d53878618e1620f47e8.tar.bz2 hercules-88a5d0cdda513357496b9d53878618e1620f47e8.tar.xz hercules-88a5d0cdda513357496b9d53878618e1620f47e8.zip | |
* Made a crazy attempt to at least partially synchronize login&char code
* Major edit to the way the servers handle ip addresses, making them obey the "host byte order inside, network byte order outside" rule
- hopefully covered all entry- and exit-points for IP address data
- discovered several places where Gravity's client breaks the convention, will need to come up with a suitable countermeasure for that
- other than that, the code should be portable, except for printing and ipban mask testing (those still assume a specific byte order)
- tested both txt and sql in all usual situations; tested single- and multi-server setups, all seems to work (but watch out for hidden bugs!)
git-svn-id: https://rathena.svn.sourceforge.net/svnroot/rathena/trunk@10162 54d463be-8e91-2dee-dedb-b68131a5f0ec
Diffstat (limited to 'Changelog-Trunk.txt')
| -rw-r--r-- | Changelog-Trunk.txt | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/Changelog-Trunk.txt b/Changelog-Trunk.txt index 3e5f2bb8d..f6f1b156c 100644 --- a/Changelog-Trunk.txt +++ b/Changelog-Trunk.txt @@ -3,6 +3,17 @@ Date Added AS OF SVN REV. 5091, WE ARE NOW USING TRUNK. ALL UNTESTED BUGFIXES/FEATURES GO INTO TRUNK. IF YOU HAVE A WORKING AND TESTED BUGFIX PUT IT INTO STABLE AS WELL AS TRUNK. +2007/04/06 + * Made a crazy attempt to at least partially synchronize login&char code + * Major edit to the way the servers handle ip addresses, making them obey + the "host byte order inside, network byte order outside" rule [ultramage] + - hopefully covered all entry- and exit-points for IP address data + - discovered several places where Gravity's client breaks the convention, + will need to come up with a suitable countermeasure for that + - other than that, the code should be portable, except for printing and + ipban mask testing (those still assume a specific byte order) + - tested both txt and sql in all usual situations; tested single- and + multi-server setups, all seems to work (but watch out for hidden bugs!) 2007/04/05 * Cleaned @whogm. It will display the name of all gms online. If their GM level is above your own, it will only display their name, otherwise level, |