Guid more than once?

[jbrauman]

For my mine bot I am thinking of blacklisting a certain rock if I cant get to it, so I will ignore that rock from now on. I am planning to blacklist it using the GUID of that rock. What are the chances that if that rock despawns, another will spawn with the same GUID? Or should I blacklist that GUID ONLY if it has the same XYZ value?

Thanks.

[kynox]

I'm just guessing here, but i would imagine that every Mining/Herb node in WoW has its own GUID.

However, being that each node has a unique spawn position, it would be better off to blacklist the affected XYZ.

[Bunster]

I'm just guessing here, but i would imagine that every Mining/Herb node in WoW has its own GUID.

However, being that each node has a unique spawn position, it would be better off to blacklist the affected XYZ.

Ye they all have a unique spawn

[RawrSnarl]

I was assuming each object would respawn with the same GUID each time. If this is the case, the "cleanest" method would be to blacklist by GUID...but if you don't feel like testing that method, XYZ will work, as Kynox suggested.

[schlumpf]

Wasn't there something like the GUID being assembled by different values like the type, the static id and some changeing id?

[arigity]

Wasn't there something like the GUID being assembled by different values like the type, the static id and some changeing id?

yes GUID's are comprised of several parts including a type identifier its item ID and it's number out of the total objects. however thats not very helpful to what he wants unless he's trying to blacklist all objects of a specific id not just ones he can't reach.

[schlumpf]

I thought that each individual spawn would have its own id in the GUID too. Sorry.

[Apoc]

GUID's change after each spawn. Though, it is likely that it can be the same out of sheer coincidence, it's not likely at all. Blacklist the location. Only blacklist GUIDs when you're doing short-term blacklisting.

[jbrauman]

Thanks for the answers, will blacklist by GUID + Position =]

[g3gg0]

imho only the position makes sense. its the position that "makes" the ore buggy.

GUIDs change every spawn and may repeat at any other time - so you may have blacklisted a future spawn that would have worked

[Cypher]

GUIDs are highly volatile. Don't use them for permanent blacklisting, ever.

Blacklisting by location would be the best way if you want to blacklist an individual node.