That's the hexadecimal digits, you need to read it as a float in big endian,
41 20 00 00 read in big endian as a float produces: 10. Are you sure that's for a mongoose, I'm asking because its coming up as 10, not 60...
And thanks for releasing it, shade.
Supermodder911 wrote:It's listed as 10 for each mongoose...
Right, but I think he's saying it's showing cost as 10 for all three of them together.
I don't think so, I believe there is a "Tag_Index_Entry" for each object on the map, not one for each type of object. So, logically, the cost would be the cost for that one object.
Supermodder911 wrote:It's listed as 10 for each mongoose...
Right, but I think he's saying it's showing cost as 10 for all three of them together.
I don't think so, I believe there is a "Tag_Index_Entry" for each object on the map, not one for each type of object. So, logically, the cost would be the cost for that one object.
That does seem to be the most logical, but then why would there even need to be a spot for the "number on map"? I haven't had a chance to look into this since the new info has been released, so does anyone else know?
Supermodder911 wrote:It's listed as 10 for each mongoose...
Right, but I think he's saying it's showing cost as 10 for all three of them together.
I don't think so, I believe there is a "Tag_Index_Entry" for each object on the map, not one for each type of object. So, logically, the cost would be the cost for that one object.
That does seem to be the most logical, but then why would there even need to be a spot for the "number on map"? I haven't had a chance to look into this since the new info has been released, so does anyone else know?
Because it lists that information in the game?...
Hijikata wrote:The fact you love Jesus doesn't change the fact you're a *** mental patient. It just means you're a mental patient with a great imaginary friend.
rocket360gs wrote:That does seem to be the most logical, but then why would there even need to be a spot for the "number on map"? I haven't had a chance to look into this since the new info has been released, so does anyone else know?
Because it lists that information in the game?...
Right, but why would it need that information in every single instance of that object rather than just once globally? But like I said, I haven't looked so I don't know, just thinking out loud here.
OK, this is probably not worh going on and on about, but what I meant was (and I realize now it was not clear) why would the NUMBER of a given object on the map (say, 3 mongeese) need to be defined every time you have an instance of a mongoose? I know why spawn info, coords, etc would need to be unnique to each one, but this is just a global value.
WOW did not realize the whole other page of posting so i gues my information has already been stated before but anyway:
well correct me if i am wrong here, especially because the hex is easier for me to understand then shade whitepaper (sorry shade but nice work anywork way because i can smeel the effort), but 4120 as a decimal number is 16672 but possibly and this is where i am not sure i know the input *space* is 20 so when you take that out you get 65 which is a little closer then 4120. I am trying a little ^.^
edit again:
@rocket i think you are right there is the identifier that defines all these properties of every mongoose that meets these standards...Wow i confused myself with your dilemma. It would make sense to globally define the properties for efficiency but what about spawn time? If i have time tonight i will try some research here to figure it out by testing but interesting conundrum here
CompKronos wrote:WOW did not realize the whole other page of posting so i gues my information has already been stated before but anyway:
well correct me if i am wrong here, especially because the hex is easier for me to understand then shade whitepaper (sorry shade but nice work anywork way because i can smeel the effort), but 4120 as a decimal number is 16672 but possibly and this is where i am not sure i know the input *space* is 20 so when you take that out you get 65 which is a little closer then 4120. I am trying a little ^.^
edit again:
@rocket i think you are right there is the identifier that defines all these properties of every mongoose that meets these standards...Wow i confused myself with your dilemma. It would make sense to globally define the properties for efficiency but what about spawn time? If i have time tonight i will try some research here to figure it out by testing but interesting conundrum here
Uh, the reason for 41200000 equaling 10 in decimal is because it is a float. It would equal 16672 as regular 32 bit int (which it is not in this case).
) on the pit.
