Showing Posts For pushpayload.6843:

Character build endpoint update time

in API Development

Posted by: pushpayload.6843

pushpayload.6843

Well that would be ideal yeah. The MumbleLink API was built into the client by ArenaNet and is AFAIK the only allowed way to do memory reading.

Right now I have to rely on the REST API for gear but it would be ideal if they put it in the ‘allowed’ region of memory. There would be nothing dubious about using that to get character state, and definitely no grounds to ban an account as they control exactly what they put in there.

Health bars are an entirely different story as they are part of ‘active’ combat data and could definitely give you an advantage over players not having it, and the entire point of the big health bars as I saw them was to see your party members health/GotL not just your own.

Character build endpoint update time

in API Development

Posted by: pushpayload.6843

pushpayload.6843

@Artemis I’m currently working on pretty much exactly what you explained in your user stories.

On the client side its a c# app that uses the MumbleLink API to find your current char and worldId and if you have input your own API key it will show you other users on that worldId that have done the same (meaning if you are in a raid instance you will see your squad members). As I’m not entirely confident a name searchable list would be preferable for privacy related issues.

There is a server component that caches the data and due to rate limiting I’m looking into letting the client pull its own build info and have it push it to the server to save on calls instead.

It would be nice if there was a “last updated” variable or something added to the character API so you know how accurate/recent the build you are getting is. Because as Artemis said the update is really slow.

The ideal option for real time ToS compliant gear checking would be if it was added to the MumbleLink API then you could just pull it from the gw2 client real time with no load on the API whatsoever.