I'm going to get Pulse-like on this one and talk about science. Well,
computer science anyhow.
Most every programming and even scripting language has the equivalent of the C and C++ SWITCH statement. Many of you here have used it in your own programming work. Essentially, it allows you to test the value of a certain variable and selectively execute code based on that value.
Consider the following:
switch (rnd) {
case 1:
SpawnBob(Location_1);
break;
case 2:
SpawnBob(Location_2);
break;
case 3:
SpawnBob(Location_3);
break;
}
In the code above, assume "rnd' is a variable containing a random number,
expected to be in the range 1-3. The code would then randomly call the SpawnBOB function with one of three possible location values ("Location_1", "Location_2", or "Location_3").
Still with me? So assume the code above executes when the Spire area loads as part of the script that populates the enemies of the area and generally sets things in motion.
So long as the "rnd" variable evaluates to 1, 2, or 3 then all is well.
UNTIL...
You realize that the value of "rnd" sometimes becomes 0, because you're generating it randomly and you forgot that the default range of your random number function begins with 0. So "rnd" actually can be any number between 0 and 3. When the control variable of the SWITCH statement doesn't match a testing condition, NOTHING HAPPENS. In other words, if 0 is chosen as the random number (or 4, or 5, or any other number for which there isn't a "case" condition) then no spawn function gets called and no error is generated. It's an easy mistake to make, and since it wouldn't generate a compile or run-time error it could easily slip through. It could also easily be missed in testing, since a missing BOB might be assumed to have simply slipped away and despawned, as they often do. I suppose that comes down to how thoroughly the testers were looking at the BOB spawning behavior in that particular area.
I have been referring to the selection of a non-spawning BOB as the "1.4" condition, since that would be the next logical numbering of a fourth BOB spawning point for BOB 5-B-1.
I'm not totally giving up that we have somehow missed the BOB, but we are really running out of options here. I think we're approaching the point where one of the following must be true:
- There is a hidden switch (or switches) we haven't found which would do something cool (like Reach Racer), and would also spawn variant 1.4 if it had been randomly chosen.
- This is the first occurrence of a BOB spawn which only spawns on Legendary, either by Bungie design or scripting accident.
- The 1.4 variant spawns before the Falcon flight (at the very beginning of Rally Point Bravo.) It would be strange for a variant spawn point to be in a completely different loading zone from the rest, but hey- it's possible.
I suppose to be thorough, I should probably include that we just haven't found it in the Spire area yet, but be my guest:
http://www.bungie.net/Stats/Reach/FileDetails.aspx?fid=24788284&player=ColdGliderThe saved film above chooses the non-spawning (or non-found) BOB at 6:44 when I enter the Spire area after the Falcon flight. Have a look around, and please prove me wrong!