Twine Video Game Peer Review Day: Instructions & Logistics (11.3)

Hello, hello—

Here’s what’s going on for this week’s Twine VG peer review. Per the assignment prompt:

Be prepared to show a work-in-progress version of your video game. It’s difficult to say how much material you should have at this point considering every project will be different. But obviously, it’s more beneficial to showcase more of your game here than less, just for the sake of receiving more feedback.

The first part of peer review day on Thursday, then, will be dedicated to play-testing your peer review partner’s games. Who will your peer-review partners be, you may ask? Here’s how I’m splitting you up for peer review this week:

—Utkarsha and Mav

—Heather and Kady

—Amal and Giulia

—Ben and Jalen

—Jack, John, and Max

—Ian and Sid

—Natalie and April

Here’s what you’ll need to do for the written slice, the likes of which you’ll be discussing for the second part of class.

1.) Share your written slice with your partner before class on Thursday. The earlier the better. Obviously, you’ll need to share your work beforehand by a reasonable hour so people can read through it and comment on it.

2.) Provide both marginal comments and a paragraph-length endnote for your partner. The comments should address specific in-text items, and the endnote should offer a more general assessment of the slice AND suggest possible avenues for improvement.

3.) What should you comment on and/or address in the endnote? These sorts of things:

How comprehensively does the writer describe their designing / making process?

—How well does the writer describe how their game is connected to a specific, defined audience?

—To what extent does the writer discuss the procedural rhetoric and video game logics present in their game?

—Is the argument of the game clear? Why or why not?

If these elements aren’t present to discuss, then be sure to comment on global issues: content, argument, structure, organization. It’s not very helpful to comment on local issues such as grammar, diction, and punctuation at this point, so don’t do that.

3.5) You can handwrite your comments / endnote or type them up digitally. Whatever you decide to do, either bring a hard copy of your feedback to Thursday’s class for your partner or e-mail these notes back to them.

4.) Whatever you do, I need to see the peer feedback you’ve completed. So if you’re doing handwritten comments, make a copy of the annotated slice for me and hand it in on Thursday. Or if you’re doing this work on your computer, e-mail me a copy of your peer review partner’s work with annotated marginal comments and the endnote, all in the same document. 

If you’re going the digital route, I absolutely need to receive this before class to evaluate whether or not you’re completing the peer review portion of the assignment. This is, after all, factored in to the grade for your Twine video game.


One Comment Add yours

  1. Logan M says:

    Questions to Discuss for Twine VG Peer Review:

    1.) What argument is present in this build of the video game at this point? If there’s not an argument yet present, is it clear how one might begin to emerge from the game-in-progress?

    2.) To what extent do you get a sense of why the designer picked the subject matter for the game they picked?

    3.) What sorts of procedural rhetoric and video game logics seem apparent in this build of the game?

    4.) How clearly does the game seem to target a specific audience?


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s