Next planned steps in plomrogue development:
-BOTH SERVER/CLIENT:
-
-- implement better server/client architecture, meeting these criteria:
- - keep interaction of server and client in the filesystem (as currently
- happens by use of plain text files and fifos) to allow for easy scripting
- - allow for specific requests of the client for specific server data (such as:
- "what path do you propose for the player character to get from A to B?")
- - reduce hard disk i/o for server/client interaction (use fifos only?)
- - further avoid exits that keep the server running and the lock file existing
- when it shouldn't
+IN GENERAL:
- check for return values of *printf()
-SERVER:
+- be more strict and humble when allocating memory from the stack
-- implement field of view / line of sight and obstacles for those on the map
+- expand use of hardcoded_strings module(s)
-- get rid of the hard-coding of the MAGIC MEAT item type and its use mode
+BOTH SERVER/CLIENT:
-- is it actually useful to define map object action ids in the config file?
+- make server and client communicate by specific world state info requests
+ in server/out, replacing server/worldstate
-CLIENT:
+SERVER:
-- enable toggling of window borders
+- optimize too-slow AI / FOV algorithms
-- enable toggling of showing "\n" in the window content either as newline breaks
- (as currently) or as " / " (without newline break) for more efficent screen
- estate use
+- save confserver/world data in record and save file, too; handle them like god
+ commands
-- does get_n_of_keybs() really need to be its own function? (only used once)
+CLIENT:
+
+- enable toggling of window borders
-- transform Keybindings struct series from a linked list into an array
+- make log scrollable
projects / plomrogue / blobdiff