1 / 14

Fall of E.V.I.L.

This document presents the key members of the development team behind "Fall of E.V.I.L.", detailing their backgrounds and contributions. The team, consisting of four senior Computer Science majors and one junior, leverages their unique skills in areas like state management, particle systems, and artistic creation. The game embodies fast-paced action reminiscent of classics like Metal Slug and Mario. While the project met its deadlines and maintained a dynamic team environment, challenges such as messy coding and focus shifts were encountered, leading to valuable learning experiences in programming and game design.

ady
Download Presentation

Fall of E.V.I.L.

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Fall of E.V.I.L. Revision 119 [Brett Hlavinka, Justin Kern] [Drew Reagan, John ‘Skinner’ Laky]

  2. Introducing the Team [Brett] • Senior Computer Science major • Most experience with XNA • Most experience in (large) group projects • Naturally cynical • Elected group leader

  3. Team Contributions [Brett] • State Management • HUD • Animations • Bosses • Screen Translation • Input

  4. Introducing the Team [Drew] • Senior Computer Science major • No previous experience in XNA or C# • Some experience in team-based development • Interested in particle systems and general eye-candy

  5. Team Contributions [Drew] • Particle System • Do not underestimate this • Collision Detection • Player Hierarchy

  6. Introducing the Team [Justin] • Senior Computer Science major • Most artistic ability in the group • Already had software and hardware appropriate for generating artwork • Some experience in team-based development

  7. Team Contributions [Justin]

  8. Introducing the Team [John] • Junior Computer Science & Math major • Interested in algorithms • Author on the side

  9. Team Contributions [John] • Level Generation • Props • Enemies • Backgrounds / Parallax

  10. “explain the game idea” Metal Slug Mario Viewtiful Joe Dishwasher Dead Samurai

  11. “game play” Fast-paced, extreme, action-packed [And other synonyms for intensity] Explosions, Blood, Smoke, Fire [i.e., Particles] Simple Progression [Stages, Levels]

  12. “what went right” • On time, on schedule • Set ambitions ‘just right’ • Team dynamism • Accountabilibuddies • User Study

  13. “what went right/wrong” • Messy code near the end • Focused on content • Focus lost on replayable levels • Shifted to fun gameplay • Poor top-level data management • Level overhead, garbage collection

  14. “what they have learned (if anything)” • Programming paradigms • Balancing parameters with OO • Some good XNA techniques • Level encapsulation / dependencies • Lambda expressions

More Related