User Ratings

ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 1 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 5 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5

Rate This Project

Login To Rate This Project

User Reviews

  • Rogue works in the "Utilities" program Terminal as you would expect for this port of the classic version of Rogue to Mac OS from the code derived from that of Timothy Stoehr. A makefile is included which shows the program compilation dependencies and all source files. This is a keyboard driven game to retrieve the Amulet of Yendor, and a lot of games like nethack were inspired by this. Unfortunately, the current executable supplied in the current compressed download will not work under what is the current version of Mac OS X.12 on the latest imacs (at least) . The error message is "Bad CPU type in Executable". The pbproj file also isn't readable by the current version of Xcode-beta 9.0, so to get this to work the Xcode command line tools were used and these allow the execution of the make file ie under Terminal change directory to that of the rogue source code and type:- make (the supplied Makefile will be used). If you haven't previously installed the command line tools, typing make will prompt you for them to be downloaded for you to use. Unfortunately there also appears to be a stricter c coding type (as default) than when the earlier compilation occurred. eg in file zap.c error: non void function zapp should return a value. For each such error it is possible to modify the source code so that the code "zapp (" etc became typed with void ie code "void zapp (" etc For some functions this was not sufficient, ie the message became error: conflicting types eg in file zap.c function bounce. Within functions like this , the code "return;" was changed to code "return(0);" and this allowed the make file (as default) to compile without further types of errors to produce an executable version of rogue to run under terminal max os x.12 (sierra). Note that within each .c file there are nearly always multiple changes to be made and that the default compilation only shows the errors for the current file which it first found them. So it took a little while to update the supplied source files as indicated by the errors, but then the program (still with a lot of other warnings which were completely ignored) did then compile using the supplied make file and then it was checked that it still ran under Mac OS X.12