Skip to content
This repository has been archived by the owner on Feb 9, 2023. It is now read-only.

Getting involved

gegerlan edited this page Dec 20, 2011 · 1 revision

There are a number of supportive tasks you can fulfill, if you're interested in supporting the project. It's important to note that the project itself is larger that its application, what you see when playing the game is just the final product of a large process with multiple contributors doing a vast array of different things.

If you're interested, you're welcome to contact the project management, or making your presence known in the http://www.hongfire.com/forum/showthread.php/156872-quot-Adventures-of-Garnet-quot-RPG-XP-game-over-rape.

If you're interested in supporting the process there are a number of areas you can support the project with.

  • Testing and feedback
  • Ideas and new features
  • Bug fixing
  • Copy editing
  • Graphics and images
  • Audio and sound
  • Writing
  • Map improvements or creations
  • Quest creation
  • Scripting

The subject areas aren't distinct, and as such may and will overlap.

Testing and feedback

After spending some time with the game, consider providing some feedback on how your experience was. Was there anything that you think could have been done better, or something that didn't work at all?

Ideas and new features

If you have any ideas of features that would improve the game, consider dropping a line. Before you do so though, make sure you answer the following points:

  1. Does the feature fit with the current game's style and world?
  2. Does it contribute towards making the game a better experience for people, and why?
  3. Is the idea detailed enough for a complete implementation, from start to finish?

If you feel like you've answered the above questions, create a new issue on Github detailing your idea.

Bug fixing

For those willing to help solve issues they themselves, or others, have experienced are welcome to work towards solving it.

To be able to work with the game, it's recommended (required) to have a copy of the RPG Maker XP editor.

Read the developer documentation for how to setup a developer environment and submitting changes.

Changes can be submitted as patches or as pull requests.

Copy editing

Fixing the current text in any form. This means correcting spelling and grammar, and to some limited extent; the visual presentation of the text.

In most cases, the errors only needs to be made aware, and a developer will solve it when possible. Do this by submitting a bug report or contacting them directly.

If you wish to make the fixes yourself, consider reading the Bug fixing section of this page.

If you wish to go through all text in the game, the recommended way is to use a text extractor like DreaMaker to work with the content.

Graphics and images

Graphics can be tiles (i.e. the graphics for the map: floor, walls, decorations etcetera), sprites (characters), persona images (large character images, and outfits), large images (e.g. game over scenes), and animations.

We are looking for original art, or art made appropriate with the appropriate visual style of the game.

Audio and sound

Creating or finding audio, such as sound effects and music.

Writing

Improving the current writing in the game, exploring new venues (working on the context and surrounding world) or writing quests and dialog that can be implemented in the game.

Map improvements or creations

Maps can either be create as empty husks for future quests, or with the specific purpose of housing one or more quests. You should be aware that due to technical limitations, it's important that you try to make any changes available, as soon you're ready.

Improvements of maps can be purely decorative, or complete re-imaginations

Quest creation

Quests usually entails a number of tasks previously mentioned. You need an idea, somewhere to play it out (map), and assets to tell your story (writing, graphics and audio). You are welcome, and encouraged, to use whatever assets that's already available, but avoid building the quests around the assets, whenever possible.

Scripting

Extending the engine that is built using the scripting language Ruby.

Clone this wiki locally