Русские капсулиры · Versión en Español
If you live in New Eden, you are probably used to having to alt+tab to web-based tools nearly every time you play. These tools are part of what makes playing EVE Online unlike any other game. However, it also ruins the immersion of the beautiful world CCP built.
EveVision is a EULA-legal way to extend the UI of EVE Online, bringing the tools you love directly into the game client.
In the near future, there will be a system allowing you to pick and choose (or develop!) plugins much like apps on your phone, complete with Android-style permissions for accessing your ESI data and EULA-legal-to-read files. You will be able to install and run anyone's tools while feeling safe about your computer and character's data.
Need help using or developing EveVision? Have a suggestion or want to show off how you're using it? Join our Discord channel!
Tool Explorer
EveEye and Thera Maps
EveMarketer
Google Translator
Abyssal Markets
D-Scan and Dotlan
There is no complex setup process. Simply download the latest EXE from the releases page, run it once and forget about it. If you would like to build it yourself instead, it is quite simple to do so.
Make sure you have DirectX 9 disabled in launcher settings. Log into EVE and play as you normally would - the rest will come naturally to you. If there is a new version available, it will let you know. There is a custom welcome screen for most major alliances!
If you are ever on an official CCP website (i.e. for ESI authentication) the window will flash green all the way to the edge of the window as shown below
To shut down EveVision, simply select Quit from the tray menu where you change your volume and network settings in Windows.
Assuming you've got node, python, yarn, and VS2019 build tools installed:
git clone git@github.com:/evevision/evevision.git
cd evevision
yarn ez:package # OR yarn ez:dev to run in development mode!
Read the rest of the README for more info.
You can donate ISK to the character EveVision ingame!
Patreon donators get their character name in the EveVision credits forever! I will put it towards paying for my development tools, the various services that EveVision utilizes, and probably PLEX because I'm a credit card warrior.
EveVision is very new and uses some techniques that easily conflict with other software. If you don't see the overlay ingame, you probably have some software installed that somehow interacts with the EVE client too.
Currently known conflicts:
- RivaTuner Statistics Server
- MSI Afterburner (if running RivaTuner)
- FRAPS
- On very rare occasion, Windows Defender
Confirmed to work:
- EVE-O Preview (you can even see EveVision windows in the previews!)
We want to hear about conflicts so we can fix them! Please, if you can't seem to get EveVision to work, join our Discord channel and help us figure out what it might be.
EveVision Core is as EULA legal as your Mumble overlay. CCP commented on this type of tool years ago: https://www.eveonline.com/article/overlays-isk-buyer-amnesty-and-account-security
We may, in our discretion, tolerate the use of applications or other software that simply enhance player enjoyment in a way that maintains fair gameplay. AS LONG AS it’s fair to everybody - neither you nor anybody else gets any unfair advantage – we are fine with it.
For instance, the use of programs that provide in-game overlays (Mumble, Teamspeak) is not something we plan to actively police at this time. This is an example of something we do NOT consider unfair, for now. This also includes other in-game overlays which do NOT grant you any unfair advantage. We do not consider it an unfair advantage if you can see who is currently talking in your voice communication tool via the means of an in-game overlay.
Most importantly, showing that this is not limited to Mumble or Teamspeak:
We also do NOT consider it unfair if you use other comfort overlays which do not affect how the game is played. This includes overlays for chat and IM applications, the Steam overlay, and Web-Browser overlays for example.
This tool cannot do anything like read the screen or perform ingame actions automatically (unless via ESI). It solely draws over EVE and intercepts input for the purpose of interacting with the EveVision windows.
However, keep in mind that CCP always retains the final say. They could full well decide in the future that EveVision is too much and should not be allowed - but in its current form there is no risk of a ban. Additionally, unofficial plugins in the future do not fall under this - if they provide an unfair advantage, it is still against the EULA, no matter what.
Want to tinker around and make your own ingame tools for EVE? It is extremely easy to build and run EveVision yourself! Once you're up and running, you'll be able to run a single command and watch your components update in real-time directly ingame as you save your changes, just like regular web development.
Issues and pull requests are reviewed. If you have an idea, hop on Discord and I'll let you know if I would pull it in!
If you plan on building private alliance/corp tools, please be aware that the core of this software is not meant to be modified for separate distribution, and the license prevents you from doing so without releasing the full sourcecode. There will be a plugin system in the very near future that will allow you to securely distribute tools.
EveVision consists of the following components:
- Electron app inside app, with a split codebase for the main and renderer processes.
- Overlay DLL that is injected into the EVE Client's process space at overlay
- Native node module for injecting and communicating with the overlay DLL at app/native.
- FlatBuffer schemas that are used for communication between the DLL and native node module at flatbuffers/schema
If you have never worked with Electron before, the main thing to know is that there is a main process that uses NodeJS and then renderer processes for each window that are Chromium. They have two different sets of code, two different entry points and communicate via Electron's IPC module.
It is the renderer process where web developers will feel most at home, as you are doing nothing more than developing a React app that is loaded by Chromium. This is where the actual UI is, rather than all the window, input, and process management code.
In many ways, the main and renderer processes share the same relationship as the backend and frontend interface of a website.
Note that you can rule out most issues with production and development mode. The only time you need to test packaging the app is when new resource files will be introduced, which shouldn't be happening often.
This application can only be built and run on Windows x64. However, it is extraordinarily easy to do so - no prior Windows development experience is required! I'm primarily a linux dev myself, and Windows repos scare me too. Every single thing is handled for you via yarn scripts.
You will need the following installed:
- Python 2
- Node v12
- Yarn Package Manager
- Visual Studio 2017-2019 Build Tools (you only need C++ Build Tools from installer)
Download the repo by cloning it or getting the ZIP and extracting it to a local directory of your choice.
Run yarn ez:package and a packaged executable will be output to release/EveVision.exe.
All components will be built to ensure the latest code is packaged.
To quickly repackage the app without running any builds, use yarn package or yarn package:fast instead.
Simply run yarn ez:dev
All components will be built beforehand to ensure the latest code is running. To quickly start development mode without running any builds, run yarn start:dev instead. Hot-reloading will be enabled so you can see your changes inside EVE in real time.
To build and run EveVision but without packaging it into an EXE, simply run yarn ez:prod. To quickly run the app without running any builds, use yarn start:prod instead.
If you make any changes to the C++, you need to know a few things:
- You don't necessarily have to shut down EVE before injecting a new version of the overlay. Old versions sit there doing nothing. However, it's usually a good idea.
- After making your changes to the overlay DLL, run
yarn build:cpp:overlay. You don't have to restart EveVision for it to inject the latest DLL. - After making changes to the node native module, run
yarn build:cpp:native-node. You will have to restart EveVision.
All build commands are run beforehand with yarn ez:dev, yarn ez:prod, and yarn ez:package.
This project uses portions of code from and was inspired by https://github.com/hiitiger/gelectron