- 4 Player (Reccomended) Internet Multiplayer, teams of two.
- 4 'Classes', one per team.
- Knight:
-
Short range, melee. Breaks weapons/spells.
- Archer:
- Mage:
- Enchanter:
- Possible Environments
- Ruins: Rundown stone structures covered in jungle, heavy vertical elements.
- Jungle: Trees, limited line of sight, limited vertical elements.
- Farmland: Good line of site, no vertical elements.
- Requirements
- Must be 3d.
- Must use internet multiplayer.
- Must use non-proprietary software and run on Linux. Possibility: Glutmaster
- Must be fun.
- Design Pros
- Only four character models to develop.
- 'Class' balance could offer unique gameplay compared to other shooters.
- 2 'classes' will require only a small amount of weapon art.
- Can focus on class skills, further reducing the need for weapons models.
- Relatively unique gameplay should counter the need for ai controlled players.
- Design Cons
- Weapons are not completely generic.
- 'Class' balance could be hard to implement.
- Spell effects may be hard to make graphically interesting.
- Fantasy theme may be unappealing.
-
Long range, limited melee. Arrow effects (freeze, poison,fire),
has rope useable by team (vertical movement).
-
Long range, little melee (dagger). Freeze, burn, direct
damage.
-
Condition breaker, regeneration and poison, little melee (dagger).
Has conveyance for team (horizontal movement), enchants weapons.
- Time
- Tentative Schedule
- Early February: Design, concept/art, organization of talent.
- Late February: Design, begin laying framework for game (basic level and models).
- Early March: Models/levels, begin programming movement/combat.
- Late March: Refine models/levels, continue movement/combat.
- Early April: Refine movement/combat, refine graphical elements.
- Late April: Testing, last minute polish, balancing.
- Tools
- Need to find Linux computers with 3d acceleration. My computer can have Linux installed, but with an ATI card 3d drivers will be a pain.
- Many tools available on the internet, such as the class library already mentioned.
- Items of Note
- Sticking to deadlines and keeping the project simple will be important.
- Everyone must pull their weight.
- Remember, the product should be fun!
-
Our primary resource is time. We have roughly 3 months to get a working game
developed. Proper budgeting, management, and organization will be vital.
- Main Menu
- Use Case: New Game
- Actor Actions
-
1. Choose "New Game" menu item.
- System Responses
-
1. Display "New Game" menu.
- Actor Actions
- Use Case: Join Game
- Actor Actions
-
1. Choose "Join Game" menu item.
- System Responses
-
1. Find existing game.
2. Place player in game room.
3. Else, report error.
- Actor Actions
- Use Case: Settings
- Actor Actions
-
1. Choose "Settings" menu item.
- System Responses
-
1. Open "Settings" menu.
- Actor Actions
- Use Case: Quit
- Actor Actions
-
1. Choose "Quit" menu item.
- System Responses
-
1. Exit program.
- Actor Actions
Note: This is from the view of the initial actor. The other actors see the same options.
- Use Case: New Game
- New Game Menu
- System Actions: Fr Settings --> Player Name
-
Display Player name, otherwise display default.
- Use Case: Start Game
-
Related use case: Choose Level
- Actor Actions
-
1. Choose "Start Game" menu item.
- System Responses
-
1. Launch game, loading selected level from Choose Level.
- Actor Actions
- Use Case: Boot Player
- Actor Actions
-
1. Choose player to boot.
2. Choose "Boot Player" menu item. - System Responses
-
1. Remove selected player from game room.
- Actor Actions
- Use Case: Choose Level
-
Related use case: Start Game
- Actor Actions
-
1. Choose desired level.
- System Responses
-
1. Set level selected on all screens.
- Actor Actions
- Use Case: Chat
- Actor Actions
-
1. Select chat bar.
2. Type desired text.
3. Hit 'enter'. - System Responses
-
1. Send text to all chat bars.
- Actor Actions
- Use Case: Back
- Actor Actions
-
1. Choose "Back" menu item.
- System Responses
-
1. Load Main Menu.
- Actor Actions
Note: Once again, this only describes interactions from the perspective of the initial actor.
- System Actions: Fr Settings --> Player Name
- Settings Menu
- Use Case: LAN/Internet
- Actor Actions
-
1. Click "LAN/Internet" menu item.
- System Responses
-
1. Toggle LAN/Internet mode.
- Actor Actions
- Use Case: Controls
- Actor Actions
-
1. Select "Controls" menu item.
2. Choose desired changes. - System Responses
-
1. Load Control Selection Menu.
2. Change controls to desired scheme.
- Actor Actions
- Use Case: Player Name
-
Related Use Case: New Game
- Actor Actions
-
1. Choose "Player Name" menu item.
2. Type desired name in box.
- System Responses
-
1. Show Name box.
2. Save player's name, show in New Game room.
- Actor Actions
- Use Case: LAN/Internet
- Ingame
- Use Case: Move
- Actor Actions
-
1. Control toon to travel around level.
2. Acquire Items/Weapons. - System Responses
-
1. Display level/players accordingly.
2. Track inventory/equipment.
- Actor Actions
- Use Case: Combat
- Actor Actions
-
1. Use controls to fire/cast effects/cast spells/swing weapon.
2. Equip weapon/item.
3. Reload. - System Responses
-
1. Display appropriate effects graphics.
2. Display other players' movements.
3. Display level.
4. Calculate damage and display accordingly.
5. Track statistics.
6. Relocate players on death with default settings (respawn methods still to be considered).
- Actor Actions
- Use Case: Exit
- Actor Actions
-
1. Hit 'esc' key.
- System Responses
-
1. Remove player from game.
2. Load Main Menu.
- Actor Actions
- Use Case: Move
- Overview
- Game
Knight finds a two-handed broadsword. Enchanter destroys three orbs he found to enchant Knight's weapon with spell break. Archer/Mage find them, Mage opens the attack with a fire column (two fireball scrolls combined). Knight quickly puts his weapon in spell break. It absorbs the spell, charging for a second then bursts back along the spell path in a polygonal gray pattern destroying one of Mage's scrolls. Mage is left with regular fireball. Archer fires an ice shot at Knight, freezing him for a bit. Mage directs her damage to Enchanter, setting him on fire. Enchanter breaks the ice on Knight and casts regeneration on himself. Archer follows up on Enchanter with a poison shot while Knight goes berserk and then charges Mage, frightening her (stun). Enchanter casts slow on the Archer.