Maths .-.

Can someone please explain to me what the math does?

angle = Maths::get360DegreesFrom256(this.get_u8("angle"));

Cheers

 

Maths is actually a namespace.
Click me for more information about what namespaces are and what they're used for.
If you have a look on the global functions inside the Functions.txt ("..\KAG\Manual\interface") you'll find a bunch of other namespaces such as:

You can find other namespaces declared in some scripts as well, here is a tiny example hoping that it could help you understand what I mean.

Spoiler: "KnightStates" namespace declaring

which had been used later in the line 77, this way.

Spoiler

as you can see shielding is actually a part of the namespace KnightStates.

PS: The script we used as an example was "KnightCommon.as" (inside "..\KAG\Base\Entities\Characters\Knight"), feel free to have a look on the other classes' common scripts since they use lots of other namespaces.

 

Uh Sorry think I wrote it wrong, let me rephrase it. What does this math equation solve?
the "get360DegreesFrom256" bit I meant, nice links bro

 

lol, ok.
So it basically gives you the angle (360 degrees) from a uint8 (Unsigned 8 bits integer).
as you know a uint8 would have 256 values (0..255) and thus we can't use it to get angles (0..359) [360 values] so the solution is using that.
Example: 360/256 = 1.40625 (think about it like this, 256*number=360, so what is that number supposed to be?).
Hence, Maths::get360DegreesFrom256(1) is actually equal to 1.40625.
Maths::get360DegreesFrom256(2) is actually equal to 2.8125.
and Maths::get360DegreesFrom256(255) would be equal to 358.594 (almost 359 ).
tl;dr it helps converting from (0..255) to (0..359) by multiplying a uint8 by 1.40625 to give a float type result.
PS: Keep in mind that Maths::get256DegreesFrom360(x) does the opposite, where x is a float type.
Hope this helps.

 

Simple enough, so it converts a float to a value that is an acceptable 8bit value?
Why does one need to convert a number to an 8bit integer? To work with the engine?

 

By the looks of it, the conversion is needed so the thing can understand it. If not, then there wouldn't have a need for conversion.

 

Cinc you ball bag.

 

why are you such a dangleberry?

 

And vice versa.

Performance-wise reasons mainly, I believe.
To simplify the explanation, let's look at the situation below:
Monkey and Cinc chat with each other on a daily basis, they thought about two possible (old-fashioned) ways of communication:

1. Exchanging their daily message on a new tiny piece of paper (a new piece of paper every time they have a new message to send).
2. Exchanging their daily message on a new big, heavy book (a new book every time they have a message).

Obviously, the best way would be using the light-weighted paper instead of the heavy book.
Same goes for KAG, the server and the clients need to synchronize the angle value at times. It would be much better to send (and receive) it as a uint8 value instead of a float one, simply because the size of a float type is far more bigger than a uint8 type; and as a matter of fact, smaller variables are transmitted faster than bigger ones (not to mention saving network data) and hence having better performances.

 

Gotcha, computers can pull numbers faster in bits :o Thanks for the answers champ!

 

I think this is going to be one of them, the more questions you ask, the more questions you have scenarios.
Just one more...

Is it just the number that is bigger, resulting in a loss of computer processing? or is there some other magic going on?
why is 1.40625 faster to call than 1.0?

 

Given how computers work, the explicit value "1.0" would also be of type float, since there is an explicit decimal point there, and as such the two numbers would be the same size and take the same time to transmit, both being 32 bit floating point numbers.

The difference between 1.40625 and 1 though (no decimal point), is that 1.40625 must be stored as a float and so takes 32 bits of space, but "1" can be stored as an 8 bit unsigned integer, which takes 4x less space (8 vs 32). As such, it's the difference between sending 32 bits of information over a network and 8 bits of information, clearly 8 bits is less and so would take less time to transmit. This difference is more important if you consider how often that information is transmitted and how many are transmitted. i.e. Ten 8 bit numbers ten times a second, or ten 32 bit numbers ten times a second - 800 bits vs 3200 bits in that scenario.

 

Nothing's wrong about asking questions.

No, it's not actually that.. and to be frank I couldn't have said it better than Verra:

Let's say you have 2 pieces of paper, the same size and the same weight.
Even If you write on the first one "9999" and write on the second one "0", their weight and size won't change, thus they're basically the same when it comes to interacting with them (carrying them?).
Having a small piece of paper in which is written "90" and a big heavy one with "1" written on it, still means that the second one is harder to deal with than the first one (see: size and weight).
everything in a computer is stored in bits, a bit value could either be equal to 1 or 0.
a uint8 is composed of 8 bits, hence we get 8 cases reserved for that variable.

Spoiler

a float type requires 32 bits, which means 32 cases that get reserved for that variable.

Spoiler

As you can easily notice the float type requires 4 times the amount of cases required by a uint8 variable.
So since it's an available solution we could use a uint8 type to reserve the least possible amount of cases without actually affecting the way our variable would work. By doing so, we can reduce the amount of data transferred to assure the synchronization of server and a client in a fast efficient way.
@Edit: Haha, it looks like SlayerSean ninja'd me. :^)

 

Ahh, I was thinking the number 1.40625 was being used in it's entirety, but it's actually being seen as a 1?

 

I have a new maths question. How would I calculate a blob's x and y velocities relative from it's angle?
triggermeomitry?

 

*ba dum tss*

 

Once the velocity vector is already orientated to the correct angle, then you can now break the velocity vector into x and y velocity vector. This is now where you use trigonometry if doing it by hand knowing the velocity vector and the angle of orientation.