1 / 10

Talisman

Talisman. Sam Odeh, Pierre Gelter, Jesper Lundkvist. Introduction. Our project: Talisman. A adventure board game Developers. Basic Idea. Why Talisman? Rules Movement Strength/Craft Fight Experience Victory. The desired design. Demo. Development tools.

barth
Download Presentation

Talisman

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. Talisman Sam Odeh, Pierre Gelter, Jesper Lundkvist

  2. Introduction Our project: Talisman • A adventure board game • Developers

  3. Basic Idea • Why Talisman? • Rules • Movement • Strength/Craft • Fight • Experience • Victory

  4. The desired design

  5. Demo

  6. Developmenttools • Main tool: Eclipse with subversion • Tried netbeans for the GUI • Separate project in netbeans • Horrible results switched to my eclipse visual swing editor • Eclipse plugin, identical to netbeans editor • STAN to analyze • Find bug • Photoshop

  7. Basic Design • MVC • Seperate client & server, and a common package • Seperate classes for adventurecards and maptiles • We have extracted some cod into new classes to avoid getting big classes • RMI, communication through network

  8. Strong and weak parts • Nice GUI • Adventure cards and Map Tiles have seperate logic in each class, easy to implement new • Client and Server independent of each other, shares Common package • ”Motorway” method calls • Most game logic is hard coded • The card packages contains references to the game logic, not independent

  9. Lessonslearned • Main lesson: Start in time! • Plan the stucture and interfaces very early • Build a running shell of the program ASAP • Use the right tools • Define packages in the beginning

  10. Futuredirection • Implement special ability • More different tile events • Additional cards • Spells • Additional graphics • Support for online-play • sound effects

More Related