Now that I have some more information I can clear things up for you.
CronoDroid wrote:QUOTE (CronoDroid @ May 29 2009, 07:59 PM) How can they have been done at the last minute? The changes were announced a lot time ago AND we had the whole thread talking first about 1. why IC doesn't need that sort of change (which nobody seems to care about) and 2. Drizzo talking about how miner AI gets confused with the rip time change.
If you haven't made another version, why is there this "two versions of CC_05 floating around"? Who's making the core changes anyway?
Here's what happened:
Andon makes the updates to CC_04, creating the new CC_05I check changes, bring up problems & potential issuesFixes are madeI check the core over again, along with spidey, andon & phoenix1Another issue is raisedThe issue is fixed, the core gets double checked again and cleared for autoupdateThe changelog is released and the community points out the 35s rip time problem.The rip time is reverted to 30sThe core gets sent to TE for AU without anyone saying they checked it, along with the new garrison .cvh
The last two points there are what caused all the confusion. I think the "two versions" issue came from one version of the core being cleared & sent off, but the new one (with the corrected rip time) also had to be sent off. You may blame me for not getting to double check the riptime changes, as that was a change to the core file. I've done some complaining to the rest of the CC team about this already, because I hate dealing with the mess of a buggy update as much as people hate playing on it. In the future we'll be making sure that somebody has checked the core over before its sent off.
QUOTE How the hell can you not know? Aren't there threads for this thing in your private dev forum?![/quote]
Everything's been straightforward and organized in the private forum actually. But there wasn't much mention of the updated garrison, hence why I wasn't sure what was going on with it. Adam finally cleared things up for me:
Adam4 wrote:QUOTE (Adam4 @ May 29 2009, 08:17 PM)It was an issue brought up in the Enforcement Zone. It was decided in the EZ that an updated cvh should be pushed to prevent any claims of cheating by using the base hole.
The CC team hadn't done any testing on the .cvh, probably because it wasn't mentioned anywhere as going in. At least thats why I never checked it - I didn't even know it was going into the update until it had already been done.
QUOTE I agree that TE putting stuff on autoupdate is out of your hands. But aside from that...all work on CC is in your hands. I'm not exactly sure whose hands it is in if it isn't in yours.[/quote]
Andon and I handle all of the actual core work (by that I mean the .igc file and ICE). I double check his work and vice versa, along with any other team members that get around to it. We actually ironed out about a half dozen issues before the core was even considered done. The miscommunication over the miner reversion & unexpected addition of the garrison .cvh is what threw a wrench into this update, hence the current mess.
All that said, I think the whole ordeal has been blown out of proportion. IC becomes unpopular for a couple of days, yeah thats not good but its not like the release crashes the servers either. Mistakes were made, corrections have also been made and Alleg continues. Now stop bickering and go vote on TF.
