HTTPS clone URL
Subversion checkout URL
- [Draft] Entity System Architecture
- Alternative Setups
- Applet architecture
- Asset System
- Behavior Tree System
- Block architecture
- Block definitions (JSON)
- Block Shapes In Blender
- Chunk Lifecycle
- Codebase Structure
- Coding Conventions
- Collada Models
- Community Suggestions
- Component Lifecycle
- Console Commands
- Console Help
- Contributor Guide
- Crafting System
- Crafting system (developer)
- Dev Setup
- Dev team
- Download Terasology
- Entity Lifecycle
- Entity System Architecture
- Entity system concepts
- Events and Systems
- Fancy Git
- Grammar System
- Input Bindings
- Issue tracking
- Key Bindings
- Major Concepts
- Markdown and Wiki
- Migrating pages to the GitHub Wiki
- Modding and Modules
- Modding API
- Modding Guide
- Pag Grammar Definition
- Player Guide
- Prefab files
- Procedural Architecture Grammar
- Project Overview
- Randomness and Noise
- Shape Architecture
- Systems and Components in Practice
- Terasology? Why not just use Minecraft, whats the beef?
- Text and Font
- The Wiki and You
- Tutorial: How to create new items
- Tutorial: How to make blocks with custom UI
- Unit Testing
- Using Blender Assets as Miniion Models
- Using IRC
- Versioning Guideline
- Weblate Setup
- What is Terasology
- World Biomes
- World Terrain Generation
Clone this wiki locally
This is the Terasology wiki, used for game documentation and other resources like how to get started as a contributor.
What is Terasology ? Founded by Benjamin 'begla' Glatzel as an open source tech demo to research procedural terrain generation a team is now taking it to the next level - a full fledged game. We're aiming for a survival and discovery game with a strong influence from Minecraft, Dwarf Fortress, and Dungeon Keeper. A key part of the game will be building up an estate of some sort and managing specialized minions to climb up the ladder of discovery, while surviving in a world that might just be full of things that want to kill you.
- About Terasology - more details on exactly what our goals are
- Download Terasology - basic instructions for how to download and set up the game. Also contains version history and other useful links
- Dev Team - the who's who of Terasology and what holes we might especially need more people to help with
These pages explain how the game's unstable / develop version works, in detail. The stable / master version may differ as it isn't updated as frequently. See the GitHub README for a current summary of that release.
- Key Bindings - how to control yourself inside the game
- Tool Functions - what the tools do
Console Help - commands available in the console opened with
Debug Features - special features only active with debug mode enabled using
Interested in getting involved with working on the game? This section is for you!
- Contributor Guide - notes for general contributions to Terasology including links to help you learn the related technologies
- Modding Guide - details on how to create mods for the game (quick guide making some assumptions of development familiarity)
- Project Overview - a summary of the different GitHub projects involved and what libraries we use
- GSOC - we keep a set of proposals ready for Google Summer of Code participation if we get accepted
- Codebase Structure - reviews how the codebase is put together
- Dev Setup - a more detailed set up guide for developing Terasology on your local machine
- Fancy Git - more advanced Git topics that you don't need to be able to run from source, but may need to submit source or maintain your source setup over time
- Checkstyle - notes about our code conventions and how to automatically check them
- Unit Testing - or the lack thereof, the most common developer sin!
- JavaDoc - well-written code explains itself, but it doesn't help to have that in an exportable format!
- Modding API - Information on the engine and how what features are available for modding
- Console commands - instructions to create new console commands
- Rendering - what you need to know to set up your own rendering code
- Contributor Guide covers most art related contribution tasks.
- Texture Origin - an index for textures we use and who contributed them. That way we can give credit where due and keep track of how many of our core textures are unique vs sourced from texture packs
- Markdown and Wiki - how to tweak away with Markdown and the GitHub wiki
- Issue Tracking - how and what we're tracking using the GitHub issue system
- Community Suggestions - a place for us to store suggestions made by the public in a place that's not good for potential long-term storage (tickets, forum, etc)
These pages offer more advanced insight into how specific features of the game are architected and why.
- Applet Architecture - structure of the applet version of the game and related info.
- Block Architecture - development overview of our Block system. (pending changes needed to make the game work in an applet again)
- Shape Architecture - defining 3D meshes via definitions in JSON!
- Block Shapes In Blender - more on shapes.
- Entity System Architecture - describes the structure and usage of the entity system.
- Events and Systems - describes how new game logic can be hooked in
- Pathfinder Algorithm - some notes about pathfinding.
Behavior Tree System - how to use and extend the behavior tree (editor).
A list of modules maintained at Terasology can be found here: http://jenkins.movingblocks.net/view/Modules/ http://jenkins.movingblocks.net/view/ModulesPending/
- Crafting System - Introduction to the crafting system, its usage and extenstion.
- Procedural Architecture Grammar - Introduction to the PAG for procedural building generation.
- Miniions - Introduction to the miniion system.
We have several ways to get the word out on updates, and likewise there are several ways to contact us.
- Forum - new development / game topics will be posted here, and any questions answered.
- GitHub - "Watch" the official project here to be able to easily spot commits and changes.
- Twitter - we'll tweet regularly about significant commits or new discussion topics posted, so "Follow" us for updates.
- Facebook - if you prefer to keep updated via Facebook you can "Like" us on there to keep up.
- Google+ - help prove people actually use G+ ! ;-)
- Blog - Major news like milestones reached, new videos posted, etc will get posted to our blog.
- IRC #terasology - We're setting this up for live chat but it may take a while to stabilize with people only rarely on (or AFK), See Using IRC for setup details.
- Jenkins RSS - If you really want to know when something has just been built ;-)
Found a problem on this page? Submit a new issue about it here