Object Manager's reach

[_duracell]

I tried searching for this answer with no luck. How far of a reach does the Object Manager have? That is, when you're looping through WoW's Object Manager and storing each object, what is the limitation for determining which objects are included and which are excluded due to them being out of a certain radius or zone? Are all of the objects in the player's current zone included in the OM?

I'm trying to decide how often I should append/update my GameObject lists as the player moves across the map.

[Ssateneth]

I'm sorry, I do not know the specific distance. All I know is its a radius from your character.

The updating also seems to be around 5 seconds, easily calculated while flying around on high speed air mount above icecrown while looking down, timing between mob spawns from area to area.

[Nesox]

I believe its 100 yards or so

[RoKFenris]

WoW's servers seem to divide the world into a grid or something similar, sending to the client updates to objects in the cell the client is and adjacent cells. So, there isn't an update speed or fixed radius for the client to receive new objects, they appear as you cross the boundaries of different cells. That said, there are some mobs and objects that are visible from a really long range, such as the Fel Reaver roaming in Hellfire Peninsula; I believe those specific ones might be visible from the whole zone.

[lanman92]

I can't see that being that way. If so, why can we see all of the mobs in the other cells adjacent to us? Right before we cross the border of one, we can see the other cell's objects. The radius is probably about 100 yds like nesox said.

[_duracell]

WoW's servers seem to divide the world into a grid or something similar, sending to the client updates to objects in the cell the client is and adjacent cells. So, there isn't an update speed or fixed radius for the client to receive new objects, they appear as you cross the boundaries of different cells. That said, there are some mobs and objects that are visible from a really long range, such as the Fel Reaver roaming in Hellfire Peninsula; I believe those specific ones might be visible from the whole zone.

Oh, I wasn't referring to how often the client receives data for surrounding objects. I meant that I was trying to figure out how many of the surrounding objects are stored in the Object Manager offset when I iterate through each object.

For example, if I loop through the OM while my player is in zone A, then move my player into a different zone B without reiterating through the OM, I assume there would be data discrepancies between the stored OM data and the actual objects in the new zone. It sounds like I would be okay to rescan the OM every time the player's zone changes. Or maybe I could store the player's XY position at the time of the OM loop, periodically compare it to his current XY position, and once the difference surpasses a certain distance (100 yard radius?), reiterate through the OM.

[lanman92]

Just run through the OM linked list in a thread every few seconds. It's not that much overhead. You will have to reload the OM and LocalPlayer when your zone changes though(I think).

[ramey]

Why do you need to store the objects at all?

[Apoc]

Why do you need to store the objects at all?

Because storing a copy of the GUID/Pointer is faster than reading it each time?

[Cypher]

Because storing a copy of the GUID/Pointer is faster than reading it each time?

It also means you can sort the objects using your own criterion which can improve lookup time even further.

[Apoc]

It also means you can sort the objects using your own criterion which can improve lookup time even further.

/me nods

Wasn't going to bother explaining intricacies as it's fairly obvious, this thread is far below the level of using sort algorithms.

[ramey]

Good points :X never thought about it, then again though I haven't even really gotten into building a bot yet. Never had a proper interest, but my interest raised a bit once I started building that framework that I'm doing...

Thanks for the reasons, surprised I posted such a crap question and didn't think for a second.

[amadmonk]

OM cached list with rich data + LINQ == sweetest of object sorting/searching love.

[Nesox]

/nods LINQ is really nice
@op: you should just update your lists each frame.
I got 7 lists that gets refreshed each frame, one for each objettype

[Apoc]

/nods LINQ is really nice
@op: you should just update your lists each frame.
I got 7 lists that gets refreshed each frame, one for each objettype

Didn't I tell you not to do that?!?

Update each frame = fine.

Updating 7 lists = baaaaaaaaaaaaaaaaaaad.

Use 1 list, and filter when needed. Tard.