Testing the Score limit *Movie*

[Odb718]

I got 99,999 as my bet

[HunterXI]

I'm betting that there is no score limit, but to a cerain point it wont show the figures...

if not that, 99999 or 65535 (256*256-1(starts at 0))

[WaLKa]

Got about 2 hours left before i check.. last minute predictions?

[gryphon]

I guess that's another way to get to the same number... I just think it's simpler to come to that conclusion since 65535 = FFFF(hex), and is therefore the largest possible two-byte number. However, tjc's guess makes sense as well, since the game will record negatives. WaLKa's test should be over in a couple of hours, and we'll see. It'd be about our luck that it's a four-byte number, though... I don't think anyone would feel like that much testing.

[WaLKa]

it wouldn't make much sense either, i doubt anyone would ever get a number as high as 1000 in actual gameplay

[HunterXI]

it wouldn't make much sense either, i doubt anyone would ever get a number as high as 1000 in actual gameplay

lol... I guess that Bungie never thought of that, they didn't think of many things you can do in gameplay...

[gryphon]

it wouldn't make much sense either, i doubt anyone would ever get a number as high as 1000 in actual gameplay

That's actually irrelevant. It depends on how the system works. If an int just happens to occupy four bytes on the Xbox, I really doubt Bungie would bother to make it any smaller, even if such large numbers would never be needed.

[[VC]CaptainValor]

So how long will this test last for? Consider in 10 hours he made it to about 16,000, that would mean it would take about 3 days straight to see if our predictions are correct.

[gryphon]

He modded the map so that the Warthog gun does much more damage, and the bullets are more spread out. He tells me it's going at about 1 kill/sec. I estimated it would reach 65535 kills at around 3pm EST today. He said he'd let it go half an hour longer than that.

[WaLKa]

it wouldn't make much sense either, i doubt anyone would ever get a number as high as 1000 in actual gameplay

That's actually irrelevant. It depends on how the system works. If an int just happens to occupy four bytes on the Xbox, I really doubt Bungie would bother to make it any smaller, even if such large numbers would never be needed.

after a while it will start interfering with the score... i guess we'll just have to wait and see..

[WaLKa]

oddest thing happened.
I got 938 kills
but the other players had 22154, 22161, and 22164 deaths
now, taking into acount that i actualled killed them most of those times, then it resets around 65541, which is awfully close to Gryphons estimate. Those extra deaths can be accounted for by being killed by vehicles while being set up. I can only remeber one.
So as far as the score limit is concerned. It resets after 66540

[HunterXI]

66540? there's something about that number... maybe it has to do with the variable type it's stored in?

[gryphon]

He meant 65540. Which is close to 65535. Which equals FFFF.

[HunterXI]

wait, Ive almost figured out...

anyway, I think the number has to do with Octal, not Hex, so we would be way off...

if you take the number it reset after (66540), and divide it by 100, you get 655.4... and if I'm not wrong, 556 in octal is 777, or vice versa, I cant remember which... more strange calculations:

if you divide 66540 by 556, you get 117.56.... etc (I think it's endless)...

anyway, if you measure throughput in cps, you have to divide it by 117.1875 to get the throughput in kb/s or mb/s etc....

its not an answer, but it's some stuff I found...

also some other calculations I found noteworthy:

66540/111=599
66540/70=950
66540/73=911
66540/74=899
66540/119=559
66540/120=554
66540/123=540

but here's one I found kinda intrest worthy:

66540/128=519

I think this may have something to do with Binary and Octal. remember the numerical patterns you have in Binary, ie multiples of 2; 64, 128, 256, 512, 1024, etc.

but also remember that Octal stores numbers in a similar fashion to Binary but a number in Octal does not equal the same number in Binary; for example the 556=777 example...

but meh, Im tired, and Im lazy, so Ill stop here...

[WaLKa]

Heres a pic of the final score, sorry for the delay.

[[users]ReApEr]

lol and the point to this whole thing was......

[baby jesus]

thahah thats pretty awesome, what do you mean someone had alot of free time.. no he didn't. All he did was tape it down, wasn't like he sat there for 10 hours killing people

[WaLKa]

lol and the point to this whole thing was......

testing the score limit... duh?

[[users]ReApEr]

wait, Ive almost figured out...

anyway, I think the number has to do with Octal, not Hex, so we would be way off...

if you take the number it reset after (66540), and divide it by 100, you get 655.4... and if I'm not wrong, 556 in octal is 777, or vice versa, I cant remember which... more strange calculations:

if you divide 66540 by 556, you get 117.56.... etc (I think it's endless)...

anyway, if you measure throughput in cps, you have to divide it by 117.1875 to get the throughput in kb/s or mb/s etc....

its not an answer, but it's some stuff I found...

also some other calculations I found noteworthy:

66540/111=599
66540/70=950
66540/73=911
66540/74=899
66540/119=559
66540/120=554
66540/123=540

but here's one I found kinda intrest worthy:

66540/128=519

I think this may have something to do with Binary and Octal. remember the numerical patterns you have in Binary, ie multiples of 2; 64, 128, 256, 512, 1024, etc.

but also remember that Octal stores numbers in a similar fashion to Binary but a number in Octal does not equal the same number in Binary; for example the 556=777 example...

but meh, Im tired, and Im lazy, so Ill stop here...

Wow hunter did some math .

[EthanDM]

Ahh... man this is sosososo funny! LMAO!