Btcc22

https://www.youtube.com/watch?v=gWJvptXsv4w

https://www.youtube.com/watch?v=gWJvptXsv4w

https://www.youtube.com/watch?v=gWJvptXsv4w

From a balance point of view, I don't agree with having it overheat to begin with. However, it looked cool when it was mirrored.

From a balance point of view, I don't agree with having it overheat to begin with. However, it looked cool when it was mirrored.

From a balance point of view, I don't agree with having it overheat to begin with. However, it looked cool when it was mirrored.

Medals!
...and chat if you haven't already seen it in the last week or so
 
 


 
Post with more info, here.

Medals!
...and chat if you haven't already seen it in the last week or so
 
 


 
Post with more info, here.

Already in the works.

Medals!
...and chat if you haven't already seen it in the last week or so
 
 


 
Post with more info, here.

Already in the works.

Medals!
...and chat if you haven't already seen it in the last week or so
 
 


 
Post with more info, here.

Medals!
...and chat if you haven't already seen it in the last week or so
 
 


 
Post with more info, here.

While I applaud your initiative, I do have to question whether you've bitten off more than you can chew. To produce an AAA quality Halo fan game with both single and multiplayer by late 2015 and get it on the Xbox One, with a tiny, inexperienced team that have never produced a game before is just, well, it's not going to happen. Then there's the prequel book you intended to write.
 
Unless Microsoft have changed direction in recent times, you'd be lucky to get the game finished before they slap you with a cease and desist let alone be invited to publish it on the Xbox One.
 
Other warning signs are that you mention it's been going since 2009, yet there's nothing to show. Another being that you suspended the development less than a week ago in favour of some other mysterious project and then randomly resumed it this week. 
 
 
I don't want to put your project down and while I'd love to be proven wrong, this is most likely going to fail as it stands.
 
