User:BandanaBoy679/Geittng coordinates of Far Lands sets wrong

I saw you kinda got the coordinates of every Far Lands' sets wrong, and here is what they actually are:

When I play Minecraft, I do it via XBOX One edition.

But, here are the real limits of Minecraft Java Edition:

Floating-point precision errors (X/Z: 16,384 to 2,147,483,648)

Spawn chunk glitch (X/Z: 524,288 to 1,073,741,824)

Far Lands (X/Z: 12,550,824 to 1,004,065,920) Fake Chunks (X/Z: >31,999,999) Farther Lands (X/Z: 1,004,065,920 to 80,325,273,600)

The 32 Bit Limit (X/Z: >2,147,483,648)

Cloud Render Limit (X/Z: 25,769,803,000 to 25,769,804,000)

The Chunk Limit (X/Z: >34,359,738,368)

Fartherer Lands (X/Z: 80,325,273,600 to 6,142,021,888,000)

Farthest Lands (X/Z: +6,142,021,888,000)

The 64 Bit Limit (X/Z: +9,223,372,036,854,775,808)

64 Bit Floating Limit (X/Z: +1797693134862315907729305190789e+308)

And here are the Limits of Minecraft Bedrock Edition: Versions: Windows 10 XBOX One Mobile Nintendo Switch PlayStation4

Floating-Point Precision Errors (X/Z: 131,072 to 1,073,741,824) This is where the player loses precision, and entities will be like this at double the distance.

Floating-Point Entity Precision Errors (X/Z: 262,144 to 1,073,741,824) This is where, not only the player, but every entity, loses precision.

Far Lands (X/Z: 12,550,824) Note: On Windows 10, XBOX One, and PlayStation4, they do not generate, however, on Mobile and Nintendo Switch, they do generate.

Stripe Lands (X/Z: 16,777,216) This is where the precision loss is more than 1 block.

Slice Lands/2 Dimension Lands (X/Z: 33,554,432) This is where horizontal block rendering stops.

The 32 Bit Limit (X/Z: >2,147,483,648) At this point, all the game will do is crash.