Making Infinity

depends on what concept of infinity you use as confusing as it is

3 Likes

I mean we are not counting infinity as a number in your situation?

I don’t know what my ‘situation’ is, but infinity is—in all situations—not a number by definition.

thats what I am meaning

Infinity won’t be a number and never will be.

Unless it’s in Gimkit. Then it’s something greater than 2^1024.

This is hurting my brain. I really want to ping jjinitzan right now…

is it because its infinity? its not a specific number, it is all numbers and never ends and there is no start nor end to infinity + it cannot be used in an equation

2 Likes

Never mind the question.
image

this is as close as we can get.

3 Likes

What? Infinity is not a number in the set of all reals. It’s a concept representing something larger than any natural number. Definitions vary depending on what the context is, but it does not fit into any set of generally accepted and used numbers.
In our case, it’s simply an output when a number does not fit into the 1024 bit integer limit.

Also, I tested it, and once a property equals Infinity, it cannot be changed by operations. Closed the tab and forgot to test resetting it though, but I assume that works fine.

5 Likes

Are you able to attempt to subtract infinity from infinity to reset it back to 0? Or does the unaffected by operations apply in this case as well.
Furthermore, are you able to create negative infinity?

(I can’t hop on gimkit rn to test this)

yes, you can

divide by negative.

infinity cannot be subtracted or put into any equation because it always goes back to infinity

Wait if it uses an equation, won’t it evenly stumble back into normal numbers based on what @Epi320 post said

Never mind the question.


this is as close as we can get.

(there was a what in-between the wait and the if I don’t know how that happened)

Ok.
so, u dont fully understand.
2^1024 is not undefined, in fact, its a natrual number. the problem is, because it is so big, computers cant handle it, and say undefined. What you said is true, it does become natural, but it was always natural, the only reason it is undefined is because it is too big. Like, REALLLLY big.

1 Like

This is interesting. I checked, and that number doesn’t seem to have any strange mathematical properties, and does not fit xn, where x and n are both integers. I wonder why that returns 16331239353195370 in particular?

Edit: Oh, apparently it’s the reciprocal of cos(pi/2). Thanks.

also i'm back hi
1 Like

Nah, a damage modifier set to “x :infinity: “

3 Likes

Big Dum Idea:
We can use the number as an placeholder for properties to be guaranteed to be lower in some cases within block code

1 Like

I don’t think damage modifiers can go that high.

Oof. Well, if other things can, that’s still epic

i googled it and found this:

tl;dr you get that number because of floating-point rounding errors. this happens everywhere, such as minecraft, as stated here in the wiki:

2^1024 is the maximum value for a 64-bit floating-point value in Java. Beyond this point, the player’s coordinates would roll over to read “infinity,” as the 64-bit float has run out of bits to represent coordinate data, possible to achieve with Cheat Engine in Beta.

also stated in the stackexchange article is that this issue is very widespread

wdym? after 21024, computers just can’t handle it anymore and “rolls into” infinity. 21024 isn’t actually infinity though

9 Likes

Oh so that’s why, ok that explains it, thanks @eiqcrmeliutgwhc

2 Likes