Hello Archmages! Welcome to the developer wiki for CodeCombat. These documents are designed to give you everything you need to know, technical and non-technical, to dive into the project. If you see an opportunity to improve the docs, go ahead!
###Index:
####Contact Us
There are a variety of ways to get hack on CodeCombat related things. We have a developer chat room on Slack. Most people are in US Pacific Time (~GMT-8) but there are usually a few other players awake at other times.
The Discourse Forum is another useful place to get help. For more information check out the main chat page.
####Starting Off
- Set up the Developer Environment.
- Make a small first commit such as creating a new Thang name, adding tips to the loading screen or adding documentation.
- Check out the Cookbook for answering all your CodeCombat-specific coding questions.
- Check out the Good for Newbies Issues.
- Browse the wiki to learn something new!
- Fix bugs.
- Bring up new ideas in our Slack channel.
- Hack to the max!
####Reading Material ######General:
- Mission Statement
- Developer Environment - Start here to get CodeCombat set up on your computer.
- Developer Organization
- Cookbook
- Coding Guidelines
- Technical Overview
- Third Party Software and Services
- JSON-Schema
- Coco Models
- Testing
- Git Policies
######Frontend Development:
######Backend Development:
######Key Systems:
######Game Engine:
- CodeCombat uses a Thang Component System architecture.
- A Thang can be an ogre, a land, an arrow--anything.
- Thangs are just clusters of Components.
- Systems organize the Components.
- Worlds simulate deterministically.
- The Surface is what we call our graphics layer.
- The Tome is our spell editor.
- Multiplayer.
######Side Projects:
####FAQ ######How do I learn Git?
Doing this quick course should get you up to speed with Git.
######What are some larger projects I can do? Here's our big project ideas list, which should give you some ideas about what you can contribute on.