Description

A text-based game written in Java. It was originally created as a project of the progether subreddit and worked on by Applzor, add7, geniuus, Malfunction, bdong_, Qasaur, and tamul. It was revived by Hawk554.

Contributors

1. Hawk554
2. projectdelphai
3. CageHN
4. kzisme
5. blackwolf12333
6. MikesNorth
7. pthayer3
8. Reinecker
9. tamul
10. shkesar

Contributing

Don't make a pull request to the main repo's master if you don't want your commit merged yet. Don't make pull requests if you're not willing to merge that code.

Rather than opening a pull request, consider opening an issue to discuss the problem you're fixing. Keep the work-in-progress updates to your fork, maybe merging the updates to a separate branch in the main repo if there's enough there to warrant it.

1. Create an issue (optional)

2. Fork the codebase

3. Clone your fork

4. Create a branch

   git branch git checkout

5. Make your changes

6. Push to your branch

   git push origin

7. Make a pull request between your branch and the progether master

Setting Up The Game For Development or Gameplay

You can download the game with:

git clone https://github.com/hawk554/JAdventure

###Run with Ant###

Install apache-ant

Run the game with:

ant -emacs run

It will automatically compile, test, and run the game.

Playing the Game

To start a new game:

start

To save a game:

s

Get a list of commands with:

h

To get a list of monsters around you:

m

To get your own current status/stats:

st

To quit the game:

exit

To move:

gn - go north gs - go south ge - go east gw - go west

To pick up an item:

p

To drop an item:

d

To equip/dequip item:

e de

Coding Standard/Convention/Style

To help make code more readable, understandable, and consistent, each contributor should follow the set guidelines lain out below. If you disagree with something or come across a style that has not been decided upon, make an issue or a pull request respectively for discussion on the best style. The standard will be decided based on either majority rule or official documentation (i.e. oracle coding standard).

1. Spaces not tabs
2. Space width is 4
3. No beginning/trailing empty lines
4. Each file should start with an import statement if necessary single-spaced
5. After class declaration and between class methods, there should be a space.
6. Within methods, there should be no spaces unless to separate specific chuncks of code (i.e not for if statements, return values, or loops)
7. Opening curly braces appear a space after the closing parentheses, not directly after.
8. Closing curly braces appear on own line unless followed by an else etc. which will be a space after the curly brace.
9. Comments should have one space after "//"
10. Comments 4 or greater in length should be multi-line commented