Glossary

This article lists agreed upon terms for the specific development departments to ease communication.

Common terms for all departments

 * Asset pipeline:
 * Baked assets:
 * Current tasks:
 * Department:
 * How to contribute:
 * Idea dump:
 * RAW assets:
 * Workflow: A Workflow describes the translation process from mere ideas to the implementation of agreed upon (game) concepts.

Graphics

 * Concept art: Inspirational artwork, may work as a input for some 3D modellers.
 * Rendering setup: Overall "conditions" (tile size, camera setting, lights) to make real in-game asset from 3D models. It is held in single file suited to use in 3D software.

Mechanics

 * Game Mechanic: Game Mechanics are plain text descriptions of how the game works, how does it model "reality". They are not necessarily parpg or Post-Apocalypse specific, and generally do not depend on programming implementation.
 * Game mechanic model: Game mechanic models are individual "items" or models of concepts/objects/thing for the game. A template for each type of "thing" is defined in   Game Mechanics, and each thing is some set of parameters that describe it.
 * UI mechanics:  "User Interface" mechanics";  This is how the User Interface to the game should function for various views and actions done by the player.  Usually a step below actual Programming specifications
 * Story mechanics: Story mechanics are rules and concepts that apply to the specific nature of the PARPG game, and it's story. So while there may be general "survival" or "character origin" rules in  Game Mechanics the specifics of how it is to be dealt with in PARPG is here.

Mechanics Concepts and FAQ
If questions or clarifications are "asked" here, they will be answered.
 * Subdual damage: Non-lethal damage

Programming

 * Code design workflow:
 * Code proposal:
 * Code style: The way in which code is written and formatted, most notably in the use of whitespace. Most programming languages have a flexible syntax and grammar, allowing the same functional piece of code to be written in multiple (more or less valid) ways. Code style standards exist to keep code consistent across one or more projects and minimize the effort required by programmers to read the code.
 * Commit comments guidelines:
 * Development environment: Set of tools and programs available on your computer used to write, analyze and debug code.
 * Grammar: The set of rules that govern how a programming language is written, including syntax.
 * Integrated development environment (or IDE): A single program or suite of programs designed to work with each other that forms a "complete" programming development environment. Examples include Eclipse, WingIDE, CodeBlocks, Emacs, etc.
 * Library: A collection of variables, functions and classes that serve a collective purpose, usually stored as a compiled file with a .so or .a extension on Unix systems and .dll on Windows systems. A shared library (also known as a dynamic link library on Windows) is a library that can be accessed by a program at runtime, while a static library must be explicitly linked into a program.
 * Runtime environment (or environment): Usually used to refer to the type of operating system installed on your computer and the number, type and versions of shared libraries required by a particular program to run. May also refer to your computer's hardware, in particular your CPU's processing speed, number of cores, machine architecture (64-bit versus 32-bit), type of GPU and amount of dedicated graphics memory, and the amount and type of system RAM.
 * Syntax: The set of rules governing how the symbols and statements defined by a particular programming language may be used together to create programs.

Project management

 * Infrastructure: Infrastructure is an umbrella term for all the (project management) tools that are needed to effectively run the project. This also includes the necessary hardware to run these tools. Infrastructure includes version control, task & bug tracking, documentation as well as various communication channels the developers utilize, such as the blog, the forums and IRC.
 * Mission statement: The Mission statement is a brief statement of what we would like to achieve with the PARPG project.
 * Public relations: Public relations are all tasks of the project management staff related to communicating with the public. That includes: updating the development blog, community interaction at external forums, wording release announcement.
 * Subversion: Subversion is a revision control software utilized by the PARPG team. It is commonly used in all kind of software development projects.
 * Trac: Trac is a project management software we're using. It's similar to a bug tracker but offers additional features such as a Subversion repository browser, visualized DIFFs and a milestone planning tool.

Writing

 * Setting
 * Theme
 * Storyline
 * Location:
 * Quest
 * NPC:
 * Faction: