• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0

Breakout code design exercise

2 posts in this topic

[font=arial, sans-serif][size=3]Hi all,[/size][/font]

[font=arial, sans-serif][size=3]Id like to do an exercise to come up with a code design for the traditional game breakout game (google if unsure)[/size][/font]
[font=arial, sans-serif][size=3]using an entity component system to see what designs you all come up[/size][/font]
[font=arial, sans-serif][size=3]with, and to practice my designing skills =P.[/size][/font]

[font=arial, sans-serif][size=3]I have my own ideas how to design it, but im more interested in the way other people think, and hopefully I might learn a thing or 2.[/size][/font]

[font=arial, sans-serif][size=3]Im particularly interested in designs engineered towards a data-driven entity[/size][/font]
[font=arial, sans-serif][size=3]system such as Artemis, where data and behaviour are split into components, and systems processing those components:[/size][/font]


[font=arial, sans-serif][size=3]For simplicity, I want to focus on:[/size][/font]

[b][font=arial, sans-serif][size=3]Objects:[/size][/font][/b]
[font=arial, sans-serif][size=3]- Ball[/size][/font]
[font=arial, sans-serif][size=3]- Paddle[/size][/font]
[font=arial, sans-serif][size=3]- Blocks[/size][/font]
[font=arial, sans-serif][size=3]- Powerups[/size][/font]
- Bullet

[b][font=arial, sans-serif][size=3]Behaviours:[/size][/font][/b]
[font=arial, sans-serif][size=3]- Ball travels with linear velocity, initially at a random upward angle.[/size][/font]
[font=arial, sans-serif][size=3]- Ball bounces off left, top, and right boundaries[/size][/font]
[font=arial, sans-serif][size=3]- Ball bounces of blocks[/size][/font]
[font=arial, sans-serif][size=3]- Ball bounces off paddle[/size][/font]

- Paddle can move left and right

[font=arial, sans-serif][size=3]- Blocks disappear when a ball touches them[/size][/font]
[font=arial, sans-serif][size=3]- Blocks disappear when a bullet touches them[/size][/font]

[font=arial, sans-serif][size=3]- Powerups have a chance of spawning when a block disappears[/size][/font]
[font=arial, sans-serif][size=3]- Powerups travel down the screen until they hit the bottom boundary, at which point they are destroyed.[/size][/font]
[font=arial, sans-serif][size=3]- A powerup is engaged when it collides with the paddle[/size][/font]
[font=arial, sans-serif][size=3]- Powerups do not collide with blocks[/size][/font]
[font=arial, sans-serif][size=3]- Powerup 1 - Ball sticks to paddle instead of rebounding[/size][/font]
[font=arial, sans-serif][size=3]- Powerup 2 - Paddle is elongated in size[/size][/font]
[font=arial, sans-serif][size=3]- Powerup 3 - Paddle can shoot bullets when fire is pressed for x seconds[/size][/font]

- Bullets travel up the screen
[font=arial, sans-serif][size=3]- Bullets are destroyed when they collide with a block[/size][/font]
[font=arial, sans-serif][size=3]- Bullets are destroyed when they hit the top boundary[/size][/font]

[font=arial, sans-serif][size=3]- 3 lives[/size][/font]
[font=arial, sans-serif][size=3]- loose life when ball touches bottom boundary[/size][/font]
[font=arial, sans-serif][size=3]- game over at 0 lives[/size][/font]
[font=arial, sans-serif][size=3]- game win when blocks == 0[/size][/font]

[font=arial, sans-serif][size=1]So yeah, if you could list the components you would use to build those 5 objects, and what systems you would use to implement those behaviours, and how those systems would process your chosen components.[/size][/font]

[font=arial, sans-serif][size=1]This is all about the details![/size][/font]
[font=arial, sans-serif][size=1]Hopefully someone is actually keen to give this a crack lol.[/size][/font]

There are so many different ways this could be done. Im interested in your way

Share this post

Link to post
Share on other sites
I would say there is a difference between a data-driven system and a component-based system. That article describes a component based system.

Are you looking specifically for components? Otherwise this seems to be an appropriate design..

Share this post

Link to post
Share on other sites
[quote name='Telios' timestamp='1328190406' post='4908704']
I would say there is a difference between a data-driven system and a component-based system. That article describes a component based system.

When I say data-driven im actually meaning data oriented, where data is separated into structs (components), and behaviour is separated into systems.

[quote name='Telios' timestamp='1328190406' post='4908704']
Are you looking specifically for components?

Yeah, Im interested in how you break down your components and systems. Do you have a system per component-type? or do systems process multiple components at once? Do your systems process lists of entities, grabbing the needed components off each, or do they just process lists of components?

Heres my example design:

* Position - x, y
* Visual - texture
* Motion - velocity
* Physics - mask, dimensions, shape type
* Input - touch position
* Identity - stores the type of object (ball, paddle, block, powerup)
* Player - stores number of lives
* Powerup1/2/3 - stores powerup type enum, and any state associated with the powerup (maybe a timer)

* RenderSystem - renders all visual components
* CollisionSystem - updates velocities of motioncomponents, does collision detection and response with physics components, raises collision events
* InputSystem - processes drag components, setting x-position to mouse position
* CollisionEventSystem - defines what happens when a collision occurs, responds to collision events from collision system: spawns powerups, engages powerups, deletes blocks
* GameSystem - processes player component, checks when lives == 0, checks when blocks == 0
* PowerupSystem - processes all powerup components

What do you think? Im not sure the best way to handle events between systems. Or how to tell the type of an object, so when a circle collides with a rect, how i know that rect is a block and not a paddle. Thats wat I thought the identity component could be used for.


Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 0