Next planned steps in plomrogue development:
-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()
+IN GENERAL:
-- be more strict and humble when allocating memory from the stack
+- expand use of hardcoded_strings module(s)
-SERVER:
+- use __func__ instead of f_name
-- 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?
+BOTH SERVER/CLIENT:
-- for game continuation, replace re-playing of whole record files with loading
- game state snapshots / save files
+- make server and client communicate by specific world state info requests
+ in server/out, replacing server/worldstate
-- why does an MapObjAct id of 0 fail?
+SERVER
-- make config file define to which map object type the player belongs
+- document server commands
CLIENT:
- enable toggling of window borders
- make log scrollable
+
+- re-work unnecessary complex command / keybinding / server message mapping