4 plomlompom tries to build his own roguelike. It doesn't do much yet (although
5 plomlompom has insanely ambitious long-term plans).
7 You can move around a player on an island and meet different enemies. You have 5
8 hitpoints to lose before death. Enemies start with different amounts of
9 hitpoints, depending on their species. Dead enemies become dirt, skeletons or
10 "magic meat" -- such objects can be collected, and "magic meat" can be consumed
11 to gain hitpoints (if allowed to lie on the ground for a while it may even
12 multiply ...). Note that different kinds of movements/actions take different
13 numbers of turns to finish.
15 Enemies' AI is very dumb so far: Each turn, they look out for actors of
16 different species to flee from (if their type starts out with more hitpoints
17 than they have) or (if the opposite is the case) move towards for purposes of
18 attack. If they see no enemy, they search for and consume "magic meat".
20 Every move of yours re-writes a file "savefile" that describes the new state of
21 dthe world, if more than 15 seconds have passed since its last writing. Once you
22 re-start the game, the game state is recreated from the "savefile" file. To
23 start over in a new world, simply delete this file.
25 System requirements / installation / running the game
26 -----------------------------------------------------
28 The game is expected to run on Linux systems that contain the ncurses library.
29 (It may also work on other Unix-like systems with ncurses, who knows. See
30 <https://github.com/plomlompom/plomrogue/issues/2#issuecomment-50972436> for OS
31 X compatibility.) Do the following steps:
33 $ git clone https://github.com/plomlompom/plomrogue
38 (If you got a redo build system installed and in your $PATH, you could also do a
39 simple "redo" instead of "./redo". The ./redo script calls a simple partial
40 shell script implementation of redo stored below build/redo_scripts/, written by
41 Nils Dagsson Moskopp a.k.a. erlehmann.)
43 ./redo generates two executables ./roguelike-server and ./roguelike-client.
44 ./roguelike is a pre-existing shell script that merely executes both of them,
45 with the server as a background job. You can also ignore the script and start
48 Client's keybindings and window management
49 ------------------------------------------
51 Multiple windows may fill the screen. One of these will be selected as "active"
52 – identified by dollar signs enclosing its title. Active windows may come with
53 window-specific keybindings. Furthermore, global keybindings are available no
54 matter what window is selected.
56 Hit "W" (per default global keybindings) to switch the active window to a view
57 that allows changing its geometry. One more hit on "W" switches the window to a
58 view that sports (and allows changing its) window-specific keybindings. (One
59 further "W" will return the window to its default, "normal" view.) The global
60 keybindings are visible (and can be changed) in the "Set global keys" window,
61 those of the window geometry configuration in the "Set window geometry keys"
62 window, and those of the window-specific keybindings configuration in the "Set
63 window keybinding keys" window; by default, the latter two are not visible, but
64 may be turned on by (per default keybindings) hitting the keys "F6" and "F7".
66 Keybindings and default window selection / visibilities / geometries are read
67 from the textfile ./confclient/interface_conf by default, or by another one
68 named by the -i command line option of the client. Some other default window
69 configurations are stored below ./confclient/single_windows/: "map", "info",
70 "inventory" and "log". Each of these opens up only a single window into the
71 client, filling up the entire terminal. This may be useful for running multiple
72 clients in parallel in multiple terminal windows that can be managed by one's
73 own window manager choice, instead of relying on plomrogue-client's bizarre
74 in-client window management.
79 Once you start a new world, every move of yours is recorded in a file called
80 "record". It gets overwritten when a new game world is started after deletion
81 of the "savefile" file. Run "./roguelike -s" to watch the current game's
82 recording from the beginning. Hit any player action key to increment turns (they
83 will not trigger the actions usually mapped to them, only repeat the actions
84 done at that point in the game as defined in the "record" file). Keys to manage
85 windows, scroll on the map and quit the program do their usual thing. Append a
86 number to the -s option (like "-s100") to start the recording at the respective
89 Hacking / server internals and configuration
90 --------------------------------------------
92 The game world is set up and made subject to player commands by
93 ./roguelike-server. It's controlled by commands explained in the file
94 ./SERVER_COMMANDS. The server usually reads these from the files ./server/in
95 (written to by ./roguelike-client), ./confserver/world, ./record and ./savefile.
97 All source files are thoroughly documented to explain more details of
98 plomrogue's internals. The ./roguelike-server executable can be run with a -v
99 option for helpful debugging info (mostly: what messages the client sends to the
100 server). Server and client communicate via files in the ./server/ directory
101 (generated when the server is first run). The ./server/in file is read by the
102 server for newline-delimited commands. The ./server/out file contains server
103 messages to be read by clients. The ./server/worldstate file contains a
104 serialized representation of the game world's data as it is to be visible to
105 the player / the player's client.
projects / plomrogue / blob