How this works:
AGSI is focused on development of Harpoon 3/ANW, that is the future of AGSI. HC3 is focused on the development of HC and in large part exists outside of AGSI day to day control. AGSI would like nothing more than for us to be good citizens, develop HC, make AGSI money, and not drain time and talent from AGSI. AGSI doesn't say, Tony, fix this bug today, that one tomorrow. We (HC3) will for the most part prioritize on our own, deal with users on our own, etc. AGSI has a pet project now and again and pet feature now and again, those are more our fee for getting to play with the code than directives.
What is the impact?
- We (HC3) thrive on the direct user input. Even all of Rene's no matter how sick of it we may get some days <g>. The H3 programmers are sheltered to make best use of their time writing code, with me on the other hand you'll get direct interaction at the expense of development being slowed by my sticking my nose in around here (on the other hand, I thrive on that input and can code all night with a couple of testers going thru build after build, I think we did the core of land units in one 36 hour period and over 20 builds that Bruce Fenster tested). But the hope is that development will be more in touch with the users and involved as well.
- We don't have much direct interaction with the H3 coders, I think the only interaction has been me asking for advice from time to time. The source code for the two games is separate. If H3 changes ECM, nothing changes in HC. If we change ECM, it doesn't change in H3.
- H3 has a goal and duty to use what they can from the paper rules. HC does not have permission to use the paper rules outside of fixing any code that was already based on the paper rules (mainly Harpoon 3 paper, not the current Harpoon 4.1 and beyond that H3 uses). We often strive to achieve similar results to the paper rules when making our models (see HC new radar model as an example, we tried to match data points with H4.1 paper but we have much more variability and entirely different equations in game).
- Our beta forum isn't even at AGSI
- I hope the message here is that while AGSI has ultimate control, we're pretty much free to do as we please within certain limitations, and that our approach is distinct and different from Harpoon 3/ANW development.
How HC3 is different
- We are small and agile, 3 people strong, H3/ANW has a much larger structure.
- We want to be as transparent as Matrix allows, H3/ANW cannot be as transparent for a number of reasons, not least of which is the impact of the Professional Version and the demands of those customers. If something is broken in HC, we will not deny it. We may quibble about what is a bug and what is a feature request or expected behavior but nothing will be covered up in regards to the game.
- We are listening, Matrix and HarpGamer.com being the two most frequented places but we frequent other forums and lists as well. Just because we listen though doesn't mean everything you personally want is going to be put in the game exactly how you want it. Rene probably has nightmares about me suggesting he find more people looking for the same features to increase the chances something gets implemented.
- We love the game, that's why we are here. I'm not saying the ANW guys don't love the game, far from it in fact, but the only draw we are concerned with is love of the game. To that end...
Our commitment to HC
- We will continue to push HC as far as it can be pushed in terms of features, until AGSI tells us we have to stop. As it stands we work on a 1-year agreement with AGSI, to be renewed each year as long as possible.
- A direct quote regarding HC2002 and something we strive for, "commitment to produce a game so stable that the players commented on how rarely it crashed"
- To keep you informed of developments with the game. Once the game is released I hope to make public the known bug list and release notes for each build. Even if we aren't allowed to do that we will share whatever information we can.