Cheat Engine

[Zanko]

ADDRESS VALUE(HEX)
0x0 08
0x1 02
0x2 00
0x3 00

If I read 2 bytes with 0x0 as base my end result is (0208)
If I read 4 bytes with 0x0 as base my end result is (00000208)

If I read array of byte of 2 bytes with 0x0 as base my end result is (08,02)
If I read array of byte of 4 bytes with 0x0 as base my end result is (08,02,00,00)

So when I read array of byte should I reverse the array to get my expected result?

[cooleko]

Computers just always use (LSByte to MSByte). Humans learn the opposite (MSDigit to LSDigit).

When CE displays 2byte and 4byes (aka 16 bit number and 32bit number), it takes the liberty of displaying the hex to you as we would read it.

However, when CE displays an array of bytes, it simply shows you exactly what the array is as it appears in memory.

Since memory is what the computer sees and uses, it will be in (LSByte to MSByte).

Fortunately, when using CE, it always takes care of this for you.

The question for how to help you leaves some confusion. What do you need help with?
Are you reading this from the address list? Lua Script? AA Script?
What do you need: Hex, int, AoB?

In address list, just use w/e format you need and let CE show you the value as you need it.

In LUA, just use readInterger/Float/Bytes

In AA, just use mov/cmp to do what you need.

If you just wanted an explanation for the differences, to put it simply it is all about the difference between a computer and a human and how they have been taught how to read numbers.

[ParkourPenguin]

@cooleko: Your interpretation of endianness is incorrect. The OP was asking about the endianness of bytes, not bits. The term endianness is seldom used to describe the order bits come in. Instead, terms like LSB, MSB, and bit numbering are more common ways of specifying bit order.

Regardless, the term endianness refers to the order the bytes of any singular data object are stored in memory. Little-endian means the least significant bytes come first, while big-endian means the most significant bytes come first.

Most numbers you'll see will be stored in little-endian. As a human, you'll have to manually reverse the byte order if you want to interpret the bytes in memory as a specific type of data. However, when using a computer, it is done automatically for primitive data types. If you're specifying your own custom data type, however, then you may need to take endianness into account (e.g. 8 byte data type in a 32-bit process).

Examples:

[cooleko]

[ParkourPenguin]

Emphasis on "it should be stated explicitly to avoid confusion with least significant bit." The majority of the time I've seen the acronyms LSB/MSB, they were referring to bits; however, that's not remarkably important.

The principal reason I thought you were referring to bits was that you stated computers use big-endian. With regards to bits, this is correct. For example, the byte D6 is 11010110 in binary (and in memory). The most significant bit comes first, while the least significant bit comes last. With regards to bytes, however, this is incorrect. As I explained in my previous post, computers store the bytes in little-endian: the least significant byte comes first, and the most significant byte comes last.

Now that I look back on your post in more detail, it's clear you're confusing big-endian for little-endian. I should have recognized this and been ambiguous when referring to your interpretation of the acronyms LSB and MSB in your explanation. As such, my previous comment wasn't pedantic, but rather flawed in my reasoning of why your explanation is incorrect. Hopefully this post rectifies this situation.

[cooleko]

Opps, gotcha, My parentheticals were correct but my identification was backwards. Removed the designation to alleviate any potential confusion.