So a couple days ago I wrote a bit on how Bungie got the rug pulled out from under them at E3.

As near as the Intertubes can piece it together, a few days before E3, Microsoft let Bungie know they wouldn't be included in the press conference. Bungie then enacted contingency plans for their own announcement, which is what precipitated the countdown on Bungie.net.

On Tuesday Microsoft told Bungie they wouldn't be allowed to do that, either, and since Microsoft is Bungie's publisher for Halo games, and Microsoft owns the Halo intellectual property, and the announcement concerned Halo, Bungie had to do what Microsoft says, prompting Bungie president Harold Ryan's apology to the fans, which can also be interpreted as a nice polite way of flipping the bird to the publisher.

Ah, the heady days of the early and mid 90s, when Bungie was an independent developer and publisher, master of its own destiny. They developed what they wanted to develop, announced when they wanted to announced, and shipped... well, when the boxes were done.

Those days must seem so simple compared to now.

Because what's going on now is apparently a Bungie announcement scheduled for E3 today-- one likely related to Halo in some way-- has been postponed indefinitely by Bungie's publisher.

That would be Microsoft, for those of you keeping score at home, even though the name "Microsoft" does not appear anywhere in the carefully-worded missive from Bungie president Harold Ryan.

Most fans, of course, don't care what happened or who is at fault. They just knew they were supposed to be seeing something exciting and new within the next twelve hours, and now they won't. For a form of popular entertainment whose fans vacillate back and forth between endurance trials of development waits-- three years for each of the last three Halo games-- and the instant gratification of online multiplayer matches where average lifetimes can be well under thirty seconds, such an indefinite delay is a great disappointment. Even if we don't know what it was we were supposed to be expecting.

So what were we expecting, when can we expect it, and why was it delayed just twelve hours before it was to hit?

This is the most definitive link I can find for what is so far a non-story story about Microsoft somehow letting Bungie become independent again.

The official Microsoft response to reports in Jacob Metcalf's blog that allege Bungie is leaving Microsoft was:

There's been no such announcement.

That's the kind of non-denial denial you'd expect from a company that is the subject of so many non-story stories.

Todd Bishop, on his Seattle Intelligencer blog, gets Robbie Bach at Microsoft to comment on that non-denial denial, and ends up getting an explanation of why the non-denial denial exists:

"The problem is, I can't comment one way or another on any of these rumors. Because then, every time you ask me a question about a rumor, I have to comment definitively, and there's times when I don't want to, and times when I do want to. I just don't. You should interpret it that way. You should interpret it as a neutral 'don't.' "

All in all, it seems very likely that people in Bungie might want to, you know, work on a game that isn't Halo, or isn't a shooter, or, God forbid, isn't a Halo shooter. Farming out Halo Wars to Ensemble and Halo Chronicles to Wingnut seemed to me like Microsoft setting up the Halo franchise to continue while Bungie moved on to other things; but perhaps it was just a move to try and maximize the revenue from the Halo property by developing ancillary products with a series of Halo shooters at the center, developed by Bungie.

I'm going to start with a really, really tiny detail and try to use it to come to a sweeping statement about what makes a game fun. The detail we'll start with is weapon spawns in the Halo games: why timers are fair, but not fun, and why slightly random spawns may be unfair, but more fun.