server icon indicating copy to clipboard operation
server copied to clipboard

Eressea is an automated play-by-mail strategy game server.

Results 41 server issues
Sort by recently updated
recently updated
newest added

Quote from Slack: aha, bei dem zweiten commit hat sich lc_write geändert, das ist für Gebäude, die in building_age eine Lua-Funktion aufrufen. Huh. Ich schätze, Wurmlöcher tun das? Irgendwas sicher....

enhancement

I don't think they should return AT_READ_FAIL, or if they should, then I don't understand why they do not all do it? Investigate!

question

there is no error handling in jsonconf.c (except log_error messages), should probably be added, especially because the building code spews errors during the unit tests.

bug
enhancement

There are some mail processing scripts that still live in a SVN repository (where?) and sit in ~/src/scripts. These need to be moved into github, under the process directory. They...

enhancement

209 if (set_email(&nf->email, email) != 0) { 210 log_error("Invalid email address for subscription %s: %s\n", itoa36(subscription), email); leaked_storage: Variable nf going out of scope leaks the storage it points to....

bug

Bei den ganzen Gerede über Konstanten neulich, habe ich mir mal überlegt, wie man das besser machen könnte und das kam dabei heraus: https://github.com/eressea/server/compare/develop...stm2:6628b2d7805c13f4d8be8b597ed3162a1b93e41b Statt ``` C int multi =...

enhancement
question

Piraten fahren ggbf. von einer Landregion zu einer benachbarten Landregion ohne zu prüfen, ob es einen Weg über Ozean dorthin gibt. Entweder sollte piracy prüfen, ob das geht (Pfad der...

bug

``` .......................................F.................... ............................................................ ....................... ``` 362 Assertions checked. 1) Failure (tests.e3.castles.test_build_castle_stages): ./scripts/tests/e3/castles.lua:74: expected 250 but was 10 Testsuite finished (142 passed, 1 failed, 0 errors).

See https://bugs.eressea.de/view.php?id=2155 for discussion

enhancement

When running valgrind with `--show-reachable=yes --leak-check=full`, it currently reports 131 memory leaks, and all but four of them are classified as "reachable", meaning they are probably in some static variable....

enhancement