https://github.com/zipcodecore/ohero
Java Fundamentals Review Text adventure Cave Game
https://github.com/zipcodecore/ohero
game
Last synced: 9 months ago
JSON representation
Java Fundamentals Review Text adventure Cave Game
- Host: GitHub
- URL: https://github.com/zipcodecore/ohero
- Owner: ZipCodeCore
- Created: 2020-03-11T15:34:59.000Z (almost 6 years ago)
- Default Branch: master
- Last Pushed: 2020-03-17T15:03:22.000Z (almost 6 years ago)
- Last Synced: 2025-04-15T21:15:49.302Z (9 months ago)
- Topics: game
- Language: Java
- Homepage:
- Size: 16.6 KB
- Stars: 1
- Watchers: 2
- Forks: 17
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# OHero
"Be your own hero."
* Objective:
* Create a text adventure game using Java fundamentals.
## Minimum Viable Product (MVP)
* This game must have certain features to be viable:
* Interaction of multiple models.characters (The Player, NPCs of some kind)
* Player choices must somehow affect stats of The Player
* Stats must be applied within interactions
* A functional inventory
* Persistence
## Specs
* The project should include some concept of
* `Display` class
* Text to be read by The Player (including menus) should be handled in an Object Oriented, single responsibility way. IE, make a class to handle display, reduce duplicated code as much as possible.
* `Character` Abstraction
* There will be many kinds of models.characters. The Player will have a Hero, there will be NPCs, bosses, other entities within the game. How will you handle that while duplicating the least amount of code?
* `The Game Loop`
* This game must continue running until either:
A: The player intentionally exits or,
B: The game comes to an end.
* `Inventory and Collections`
* How will you have the application track different models.characters, The Player's character inventory, and a reflection upon stats?
* `Random Encounters`
* Utilizing Dice and other known tools, create a means of randomizing encounters, initial stats rolls for models.characters, or otherwise.
* `Testing`
* Is not optional. Any portion of your code base which can be tested, should be tested using TDD.
## Developmental Notes
* OHero (Be your own Hero!) is an adventure game. The adventure is making the game. As such, player input is required early and often and **EVERY DECISION** should impact the state of The Player's character. Those state changes (IE, Stats) should reflect future interactions.
* You are to utilize tools and techniques you have learned throughout the course to plan and solve the problems involved with creating a functional game with a manageable code base.
* Manage your abstractions. Think through and understand where methods should be - does The Player move to the next room, or does the current active character being used by that player move to the next room? Does it matter?
* You must have a completed and approved UML diagram before you proceed to do any development
* All public methods should be tested.