M-M2 Indexing Thoughts?!

[UnknOwned]

Been messing around with the new memory-model structure for a while today but am getting a bit tired and kinda want to call it a day, however there are still a few things that I don't quite understand.
The old system had inconsistency however was easy to index since the 4999 indexes was indexed by a header. We had a clear list with entries at 0x0 for each step array. But now the header is gone and after a quick overview it all looks a bit messy

In 3.0.2 the array is 0x170 bytes long, apparently WotLK have brought additional 64 bytes data (from 0x10C bytes in 2.4.3).
The indexing is quite mysterious. It goes like this:

 |obj|obj|nill|obj|obj|nill|

And additionally the first links to the entry of a array (0x0) while the 2nd links to 0x74 in the array so its like:

 |obj(0x0)|obj(0x74)|nill|obj(0x0)|obj(0x74)|nill|

Wonder why that is?

So, after updating my old indexing function that take all entities from the model index I realised that not all models was indexed in the global index.:nuts:



Indexing.



After full index termination.


Now as you can see there are quite a few models there that are not a part of the global index.

So, i wonder if anyone got some additional intel on the new m-m2 array index?

[Cypher]

I had no problems looping through the WorldObj array when I tried earlier. Not on my main PC so I don't have my IDA DB or VS Projects to check the offsets for you, but I definitely had it working the same as in 2.4.3.