Development: Difference between revisions
m (fixed link) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
After the [[History#Disappointment_of_the_Highest_Hopes.3B_Fulfillment_of_the_Greatest_Ones|source code release by Microsoft]] the community founded the FAZ project - Free Allegiance Zone. FAZ now stands at Release 4 (R4). | After the [[History#Disappointment_of_the_Highest_Hopes.3B_Fulfillment_of_the_Greatest_Ones|source code release by Microsoft]] the community founded the [[FAZ|FAZ project]] - Free Allegiance Zone. FAZ now stands at [[FAZ R4|Release 4 (R4)]]. | ||
The core of Allegiance, including the game client, server and lobby code are being developed by the FAZ Development | The core of Allegiance, including the game client, server and lobby code are being developed by the [[Development Team|FAZ Development Team]] in an open source project. Anybody is free to download, examine and offer patches. To be included in the official builds the patches have to be submitted to the Development Team. | ||
The [[ASGS]] system is closed source for security and licensing reasons. However, some trusted members of the community have access to the full ASGS source. | The [[ASGS]] system is closed source for security and licensing reasons. However, some trusted members of the community have access to the full ASGS source. | ||
==Development process== | ==Development process== | ||
The current development process is led by [[Individuals#Dogbones|Dogbones]]. For each release a set of goals are created. All members of the development team are free to submit patches to a SVN repository for review and inclusion in beta builds until a feature freeze is made (usually when the development team feels enough improvements have been made). Patches that have a clear effect on game play are taken to the community for voting. | The current development process is led by [[Individuals#Dogbones|Dogbones]]. For each release a set of goals are created. All members of the development team are free to submit patches to a SVN repository for review and inclusion in beta builds until a feature freeze is made (usually when the development team feels enough improvements have been made). Patches that have a clear effect on game play are taken to the community for voting. | ||
Beta builds are run on a special development lobby to weed out bugs. Towards the end of each development cycle weekly beta games are held to find the final bugs. | [[FAZ Beta|Beta builds]] are run on a special development lobby to weed out bugs. Towards the end of each development cycle public weekly beta games are held to stress test the new releases and find the final bugs. | ||
It is important to notice that only approved builds will be accepted by [[ASGS]]. Therefore you can not build your own client and play on the normal servers. | |||
==About== | ==About== | ||
| Line 19: | Line 21: | ||
==Releases== | ==Releases== | ||
*'''Placeholder''' for someone writing up a nice, easily read, development history | *'''Placeholder''' for someone writing up a nice, easily read, development history | ||
===Time Line=== | |||
*'''Placeholder''' for a timeline chart thingy | *'''Placeholder''' for a timeline chart thingy | ||
===Code changelogs=== | |||
Note that these are different from Game Balance changelogs, you need to look up the appropriate [[Cores|Core]] to view those. | |||
*[[MS]] - 2000 | |||
*[[FAZ R1]] - March 1, 2006 | |||
*[[FAZ R2]] - August 1, 2006 | |||
*[[FAZ R3]] - December 14, 2006 | |||
*[[FAZ R4]] - November 1, 2007 | |||
| Line 34: | Line 40: | ||
*[[Creating Models for Allegiance]] | *[[Creating Models for Allegiance]] | ||
*[[Downloading and Building the Source]] | *[[Downloading and Building the Source]] | ||
*[[Making Custom Maps]] | *[[Making Custom Maps]] | ||
* | *Add stuff here | ||
===Mods=== | |||
There have been many changes and improvements that haven't made it to the default program for various reasons. | |||
*[[Chat Packs]] | |||
*[[User Interface Mods]] | |||
*[[Targeting Reticles]] | |||
*[[Hi-res textures]] | |||
==Historical Development== | |||
*[http://www.allegacademy.org/devs/peterarisman.shtml Historical Interview with Allegiance's original Art Lead] | |||
*Original Developer Journal - Written in early 2000 | |||
**[http://au.pc.ign.com/articles/075/075281p1.html Chapter One] - Game Development Virgins | |||
**[http://au.pc.ign.com/articles/075/075594p1.html Chapter Two] - Environment + Rules + Toys = Gameplay | |||
**[http://au.pc.ign.com/articles/075/075916p1.html Chapter Three] - Game Balance as an Art Form | |||
**[http://au.pc.ign.com/articles/076/076279p1.html Chapter Four] - Game Development 101 | |||
**[http://au.pc.ign.com/articles/076/076603p1.html Chapter Five] - So you want to create a game? | |||
**[http://au.pc.ign.com/articles/077/077237p1.html Chapter Six] - In the Beginning | |||
**[http://au.pc.ign.com/articles/077/077584p1.html Chapter Seven] - A Day in the Life | |||
**[http://au.pc.ign.com/articles/077/077922p1.html Chapter Eight] - Hints and strategies | |||
{{Stub}} | {{Stub}} | ||
{{FAZdev}} | {{FAZdev}} | ||
Revision as of 23:36, 12 March 2008
After the source code release by Microsoft the community founded the FAZ project - Free Allegiance Zone. FAZ now stands at Release 4 (R4).
The core of Allegiance, including the game client, server and lobby code are being developed by the FAZ Development Team in an open source project. Anybody is free to download, examine and offer patches. To be included in the official builds the patches have to be submitted to the Development Team.
The ASGS system is closed source for security and licensing reasons. However, some trusted members of the community have access to the full ASGS source.
Development process
The current development process is led by Dogbones. For each release a set of goals are created. All members of the development team are free to submit patches to a SVN repository for review and inclusion in beta builds until a feature freeze is made (usually when the development team feels enough improvements have been made). Patches that have a clear effect on game play are taken to the community for voting.
Beta builds are run on a special development lobby to weed out bugs. Towards the end of each development cycle public weekly beta games are held to stress test the new releases and find the final bugs.
It is important to notice that only approved builds will be accepted by ASGS. Therefore you can not build your own client and play on the normal servers.
About
Releases
- Placeholder for someone writing up a nice, easily read, development history
Time Line
- Placeholder for a timeline chart thingy
Code changelogs
Note that these are different from Game Balance changelogs, you need to look up the appropriate Core to view those.
- MS - 2000
- FAZ R1 - March 1, 2006
- FAZ R2 - August 1, 2006
- FAZ R3 - December 14, 2006
- FAZ R4 - November 1, 2007
Current Development
- FAZ Beta
- Creating Models for Allegiance
- Downloading and Building the Source
- Making Custom Maps
- Add stuff here
Mods
There have been many changes and improvements that haven't made it to the default program for various reasons.
Historical Development
- Historical Interview with Allegiance's original Art Lead
- Original Developer Journal - Written in early 2000
- Chapter One - Game Development Virgins
- Chapter Two - Environment + Rules + Toys = Gameplay
- Chapter Three - Game Balance as an Art Form
- Chapter Four - Game Development 101
- Chapter Five - So you want to create a game?
- Chapter Six - In the Beginning
- Chapter Seven - A Day in the Life
- Chapter Eight - Hints and strategies
Stub This article is incomplete This is an article about a topic that should be covered in more detail by the FreeAllegiance Wiki, but is lacking in content.
You can help by improving it!
| FAZ Development |
| ||||||||
|---|---|---|---|---|---|---|---|---|---|
