Game Dev Studio @gamedevstudio1 - Tumblr Blog

ALEX HOCHBERG

BINDING OF ISAAC HOMEWORK 8 (NOT FAVORITE GAME BUT STILL(

Objective(s): Dwell deeper into the basement and kill your mother.

Game Space: Zelda dungeon/Robotron/Smash TV like playing field

Components: Treasures, Tears, hearts, soul hears, enemies, boss

Core Mechanics: Run and Gun

Secondary Mechanics: Collect treasure, hearts, coins, spend money and bomb doors, go down trap doors

Conflict:

Enemies try to kill you.

Trying to cosverse health and keyes

Health and Bombs are limited

Limited

Progression:

1 Clearing the enemies to open to doors

2 Do this again and again to get to the boss eventuall

3. Deafet Boss

4. Go down trap door

3 Repeat 1 to 4 until you reach mom.

4 Kill mom...

5 . Reapeat 1 to 4

6. Repeat 1 to 3

7. Kill moms heart

8 Choses heaven or hell. Lets fight!

9. Kill Satan or Yourself (He looks like Isaac)

Description/Rules:

Each floor has a treasure room, boss room, a secret room, a super secret room, and a shop.

Isaac dies when you run out of health and you must from the beginning.

ROGUELIKE

Choices:

Pick up some items that hurt or not you like some of the pills.

Whether to convert hearts to money at the bloodstation

Homework 6

Bohnanza Alex Hochberg

While playing Bohnanza I came arose a problem, I don't I ever had before. Me and my group when to play a commercial card that none of us I have ever played before. Same with board games. Think about it when, you play a board or card game, the one who owns the game or brought it over has played it before. The majority of our time that was set aside for us to play the game, we just trying to figure out how to play it. The manual was long and a bit complicated. So it took awhile before we had any grasp of what we suppose to do. When are generally introduced to a board or card game, some else has played it before. They understand the structure of the game, they know the general rules, they understand how the game progresses. They probably don't have the rule book memorized but they understand the mechanics of the well enough to make the game work. You can ask the person who played the game before questions about the how the game is played. You can't ask manual questions. The person who played the game before can give starting point to understand a game. When explain a game to someone else you compile the rules and structures in understandable human code. When you explain chess to someone, you say the knight moves in a L shape that jumps over pieces instead of the knight must move 2 squares either up, left, down and right and then move1 square perpendicular the previous cardinal directions while going through the other pieces. Being taught a game is an experience.

Videogames get by having most of the rules of the game being in the background and hidden from you. Many times you're taught the game through structured tutorials where you're taught the most of the rules on at a time. Some games like metroid make you learn the rules yourself. Look at this.

http://www.nintendolife.com/news/2013/05/miiverse_super_metroid_too_taxing_for_todays_gamers

http://www.destructoid.com/wii-u-owners-don-t-know-how-to-play-super-metroid-253895.phtml

.To play a board and card game, you have to someone know all the rules to make the game run. You're one the who has to make your piece a king in checkers when you bring to the other side, the game itself doesn't do that. The players are the one who enforce the rules of the game.

I'm sorry I didn't really talk about Bohnanza but this is the experience I truly remember this game. Generally a board doesn't function as good a toy when you don't the rules. Unless your mouse trap, who actually knows the rules for mouse trap anyway?

HW#2

Partners: Yao Chen, Reem A. Hassan

Sepak = kick/smash(Malaysian)

Takraw = rattan/woven ball(Thai)

Component:

Court: area of 13.4m * 6.1m ,width of boundary lines=0.04m, center line=0.02m,

Quarter circles near the center line ->radius:0.9m each

Service circle radius:0.3m in radius, location: 2.45m from the back line of the court and 3.05m from the sidelines, line width=0.04m

Post height=1.55m for men and 1.45m for women, placed 0.3m away from the sideline and in line with the center line

Net: made of nylon with 0.06m to 0.08m mesh, 0.7m in depth, and no shorter than 6.1m in length, height=1.52m for men and 1.42m for women

Ball: spherical, made of synthetic fiber of one woven layer

Goal:

-deliver the ball over into the opponent’s court in such a way that the ball is difficult to be returned and does not go out of bounds.

-win a set with score of 15 or more (up to 17) with a lead of 2 points minimum.

- win 3 out of 5 sets.

A match set is played by 2 teams(regus), 3-5 players per team, 3 on court

There is a match referee and a linesman stationing on each end of the net, and one court referee stationed behind one of the match referees.

One game set is played over 15 points, with a deuce being played over 17 points:

-when the game starts, the right inside player throws the ball to the server, and the server will initiate the first serve

Following an initial serve, each team has up to 3 touches of the ball before having to return it across the net.

The Feeder and Server will help set up the ball so that the striker can smash the ball across the net.

Horse-kick serve

Jaw-dropping sunback spike- the spiked ball can travel towards the opponent in excess of 120km/h.

Rules and Regulations:

Substitution occurs after one set ends.

A team scores when the opposing team fails to return the ball across the net after three touches with the ball, or when the ball is returned across the net but lands outside of the court.

-player may use any part of their legs, head, and torso to handle the ball, but not with their arms and hands.

-starting from the beginning, service switches from one team to another every 3 turns. Service- over occurs after every 3 consecutive points scored regardless of the team which has earned the points. After every consecutive points, ball service changes to the opposing team for the subsequent 3 consecutive points. This service-over process continues until a game set ends.

-At deuce (when both sides are 14-14), the service alternate on every point.

-the ball can be repeatedly kicked by one person up to 3 times.

-a service is valid if the ball goes across the net, whether it touches the net or not, and inside the boundary lines of the opponent’s court.

-during a spike, if the ball flies out of bound and the opponent is in contact with the ball, then 1 point goes to the team performing the spike

Scoring:

-whenever a team commits a fault, a point is awarded to the opponent side

-a set is won by the side which scores 15 or more with a minimum difference of 2 points over the opposing side, or when a side first reaches the score of 17.

-each side is entitled one tactical time-out in each set, and each such time-out lasts a maximum of 1 minute. Time-outs may only be called by coach when the ball is not in play.

-on the last set, the game goes up to 8 to win that set.

Faults:

-when throwing the ball for the serve, the inside player steps on or crosses over the quarter lines or center lines

-server stands on the service circle line before and during the service

-server does not kick the ball on the service throw

-ball touches players on serving side before the ball goes over the opponent court

-ball falls outside of the outer court boundaries

- ball does not go over the net

- player uses arms or hands to directly touch the ball, or facilitate a kick by touching the other objects and other surfaces with their arms or hands.

-ball touches the arm

-creating distracting manner or noise

-touching the ball more than three times in succession by players from the same team.

-holding or carrying the ball

-ball touches the ceiling, roof, or the wall

-using external objects as a form of support to playing

Core Mechanics:

-kicking, leaping,

-walking, throwing (at the start of the game only),

-controlling the ball with

head, chest, or knees

Choice:

-Substitution of team players

-delivering the ball across the net

-strategic moves: ex. Spiking

Conflict:

-deuce

-preventing opponent from scoring

-distracting opposing team while serving: ex. yelling, screaming, shouting

HW#1

Partners: Reem A. Hassan, Lucas Dias

Game: Ninja Jutsu

Contents/Materials: Bag of palm-sized hand balls, open enclosed area (not included)

Objective: Be the last ninja standing (ultimate ninja-sensei)

Players: 2+ Ages 10-1080

Rules:

~Players(ninjas) start off in any position they desire, holding one ninja ball(Kunai) in one hand and standing 2-3 arm lengths away from opposing ninjas.

~At the start of the game, ninjas take turns throwing their Kunai at opposing ninjas.

~Turns equate to moving a ninjas body in one fluid motion, then freezing for the remainder of the game.

~Ninjas are able to grab Kunai from the ground, along with resetting their position.

~Turns include:

-Throwing/Dodging Kunai -Grabbing Kunai from ground -Resetting position

~Ninjas are unfrozen and able to move while throwing Kunai and defending from oncoming Kunai.

~When a ninja is hit with a Kunai from the shoulder down, they are considered to be

mortally wounded and are out of the current challenge (sent to the medical sensei).

~Ninjas are allowed to attempt grabbing an oncoming Kunai. However if it hits the ninja, then they are sent to the medical sensei.

~The last ninja to not have been wounded is the ultimate ninja sensei.

Anbu Ninja Corp ~Original Ninja Jutsu, separated into 2 teams

Run the witch wants to eat you ~update~

Final Project - John, Jason, Stanford and Kirsten

The Campaign

We are making a 2 player versus RTS based on the lifecycle of a political campaign in a small town. Each player will start with a certain amount of money and be able to buy items that influence the townspeople. The more people influenced, the more money received by donors. By the end of the time, whichever side has influenced more people will win the election.

Jason Schapiro - programmer / designer

Kirsten Sugar - designer

John Roth - programmer / designer

Stanford Medenhall - designer

Final Game (Play it!):

Beta for playtesting:

Early Prototypes:

#political #game #flash

Final Project – Yao, Kathy, and Trevin

Update: 04-28-13

Here is a set of instructions for our game, Color-Coded:

Color-Coded is a 2-D side-scrolling competitive game where players are racing against each other in a color-coded background.

Players are constantly running in one direction throughout the game. As they move along, players are entitled to press,and hold if necessary, corresponding keys that are representative of the colors to match the colors of the background

The background is made up of strips of 9 colors: white, gray, black, the primary and secondary color trio. All colors besides black,gray and white require the player to press keys to "make" the color.

The gray color strip is known as the random effect strip. It induces at 50/50 chance good/bad effects on the enemy player respectively. The effect is activated if the player so chooses.

If the colors are not "decoded" correctly, players will be slowed in the competition.

Each player has 4 keys to control, three of which for the three primary colors, respectively, and one for activating a random effect when passing the gray strip.

The beta version includes two players only:

Player 1's commands: Red-A,Yellow-S,Blue-D,Gray-W

Player 2's commands: Red-left,Yellow-down,Blue-right,Gray-up

That's it for now. More on Tuesday's beta release!

------------------------------------------------------------------------------

Genre: 2-D Side-Scroller Platformer Racing Game

Narrative/Summary: A bunch of stick figures competing against each other in a running race.

Objective: Be the first to reach the finish line!

Game Space: The screen is split vertically into several layers of platforms. The side-scrolling effect is asynchronous among the platforms

Components: Stick figure players, obstacles, falling objects, boost-ups, full-screen effect items, race

Core Mechanics: evade obstacles in different ways, pick up stuff

Secondary Mechanics: AOE effect of items, randomization of item spawns

Conflict: A bunch of stick figures are running to death in order to win a race full of life-threatening obstacles

Progression: Outspeed everyone else in the race

Choice: ways to evade obstacles

Rules:

The stick figures are constantly running in one direction throughout the race, but can be slowed down or stopped by obstacles or other effects

Some items that a player picks up will have an effect on all other players except the player who picked them up

Winning solely depends on time. It’s possible to have multiple players winning

Considerations:

Use the One-button mechanism on the arduino for a certain event where everyone has to reach for the button

Falling down on/jumping onto other peoples’ platforms

Have some BAM (big ass monster) chasing the stick figures as they race

Allow players to go left or right

Team Members:

Yao Chen – designer, moderate programmer (helper), UI, animations, sounds

Kathy Ou – designer, hardcore programmer (basically involved in everything code-wise)

Trevin – Hardcore Programmer (with focus on special effects)

Final Project - Jifeng, Collin, Lucas and Alex

Last update:

Presentation | Source

Update 5/1/2013:

So far:

Suggestions:

make the score indicator bigger -> easy

add a restart button -> easy

use SPACE to build -> easy

add an end game condition or time limit -> easy, maybe a 5-minute time limit or a max score, like 20

power-up to build/destroy indestructible blocks -> medium

line of sight -> medium

when no more blocks exists, you can't build / it's hard to build the blocks -> hard, could be solved by allowing to build on the walls and improving the build algorithm

synchronize blocks -> hard

synchronize scores -> hard

use UDP instead of TCP to increase speed -> hard

use right click to build blocks -> not possible due to Flash limitations

Update 4/29/13:

After many hours of hard work, we've got LAN multiplayer!!! Also a new tileset!

Update 4/27/13:

The network interface seems promising! So far we can send messages from one client to another.

Here's our new hero:

Update later 4/26/13:

Improved shadows!

Update 4/26/13:

We've built our own dynamic shadows engine! Who needs gameplay when you have graphics? XD

Update 4/25/13:

We've got a cubic player equipped with a gun which can build/destroy tiles. Also, there's a cool retro looking cave, lighting effects and particle effects.

Creation 2/25/13:

Description: We are planning to do a 2D platformer using a destructible tiles mechanic. We will first develop a fighting game with 2 players on top of a platform with guns able to create and destroy tiles, with the objective of making the opponent fall off the platform. After developing the basic mechanics, we will add items, enemies, and maybe some kind of progression to make it a co-op game.

Inspiration: games with destructible environments, like Liero, Worms, Terraria, Tanks, Dig Dug, etc. (what? Minecraft?)

Dream team:

Jifeng

· Character & Animations Artist

· Professional Beta Tester

Collin

· Senior Software Engineer, Gameplay & User Interface

· Abandonware Games Specialist

Lucas

· Senior Software Engineer, Mechanics & Collisions

· Coffee Addict

Alex

· Environment, User Interface & Sounds Artist

· Jedi Knight in Residence

Final Project - Sheree, Reem, Krystel

Run! The Witch Wants To Eat Us! is going to be a two-player 2D - platformer based off of the Hanzel and Gretel story where the players choose to be Hanzel or Gretel. The two players must escape the Witch’s Candy Mansion and reach safety. While there is only one level, there will be three different stages: the Witch’s Candy Mansion, a Forest and a Mountain. Both players will have their own scores which will be added at the end. The score is based on time and how quickly the game can be finished . The score can be increased through power ups and collection of items. It can also be lowered if the players are injured by the Witch or obstacles. If one player is dead by the end, their score is not counted in the final score. There are three different endings to the game which detail a lose state and two win states.

Sheree – Character Design, Interface/HUD, Sound

Reem – Programmer

Krystel – Level Design, Interface/HUD, Sound

FINAL COUTDOWN

Hey Everyone!

Here are the constraints for your final project: http://bit.ly/17gbu57

Please make sure to update the tumblr as you create your game. It will be a huge part of your grade!!

PS

Check your email for the pre-release links to Polycode!

Syed

#gamedevstudio

Game Show Interface - Kathy

The above are pictures for a game show interface made using an Arduino. There are two buttons on the breadboard and the interface was set up so that as long as one player is holding down their button (indicated by their respective LED turning on) the other player's LED won't turn on even if the other button is pressed and held down. If the two players "simultaneously" press their buttons then the system will decide for itself which player will be the winner in the end.

MoMa TRIP by Stanford Mendenhal

At the MoMa exhibit I played Canabalt, Passage, Vin Ribbon, and Myst. I also looked at some art including Mapping the Internet, a data visualization print, and the Babel Blocks, a group of block art based on diversity. I loved Passage because it showed how conceptual game design is becoming and how much thought goes into making a game. Before, one might think of games as being made to be played for fun, but with this game, you can see how much “design” goes into making a game. Mapping the Internet was also interesting because I am recently interested in data visualization and have recently seen a lot of interesting things done with it. Vin Ribbon was really interesting because it also was an innovative way of using design. I loved how minimal it was, and its use of sound as an integral part of the game.

Rayman by Stanford Mendenhall

Rayman Origins for the PS Vita has a simple narrative where Rayman and other characters that can be purchased by receiving a certain amount of Electoons. Each character you can play as has similar characteristics in term of how they attack and get around. The core mechanics of this game is kick, jump, running up walls, hover, swim and shrink to fit in certain locations. In certain stages you can also get on top of a flying machine where you have to attack enemies and collect Lums for a chance to get an extra Electoon toward the end. This game is based on levels with different tasks, some involving saving a princess, similar to Super Mario. The design of this game is well done, containing harmony, balance, and rhythm. This game exposed me to the psychology of game design. I made me question what makes one know a character is an enemy. There were some brightly colored characters you knew were enemies because they contained spikes. It taught me to look into how texture, character attributes, and color play into the design of a charachter.

Stencyl Game by Stanford Mendenhall

1. Have you taken any game programming courses or other programming courses? If so what?

Python

2. What programming languages do you know? And how well?

Python

C++(most of it)

3. What frameworks or game engines have you used? What do you feel most comfortable using?

I’ve used Gamemaker a while back.

Recently working with Stencyl

4. Do you have any 3D modeling experience? If so, how much?

3D1

5. Do you have any graphic design experience? If so, how much?

Yes. Interning at Sculptor’s Guild

6. Do you have any experience working with sound? If so, how much?

No 7. If you were part of a game development team, what role would you feel comfortable and/or interested in filling?

Creating the graphics

Chicken by Stanford Mendenhall and Raymond Gao

/*

Button

Turns on and off a light emitting diode(LED) connected to digital

pin 13, when pressing a pushbutton attached to pin 2.

The circuit:

* LED attached from pin 13 to ground

* pushbutton attached to pin 2 from +5V

* 10K resistor attached to pin 2 from ground

* Note: on most Arduinos there is already an LED on the board

attached to pin 13.

created 2005

by DojoDave <http://www.0j0.org>

modified 30 Aug 2011

by Tom Igoe

This example code is in the public domain.

http://www.arduino.cc/en/Tutorial/Button

*/

// constants won't change. They're used here to

// set pin numbers:

const int buttonPin = 2; // the number of the pushbutton pin

const int ledPin = 13; // the number of the LED pin

const int buttonTwo = 4;

// variables will change:

int buttonState = 0; // variable for reading the pushbutton status

int buttonPosition=1;

void setup() {

// initialize the LED pin as an output:

pinMode(ledPin, OUTPUT);

// initialize the pushbutton pin as an input:

pinMode(buttonPin, INPUT);

pinMode(buttonTwo, INPUT);

}

void loop(){

// read the state of the pushbutton value:

buttonState = digitalRead(buttonPin);

buttonPosition = digitalRead(buttonTwo);

// check if the pushbutton is pressed.

// if it is, the buttonState is HIGH:

if (buttonState == HIGH) {

// turn LED on:

digitalWrite(ledPin, HIGH);

}

else if(buttonPosition==HIGH){

digitalWrite(ledPin, HIGH);

}

else {

// turn LED off:

digitalWrite(ledPin, LOW);

}

Reem, Sheree, Krystel

Working with arduinos!!

#hbngfhfdngslkjdg please mute

Simoino - Lucas and Collin

A simple Simon game using Arduino!

Source

Trending Blogs

Recently Viewed Blogs

Game Dev Studio