-
Notifications
You must be signed in to change notification settings - Fork 51
Developer Guide
Amadeusz Sadowski edited this page Mar 23, 2014
·
30 revisions
###Quick setup###
Here I assume you're a member (not a member?(dead link)). First:
- Turn off automatic updates.
- Why? It's too automated. Might lead to chaos. More...
- How? BattleScribe Editor (Catalogue or Roster) -> Manage Data -> uncheck "Check for new data files on startup?"
- Open GitHub app.
- Open BSData repo list.
- You have a list on right. There is your profile and all organisations you are member of.
- Choose BSData.
- Clone repos.
- For each repo you want to develop, right-click -> "Clone to..." -> choose "BattleScribe/data" folder.
- You can find it in BattleScribe -> Manage Data on the bottom: ie. "Data location: C:/Users/Amadeus/BattleScribe/data"
- Now we can actually start developing!
###Development cycle###
If you're part of our organisation (not a member?(dead link)), you can directly commit changes. Here's how:
- Open GitHub app.
- Open local repo you'll work on.
- Click the cog symbol, "View on GitHub".
- Browse Issues. Choose which one to work on. If you want to do something not
- Work! :)
- Commit you hard work for community (& yourself).
- If you've finished for today, sync. If not, go back to bullet-point 4.
###Auto-updates###
You can turn on updates for games you don't develop for, because each game has it's own folder. So just subsribe to them. But make sure these repos don't contains files for game system you develop for - that will, again, lead to chaos. Seriously.