1 Next planned steps in plomrogue development:
5 - make server and client communicate by specific world state info requests
6 in server/out, replacing server/worldstate
8 - check for return values of *printf()
10 - be more strict and humble when allocating memory from the stack
12 - may err_line store the processed line internally as it does the line count
16 - implement field of view / line of sight and obstacles for those on the map
18 - is it actually useful to define map object action ids in the config file?
20 - make shape of map (and diagonal movement penalty) configurable in config file
22 - for game continuation, replace re-playing of whole record files with loading
23 game state snapshots / save files
25 - why does an MapObjAct id of 0 fail?
29 - enable toggling of window borders
33 - implement server-config-file-like parsing for client-config-files, too