If your team’s Zork III was a train wreck, and you’d like to start Zork++ phase 2 with my solution, it is now available in Canvas in the files tab, in the git bundle “zorkIII_stephen.git“.
(Note that you don’t need this at all for Zork++ phase 1, since that phase doesn’t require any code. I’m posting this now just so I don’t forget later.)
FYI: lab aide hours this Sunday, Nov 2, and Tues, Nov 4, have been cancelled.
The next milestone in your team project has been posted, and is due on Wednesday, Nov. 5th at 5pm. Note that your team will be turning in a stapled hardcopy packet for this, not anything electronic.
Good luck, and may the Zork be with you!
If you worked hard until the last minute and didn’t quiiiiite slip a fully working Zork III under the radar, I’ve decided I’m in a spirit of mercy this morning and will forgive up to 24 hours lateness. (If you already submitted an email, you don’t need to submit another; I’ll simply grab your latest code from github when I start grading.)
Also, I’ll post the file I’ll be using in grading for you to take for a ride; if you discover any bugs when using it that you didn’t see before, the above amnesty offer still applies.
(Remember: you can download this file to your current directory by typing this:
$ wget http://stephendavies.org/cpsc240/westerosv3.zork .
at the command line.)
Here’s a more or less complete list of the one-time commands you should enter to configure your git/github environment for success. Note that the first two include placeholders that you need to replace with your actual text.
git config --global user.name "PUT YOUR FULL NAME HERE" git config --global user.email "PUT YOUR EMAIL ADDRESS HERE" git config --global init.defaultBranch main git config --global pull.rebase false git config --global pull.ff false # allows merge commits on pull git config --global core.editor "vim" git config --global core.autocrlf input git config --global merge.tool vimdiff git config --global diff.tool vimdiff git config --global difftool.prompt false git config --global format.pretty "(%h) %Cblue%an%Creset: %Cgreen%s %Creset(%ad)"
From Wednesday’s class:
In order to access github from the command-line, you’ll need to create and enable SSH keys for it. Ian, as usual, has excellent instructions documenting what you need to do: https://ianfinlayson.net/class/cpsc225/notes/11-git2#github. (You should have already done this if you followed these instructions in CPSC 225.)
I have posted today’s code as a github repo. If you’d like to get a copy of its code, just enter this in your workspace:
$ git clone git@github.com:divilian/anotherzoo.git anotherzoo
and voilà, you’ll have an anotherzoo directory with its contents.
Okay gang, I hope you’re well-rested from fall break. It’s time to take a hard pivot into the team-centric portion of the semester, starting with the new homework assignment!
Note very very carefully that this is a team assignment. Do not start plunging in and working on it yet! Instead, read your email for a very important message about your team assignment, and make contact with your team! They will be your compatriots from now until the end of the term.
That said, do start reading the assignment and begin to wrap your head around it! Lots of fun here, which will take significant time on all y’all’s part to experience. Start building that in to your schedule and expectations!
For your reference, here’s the dungeon that I’m battle testing your Zork II on. You can download it to your workspace via:
$ wget http://stephendavies.org/cpsc240/westeros.zork .
So, it turns out we’re not ready for quiz #3 yet. The material it covers everything up through and including chapter 12, which we haven’t yet reached in class. We’ll have to do quiz #3 the following week, probably in-class Monday the 20th. Stay tuned for more.
On Tuesday the 7th, my office hours will be 1:30-3:30pm instead of the normal 12-2pm.
From today’s class:
A couple of brilliant students have pointed out to me this weekend that there’s an inconsistency between the class diagram and the sequence diagram for Zork hydration: in the class diagram, I have the (new) Exit constructor only taking a Scanner as an argument, whereas the seq diag shows it taking a Dungeon object as well. What gives?
Note that the fundamental “problem” here is: how will an Exit object that’s being hydrated get access to the actual Room objects it needs to connect itself to? One way is to hand its constructor the Dungeon object so it can call .getRoom() on it. Another way is to have the Exit constructor go through the (globally accessible) GameState object to get the Dungeon, which it can then call .getRoom() on. (I’m all ears for a third option.)
The reason for the discrepancy has to do with the version history of the Zork design. The seq diag is older, and is actually from my previous Zork design from a few years ago. In that older design, I did things the “give the Dungeon to the Exit constructor” way. Since then, I’ve decided I like it better to not have to pass that extra argument, since the Exit constructor (or anything in the program, actually) can always get the Dungeon by going through the GameState.
Bottom line: you can do it either way and it’s fine. Since I prefer the new design choice, I recommend you let the class diag “win” over the seq diag in this case. But it’s not require that you adhere to one vs. the other.
Postlude: why not just fix your &@#$*!! sequence diagram, Stephen? Answer: because this exact scenario made for such a good learning experience. 🙂
(Extra credit to Odari and Morgan for calling out this contradiction.)
Here’s my solution to Wednesday’s SWYK check.
There’s a bit of confusion about the Exception subclasses defined in the Zork II design, which is understandable since they use inheritance and we haven’t covered that yet.
Let me make it easy for you. You should create a file called IllegalDungeonFormatException.java and put exactly these contents into it:
public class IllegalDungeonFormatException extends Exception {
public IllegalDungeonFormatException(String e) {
super(e);
}
}
Likewise, you should create a file called IllegalSaveFormatException.java and put exactly these contents into it:
public class IllegalSaveFormatException extends Exception {
public IllegalSaveFormatException(String e) {
super(e);
}
}
You should also create a file called NoRoomException.java with exactly these contents:
public class NoRoomException extends Exception {}
and finally, a NoExitException.java with these contents:
public class NoExitException extends Exception {}
Save those, make sure they compile (to catch typos), and commit them to your repo. From now on, whenever you discover a problem in a .zork file you’re hydrating (like, for instance, that the third line is anything other than literally “===“) you can write this code:
if (bad thing happens) {
throw new IllegalDungeonFormatException("Third line is not ===!");
}
Any time you read a .sav file and find something wrong (like, for instance, that there is no “Room states:” section), you can write this code:
if (other bad thing happens) {
throw new IllegalSaveFormatException("Missing 'Room states:' section!");
}
And of course when you reach the end of the rooms, or exits, while hydrating a Dungeon, you’ll be doing these things:
...
throw new NoRoomException();
and
...
throw new NoExitException();
exactly as described in chapter 10.
To help you wrap your head around the hydration process, check out this sequence diagram (click on it to enlarge) which illustrates it:
The next installment of your Zork project has been posted, and is due midnight, Oct 10th. Read through it as soon as you read this, and get your neurons fermenting!
For those who struggled with Zork I, and did not end up producing a working version, you should start with my Zork I solution. It is in Canvas, in the “Files” tab, and is called zorkI_stephen.git. To pursue this route, you should:
$ git clone zorkI_stephen.git zorkII
This will make a new “zorkII” directory in your workspace. If you go inside it (with cd) and look around, you’ll see a src directory with all my code inside. This new zorkII directory is a git repo (as you can verify with ls -a and looking for .git in the output). Proceed on the assignment using the code in this directory, and perform all git commits in this new repo.
Here’s a pro-gamer tip you may or may not know: whenever you compile (with javac) and get errors, always inspect and fix the first compile error in that list of errors, then re-compile. Don’t pick and choose from all the error messages to decide which one to fix first. This is because of “cascading errors”: if you have something syntactically wrong on line 17, that will often confuse the compiler into misinterpreting all the stuff on lines 18-100, which may give a slew of (ultimately non-)errors.
The Interpreter (specifically, the buildSampleDungeon() function) will instantiate Dungeon, Room, and Exit objects in order to build your little toy 5-room dungeon. These lines are not shown on the class diagram, and PlantUML is being finicky for me so I’m going to choose not to try and add those to the diagram but instead simply affirm the relationships in this announcement.
Thanks to Morgan for catching this.
Not only will every Dungeon object have a Hashtable of Room objects, as shown on the original diagram, but also every Dungeon object will have, as a separate instance variable, a Room object that is designated as “the entry room.” (This is where the adventurer will initially spawn when the game begins. In the original Zork, I think it was “West of House” or some such.)
I added this line to the diagram now, though it’s kind of hard to make out since PlantUML keeps drawing the two lines nearly on top of each other. Anyways, just be aware that there should be two different associations between the Dungeon and Room classes: one for “all the rooms” and one for “specifically the entry room.”
Thanks to Odari for catching this.
Take a look at my solution to SWYK check 1 if you’d like to see where you might have gone wrong. And ask questions any time!
As promised, Zork I (your first real programming assignment of the semester) has been posted. It is due at the end of the month. Warning: procrastinating on this assignment will result in certain death. I can tell you this from years of experience teaching this class. This is true even if you started igpay at the last minute and got it perfect. The Zork homework, and all that follow, are at a completely different level than Igpay was, I promise you.
Suggestion: work on this assignment a little bit every day between now and the due date.
Suggestion 2: for today’s “little bit,” start by simply reading the assignment, start to finish!
This lil’ homework should be relaxing and fun for you, and can be viewed as “the calm before the storm.” (The “storm” is programming assignments #2 and beyond.)
Good luck, adventurer! This little 10-pointer is due next Friday at midnight.
If you’ve instantiated a Scanner object, like so:
Scanner input = new Scanner(System.in);
then you can read an entire line of input from the user this way:
System.out.print("Where do you want to go today? ");
String destination = input.nextLine();
Now, if the user types “New York City“, the value of the destination variable will be “New York City“.
However, if you do this instead:
System.out.print("Where do you want to go today? ");
String destination = input.next();
(stare carefully to see the difference) then Java will only read the first word of the input, and leave the rest dangling on the input stream for later. In this case, the value of destination will be “New“.
Strange but true.
I have posted the code for today’s crazy in-class activity to a github repo. This is the “normal” way to share code, and the way you’ll be doing it all semester with your team.
To get the code, cd to whatever directory on cpsc.umw.edu you’d like to put the code in (you can create a new directory for this purpose if you’d like) and type this command:
$ git clone git@github.com:divilian/CrazyInClassExample.git
This will clone my repo in your local workspace on cpsc. You can then cd into the directory it made (CrazyInClassExample) and see, compile, and run all the code.
You might ask, “in general, how does one know what to put after the “git clone” part? Answer: on the repo’s home page, click the green box that says “Code” and copy the link in the “SSH” tab. That’s what you paste immediately after typing “git clone“.
(Btw, if you don’t have your github SSH keys set up like Ian specified, you’ll instead choose the “HTTPS” tab, and paste that URL after “git clone” instead.)
Finally, the answer to the activity is:
Some exciting upcoming department events: please consider attending!
Here’s the latest version of our Car class that we worked on in lecture today.
The next homework due (after “igpay“) is a thoughtful written response to a book section and article I have posted. All the details are here. It’s due to my manila folder at 5pm on Monday Sep 15th. Send questions!
The purpose of the first programming assignment is for you to get used to using the Linux CLI (command-line environment) with vim and git and javac.
Therefore DO NOT use NetBeans, IntelliJ, Eclipse, or any other IDE to complete this assignment! That would be a complete waste of time.
My purpose isn’t to test that you can write basic Java code. I already know you can write basic Java code, otherwise you wouldn’t have the prerequisites necessary to get into this course. My purpose, instead, is to help you get up to speed being productive in a CLI.
A number of talented lab aides are at your disposal this semester for help with your understanding in learning how to program! I’ve put their names and weekly date/time/locs in the office hours tab.
Here’s a helpful list of common String methods you may find handy to use in your igpay project.
If you didn’t turn in the homework due Saturday on time, you forfeited the one point it was worth, which of course isn’t much. However, you still have to do this homework! If you don’t, you won’t be able to do much of anything else in the class.
If you’ve received an accommodation letter from the ODR, and sent it along to me, thank you very much. Let me be specific about how I will handle all of these:
The first programming assignment of the semester has been posted, and is due at midnight on Thursday, September 11th. Good luck, and ask questions!
CPSC 225 currently shows “full/overenrolled” on Banner, but that’s just because Dr. Finlayson wants to be notified when people join so he can set them up on the server.
So: if you haven’t previously completed CPSC 225, and you’re not currently registered, please send an email to ifinlay _AT_ umw _DOT_ edu and ask to be added.
Here’s the essence of that June 2nd email I sent to the class:
As the summer months truly begin to set in, and you get into the rhythm of your break from classes, I’d like to interject a dose of reality. If you’ve had me in class, you’ve heard this spiel before. If not, then allow me to highlight some incontrovertible facts of the universe:
Computer programming, like playing the piano or marathon running, is an activity that requires consistent practice in order to perform at a high level. There’s simply no way you can practice your instrument dutifully for three months, then take three months off, and not suffer a major degradation in your skills. Similarly, there’s no way to train like an Olympian for three months – running 15-20 miles a week – and then take three months off without losing nearly as much stamina as you’d gained.
Your body simply doesn’t work that way. And it turns out, neither does your brain. (If you didn’t realize this, your brain is actually part of your body! And it obeys all the same physical rules.)
Every variable you declare, function you call, and while-loop you write strengthens the logical component of your mind that you need for programming. It develops and reinforces those patterns you’ll need to rely on in the trenches, when your frontal lobe is allocated to contemplating larger concerns like architecture, design, and strategy.
…When I begin the first lecture on August 25th at 11am, I’ll be assuming you have mastered the Java material in CPSC 220 and are ready to climb higher from there. I will not be spending the first month or two reviewing the 220 material and trying to wake you back up from your coma.
Greetings, and welcome to the fall 2025 edition of CPSC 240: Object-oriented Analysis & Design with Stephen!
This site is gonna be hip-hoppin’ with all kinds of great stuff real soon, so stay tuned!