Next planned steps in plomrogue development:
+IN GENERAL:
+
+- expand use of hardcoded_strings module(s)
+
BOTH SERVER/CLIENT:
- make server and client communicate by specific world state info requests
in server/out, replacing server/worldstate
-- check for return values of *printf()
-
-- be more strict and humble when allocating memory from the stack
-
SERVER:
-- implement field of view / line of sight and obstacles for those on the map
-
-- is it actually useful to define map object action ids in the config file?
-
-- for game continuation, replace re-playing of whole record files with loading
- game state snapshots / save files
+- consider
+ <http://www.plomlompom.de/PlomRogue/plomwiki.php?title=TheCreationOfSpace#comment_0>
-- why does an MapObjAct id of 0 fail?
+- save confserver/world data in record and save file, too; handle them like god
+ commands
-- make config file define to which map object type the player belongs
+- ensure atomic re-writing of savefile
CLIENT: