JAdventure is a Java (text) based implementation of a Role Playing Game (RPG) - Single Player.
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.
Under Construction This project is in a alpha status. The player can walk through the game, find items and fight with some nice characters!
Everyone is welcome to help with the creation of JAdventure!
The best way to find out more about the game and the ideas that are there, is to have a look at Reddit - JAdventure.
Or drop by at our IRC channel reddit-progether
All documentation is avaiable from the JAdventure wiki and from the JAdventure website. These form the majority of the project's documentation and development guidelines.
- Hawk554
- projectdelphai
- CageHN
- kzisme
- blackwolf12333
- MikesNorth
- pthayer3
- Reinecker
- tamul
- shkesar
- paddatrapper
- Dev-Osmium
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.
-
Create an issue (optional)
-
Fork the codebase
-
Clone your fork
-
Create a branch
git branch <branchName> git checkout <branchName>
-
Make your changes
-
Push to your branch
git push origin <branchName>
-
Make a pull request between your branch and the progether master
- Download the game from here
- Extract the game files
- Go into the game directory and run
java -jar jadventure-XX.jar
(where XX is the version)
- Install Maven
- Go into the game directory and run
$ mvn test $ mvn exec:java
to play the game.
Maven has other useful targets such as mvn compile
to compile and
mvn install
to install a copy of JAdventure and all its dependencies to the
local Maven repo on your machine.
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 view details about your player:
v <s,e,b> - view status, equipped items, backpack
To quit the game:
exit
To move:
g n - go north
g s - go south
g e - go east
g w - go west
To pick up an item:
p <itemName>
To drop an item:
d <itemName>
To equip/unequip item:
e <itemName>
ue <itemName>
To attack:
a <monster>
To look around:
la
To talk to a Non-player Character:
t <npc>
To help make code more readable, understandable, and consistent, each contributor should follow the set guidelines laid 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).
- Spaces not tabs
- Space width is 4
- No beginning/trailing empty lines
- Each file should start with an import statement if necessary single-spaced
- After class declaration and between class methods, there should be a space.
- Within methods, there should be no spaces unless to separate specific chunks of code (i.e not for if statements, return values, or loops)
- Opening curly braces appear a space after the closing parentheses, not directly after.
- Closing curly braces appear on own line unless followed by an else etc. which will be a space after the curly brace.
- Comments should have one space after "//"
- Comments 4 lines or greater in length should be multi-line commented