I have several instances where I need to use the Binary custom type with multiple bytes in a row, but the Binary custom type seems to be handled as a Little Endian type, and therefore doesn't display the bits in the proper order. Can someone make a Big Endian custom type of this?

It gives the scripts for 2 and 4 byte (1 byte is the same in both big and little), if you need something different then you need to actually say what you need other than just "Big Endian".

As far as I knew from what you posted, if they weren't enough then you had enough knowledge to take the scripts given and google how the instructions worked and what you'd need to do larger values. Since assuming that takes less work (and thus time I could spend on my kids, my friends, other people needing help, or simply hacking games) than me guessing at everything you might possibly be needing and doing all of them for you, that's all I gave you. It's really up to you to provide the information needed for people to help you get what you need, not us to play 20(0) questions to figure it out...

It gives the scripts for 2 and 4 byte (1 byte is the same in both big and little), if you need something different then you need to actually say what you need other than just "Big Endian".

As far as I knew from what you posted, if they weren't enough then you had enough knowledge to take the scripts given and google how the instructions worked and what you'd need to do larger values. Since assuming that takes less work (and thus time I could spend on my kids, my friends, other people needing help, or simply hacking games) than me guessing at everything you might possibly be needing and doing all of them for you, that's all I gave you. It's really up to you to provide the information needed for people to help you get what you need, not us to play 20(0) questions to figure it out...

I clearly said that I need a custom type for Binary Big Endian. I don't see how this can possibly be made more clear. Linking me to the code for 2 Byte and 4 Byte Big Endian custom types doesn't help me with this, because the general coding for the Binary type is completely different.

Everything on a computer is binary... if you haven't learned that you might want to do some more research. CE showing it as hexadecimal, decimal, floating point, ASCII/Unicode, etc. is all just for convenience.

Big and Little Endian refer to the order of bytes in multi-byte values, Little Endian stores the least significant byte(s) first while Big Endian stores the most significant byte(s) first.

To copy an explanation I gave on reddit:

Quote:

If you had the value, say, 5461 which is 00010101 01010101 Big Endian says to store each byte exactly like that in memory with the 0001010 first followed by the 01010101 byte while Little Endian says to reverse the bytes and store 01010101 first followed by 00010101. The effect is that with Big Endian the most "significant" value is stored first while with Little Endian the "least" significant value is stored first and that with Little Endian you can easy read a value as 1 byte, 2 bytes, 4, 8, etc. simply by changing how many bytes in memory you choose to read while with Big Endian if you have 5461 stored as 2 bytes then you have 00010101 01010101 but if you have it stored as 4 bytes then you have 00000000 00000000 00010101 01010101, meaning to read it as 2 bytes you'd have to add 2 bytes to the address before you tried to read it with Little Endian the 4 byte version would be 01010101 00010101 00000000 00000000 so you don't have to add anything to read it as only 2 bytes (or 1, etc.).

If you wanted to represent it in hexadecimal, then 5461 is 0x15 55, which is how it'd be stored in Big Endian Format, the 0x15 byte first (0001 0101, 0x1 0x5) followed by the 0x55 byte (0101 0101, 0x5 0x5) while Little Endian would store the bytes in reverse with 0x55 (0101 0101, 0x5 0x5) first followed by 0x15 (0001 0101, 0x1 0x5).

offtopic: is it just me or does this topic show clearly how unrelated number of posts is to how advanced of a cheater you are?

edit (after DB/panraven): ah, I forgot CE had a actual binary scan (I never use it, but it's also not a custom AA/lua type), but even so big/little endian doesn't really apply to it unless you're still dealing with bytes and just want to represent them in binary for whatever reason... panraven's solution is essentially just doing a string reverse on the bits (so 1101 becomes 1011) which may be what's needed in this case but isn't related to big/little endian other than the fact that something is being reversed and it happens to be binary.

Last edited by FreeER on Thu Mar 23, 2017 7:08 am; edited 2 times in total

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum