*** empty log message ***
*** empty log message ***
*** empty log message ***
*** empty log message ***
*** empty log message ***
minor nit
*** empty log message ***
switch from Event to EV
remove storable compatibility mode
slightly better can_merge
- fix dmshell filehandle - zero-initialise faceinfo - for various reasons, the AIO watcher has to have similar priority as the server ticker. before thta, the server ticker could preempt the map scheduler completely when overloaded, which disabled the only way to reduce load.
*** empty log message ***
tweaking
add and sue Coro::Debug
rent was calling blocking functions in the main coro. doh.; also, do some cleanups
lock map_data in addition to map_load when loading a map, possibly avoids the crash seen today
- this seems to fix almost all known cases of players staying around for no good reason: player throws stuff, picks it up. this also leads to players not losing their missile weapons. - async vs. async_pool means we keep stdout...
add books from books.pod via some most dire hacks
- implement two new helper functions: cf::cache => load and process a file, caching the result in the db cf::fork_call => execute a given sub asynchronously (e.g. for cpu jobs) - make use of it in ext/map-world.ext, greatly speeding up worldmap loading. - preliminary garbage added to cf::pod.
- rename load_xxx to reload_xxx, all of which are guarenteed to a) do their thing b) take no parameters c) almost certainly fail when not run asynchronously - considerably improve dmshell (and support postfix-'&' to move job in bg) example data and execution times on my system: reload_regions 0.0007s reload_facedata 0.69s reload_treasures 0.0156s reload_archetypes 0.035s all of them run without impeding the running server (unless the server starts to use e.g. an archetype refering another archetype not yet defined), exccept for reload_perl, which is very heavy.
dmshell improvement
- better dm shell - minor cleanups - added cf::dumpval, cf::player::list_logins and $player->maps
moved perl extensions into server codebase, where they belong
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, select a symbolic revision name using the selection box, or choose 'Use Text Field' and enter a numeric revision.