Cairenn asked them for the Patchnotes. They something about "tomorrow" or so. Chances are we got a not so problematic replacement for it.I could see this one being intentionally eliminated in order to combat botting, but yeah. It'd be nice if they actually said something.
[...]
I am getting in touch with Zenimax to see if we can get some information on the changes to the API. I'll update this as appropriate.
[Edit] Okay, I just heard back from Zenimax and I 'should' have API notes by tomorrow.
I understand they dont want botting but this API function is not really useful for botters either why would botters need NPC X,Y,
Flawed information is flawed. Trust me, botters don't bother using addons. They straight up hack the game and use tools they write themselves that absolutely don't follow any of the rules. Addons are legitimately written pieces of code that use the supplied approved UI API.Ragnar_Lodbrok wrote: »Personally Id have been happy they didnt allow add ons. Add ons were the root cause of all the botting issues for months.
oh add ReticleSettings and ZrMM to the list of addons that used GetMapPlayerPosition('reticleover') like 2 of the BEST and most needed addons out we really got the end of the stick on this patch
i dont think ZrMM really used it tho but still
Specificalyl we cannot move, fire skills, no mouse action, no chat messages.There's nothing TO bot in the API.
I think a core problem is that you try to gather all the data yourself. Lorebooks, Atlas and several similar relied on a dual approach:So I've converted the scanner to a interact works still but you half to interact with said vendor to have it log to the database and pin to the map it's not so much that I half to use player X Y but the fact to get reliable X Y for the Npc location the player has to be as close to the Npc as possible and interact ...where before it was just a reticule by and it loged, really would like to see a dev or CS post something on why it got changed
We got an update now. I think it might be related to the dispaly name issue.TargetX, TargetY, TargetH = GetMapPlayerPosition('reticleover')
can anyone explane what happen to it seem only "player" return position data now as of V1.2.3 if you use 'reticleover' its all 0 0 0
anyone any ideas?
We got an update now. I think it might be related to the dispaly name issue.TargetX, TargetY, TargetH = GetMapPlayerPosition('reticleover')
can anyone explane what happen to it seem only "player" return position data now as of V1.2.3 if you use 'reticleover' its all 0 0 0
anyone any ideas?
If GetMapPlayerPosition() tries to get the position relative to displayName-unit it would make sense that it only returns nul (propably because it cannot find a unit named "").
I now think actually that is more a bug related to the DispalyName issues.We got an update now. I think it might be related to the dispaly name issue.TargetX, TargetY, TargetH = GetMapPlayerPosition('reticleover')
can anyone explane what happen to it seem only "player" return position data now as of V1.2.3 if you use 'reticleover' its all 0 0 0
anyone any ideas?
If GetMapPlayerPosition() tries to get the position relative to displayName-unit it would make sense that it only returns nul (propably because it cannot find a unit named "").
well half to see i think they removed "reticle" for PVP reasons but well see hopefully they get all the fixes in place really quick
ZOS_JessicaFolsom wrote: »can we get an update for :
-TargetX, TargetY, TargetH = GetMapPlayerPosition('reticleover') doesn't return target X,Y is this a bug or intentionally removed?
This was intentionally removed, and there are no current plans to return the functionality.- IsUnitDead('reticleover') , completely broken dead units return nothing, unless transformed into a werewolf??
We're looking into this. As you mentioned, that is not working as intended.- GetDisplayName(), whats happening with this, is it comming monday? like an update as MANY ppl have modified/fixed thier saves and now are loggin new data and will half to fix again...
We're working on a fix for this one, though we don't have an ETA yet.