Discussion Reading Process Memory

Hi,

i was wondering if it is okay to read process memory of the active game? this would enable tools to be a bit more accurate like for example VA if you say "Target Powerplant" it often fails to target the powerplant. Reading memory would allow to validate certain things a bit more accurately. Things i have interest in knowing include how i currently manage my pips or in which system i am in currently. maybe get some more detailed ship information regarding modules i own etc.

As an explanation to the why: I was planning on making a tool to aid new/older players with engineers. Often you loose track of what you need/have, which modules you want upgraded, in which order to upgrade them while taking distance into consideration and a lot of more things.
 
I believe that it's against the terms of service to read the process memory.

That said, there is a certain amount of information available from a combination of the netlog (soon to be the much more detailed journal) and the companion API. There are details on both in this forum so you might want to read through them to see if they meet your needs (for example, the companion API provides full information on your current modules including engineer upgrades).
 

Slopey

Volunteer Moderator
It is against the T&C and expressly forbidden.

Reading the pilot stat API from the web service (which powers the iOS app) is permitted provided you don't continuously poll (i.e. hammer) it. But memory scraping is not.
 
Back
Top Bottom