## Voila! Look at this!

~~What the Bug Is~~ The Floating Point Error

Oh noes! It affects whole numbers? That’s just insane!! Can you believe it? Earlier it was tons of decimals into parts, now it’s inside whole numbers? ~~What sorcery is this?~~

**Reproduction:**

- Create an instance of a normal part.
- Type in any number as high as you can think of.
- Result as in the gif above.

*Side notes:*

- Bug occurs 100% of the time.
- It is a classic floating point error,
~~and I really hate this.~~

**Explanation:**

As mentioned earlier, it’s floating point errors, computers aren’t as accurate as they are. They sometimes mess up and create those errors. It might not be exactly 1, it could be 1.00000000042829.

If you want an in-depth explanation, check out this page all about it!

There are two types of errors: Cancellation & Rounding.

Both explained in the wikipedia page link above.

Now who told us that computers can be **very precise**? They can still fail at tasking some numbers correctly and precisely. And boom, a flaw was born within computers.

*This is addressed for those who doesn’t understand the super-slim gaps in building, excessive decimals in printing certain values, or even anything that comes along with numbers.*