In patch 10.2.5 UnitPosition returns an incorrect number of values inside instanced content, resulting in the instanceID return value (at position 4) actually being returned at position 2 in the result list.
In outdoor content in both 10.2.0 and 10.2.5, all four values are returned as expected.
In instanced content in 10.2.0, all four values would be returned, however per API restrictions the first three values would always be nil.
In instanced content in 10.2.5, only two values are returned - a leading nil, followed by instanceID.
This effectively results in UnitPosition having two return signatures based upon whether or not you're in an instance, which breaks any code reliant upon the instanceID return value being 4th in the list.
Meorawr
commented
8 months ago
In patch 10.2.5 UnitPosition returns an incorrect number of values inside instanced content, resulting in the
instanceIDreturn value (at position 4) actually being returned at position 2 in the result list.UnitPosition has the following signature:
nil, followed byinstanceID.This effectively results in UnitPosition having two return signatures based upon whether or not you're in an instance, which breaks any code reliant upon the
instanceIDreturn value being 4th in the list.