Now for the constructive bit:
Narrow the scope of the project. Even an experienced team with millions at their disposal would balk at the idea of pulling something like this off. Don't try to develop the entire project at once. Pick a task (say, a single level) and get it working, it'll keep the team motivated. Set a proper website up and make the development open. People are more likely to contribute to something that they can see is making progress. Learn a useful skill that will allow you to make a worthwhile contribution to the project. I would never join a mod where the leader was just an ideas guy; they have no investment when things get tough (and they'll probably always be tough) and no way to keep the project going forwards even if they're on their own for periods of time. Post when you have something to show. Talk is cheap and making posts is fun but don't let it stand in the way of actually getting stuff done. Join other game development communities and ask for their advice too. Surround yourself with people that actually have experience and can help you keep things in check. The fanboys sure won't.

While I applaud your initiative, I do have to question whether you've bitten off more than you can chew. To produce an AAA quality Halo fan game with both single and multiplayer by late 2015 and get it on the Xbox One, with a tiny, inexperienced team that have never produced a game before is just, well, it's not going to happen. Then there's the prequel book you intended to write.
 
Unless Microsoft have changed direction in recent times, you'd be lucky to get the game finished before they slap you with a cease and desist let alone be invited to publish it on the Xbox One.
 
Other warning signs are that you mention it's been going since 2009, yet there's nothing to show. Another being that you suspended the development less than a week ago in favour of some other mysterious project and then randomly resumed it this week. 
 
 
I don't want to put your project down and while I'd love to be proven wrong, this is most likely going to fail as it stands.
 
Now for the constructive bit:
Narrow the scope of the project. Even an experienced team with millions at their disposal would balk at the idea of pulling something like this off. Don't try to develop the entire project at once. Pick a task (say, a single level) and get it working, it'll keep the team motivated. Set a proper website up and make the development open. People are more likely to contribute to something that they can see is making progress. Learn a useful skill that will allow you to make a worthwhile contribution to the project. I would never join a mod where the leader was just an ideas guy; they have no investment when things get tough (and they'll probably always be tough) and no way to keep the project going forwards even if they're on their own for periods of time. Post when you have something to show. Talk is cheap and making posts is fun but don't let it stand in the way of actually getting stuff done. Join other game development communities and ask for their advice too. Surround yourself with people that actually have experience and can help you keep things in check. The fanboys sure won't.

HAC 2 allows for this (it was added* to 1.10 so the non-HAC 2 heathens could enjoy it too).
 
*technically nothing was added, just a pointless limitiation removed.

HAC 2 allows for this (it was added* to 1.10 so the non-HAC 2 heathens could enjoy it too).
 
*technically nothing was added, just a pointless limitiation removed.

HAC 2 allows for this (it was added* to 1.10 so the non-HAC 2 heathens could enjoy it too).
 
*technically nothing was added, just a pointless limitiation removed.

HAC 2 allows for this (it was added* to 1.10 so the non-HAC 2 heathens could enjoy it too).
 
*technically nothing was added, just a pointless limitiation removed.

While I applaud your initiative, I do have to question whether you've bitten off more than you can chew. To produce an AAA quality Halo fan game with both single and multiplayer by late 2015 and get it on the Xbox One, with a tiny, inexperienced team that have never produced a game before is just, well, it's not going to happen. Then there's the prequel book you intended to write.
 
Unless Microsoft have changed direction in recent times, you'd be lucky to get the game finished before they slap you with a cease and desist let alone be invited to publish it on the Xbox One.
 
Other warning signs are that you mention it's been going since 2009, yet there's nothing to show. Another being that you suspended the development less than a week ago in favour of some other mysterious project and then randomly resumed it this week. 
 
 
I don't want to put your project down and while I'd love to be proven wrong, this is most likely going to fail as it stands.
 
Now for the constructive bit:
Narrow the scope of the project. Even an experienced team with millions at their disposal would balk at the idea of pulling something like this off. Don't try to develop the entire project at once. Pick a task (say, a single level) and get it working, it'll keep the team motivated. Set a proper website up and make the development open. People are more likely to contribute to something that they can see is making progress. Learn a useful skill that will allow you to make a worthwhile contribution to the project. I would never join a mod where the leader was just an ideas guy; they have no investment when things get tough (and they'll probably always be tough) and no way to keep the project going forwards even if they're on their own for periods of time. Post when you have something to show. Talk is cheap and making posts is fun but don't let it stand in the way of actually getting stuff done. Join other game development communities and ask for their advice too. Surround yourself with people that actually have experience and can help you keep things in check. The fanboys sure won't.

While I applaud your initiative, I do have to question whether you've bitten off more than you can chew. To produce an AAA quality Halo fan game with both single and multiplayer by late 2015 and get it on the Xbox One, with a tiny, inexperienced team that have never produced a game before is just, well, it's not going to happen. Then there's the prequel book you intended to write.
 
Unless Microsoft have changed direction in recent times, you'd be lucky to get the game finished before they slap you with a cease and desist let alone be invited to publish it on the Xbox One.
 
Other warning signs are that you mention it's been going since 2009, yet there's nothing to show. Another being that you suspended the development less than a week ago in favour of some other mysterious project and then randomly resumed it this week. 
 
 
I don't want to put your project down and while I'd love to be proven wrong, this is most likely going to fail as it stands.
 
Now for the constructive bit:
Narrow the scope of the project. Even an experienced team with millions at their disposal would balk at the idea of pulling something like this off. Don't try to develop the entire project at once. Pick a task (say, a single level) and get it working, it'll keep the team motivated. Set a proper website up and make the development open. People are more likely to contribute to something that they can see is making progress. Learn a useful skill that will allow you to make a worthwhile contribution to the project. I would never join a mod where the leader was just an ideas guy; they have no investment when things get tough (and they'll probably always be tough) and no way to keep the project going forwards even if they're on their own for periods of time. Post when you have something to show. Talk is cheap and making posts is fun but don't let it stand in the way of actually getting stuff done. Join other game development communities and ask for their advice too. Surround yourself with people that actually have experience and can help you keep things in check. The fanboys sure won't.

What skills do you bring to the table?

What skills do you bring to the table?

SATA 3 is 6Gbit (that's 768MB) as a theoretical maximum, so yes, current drives are already cutting it close.

SATA 3 is 6Gbit (that's 768MB) as a theoretical maximum, so yes, current drives are already cutting it close.