It’s annoying to extend the intel page with new features because the minified code makes it hard to grasp what’s going on. Also, one has to play catch up each time Niantic put up a new version because all the variables might get new names.
So instead, here’s a userscript that starts from scratch (click to zoom):
You already know you want it, why add a feature list here? Instead, read the user guide for tricks and less obvious features. If you have questions, the user guide will also likely answer them.
IITC can be extended with the use of plugins, so have a look at those if you want (or need) more.
Current version is 0.7.7. See NEWS.md for details.
- Install Greasemonkey or Scriptish.
- Click install link: install
- Confirm security question.
- Reload page.
NoScript: To make the script work whitelist at least these domains: ingress.com github.com leafletjs.com googleapis.com. If you want to see the cool font also whitelist googleusercontent.com.
- Install Tampermonkey.
- Click install link: install
- Now beware: a OK/cancel dialog pops up. It does not allow you to cancel the installation. Choose OK to install the script with Tampermonkey.
- Confirm once again.
- Reload page.
NOTE: You still need to manually update IITC with Tampermonkey. There is a bug in the current stable release. It has been fixed in Tampermonkey’s development version. Until it is released, you need to manually update IITC.
Note: Tampermonkey is optional. However, it offers auto-update, shows correct version numbers and installing user scripts is much easier. If you have installed the scripts directly into Chrome before, I recommend you switch to Tampermonkey. To do so, uninstall the IITC scripts and click each install link again. Follow the procedure explained above.
- Download the script: download
- put it into your user_js folder (that’s
~/.opera/user_json Unix). If you can’t find it see Opera’s docs. - reload the page
Note: You need to update the scripts manually.
tutorial / guide / please read / free candy
First of all, it’s very nice you want to help. There are several equally important ways you can. Some require a technical background and some don’t:
- answering help requests: often people are asking how to do specific things in bug reports or are asking for things that already exist. Kindly point them to what they’re looking for and maybe consider updating the user guide, if it lacks on that topic.
- asking for more information: Sometimes a bug report contains barely enough information to grasp what’s going on. Ask the reporter for the parts that you believe might be helpful, like the browser used. Similarily, if someone requests a feature make sure the description is accurate. Depending on the request, a concrete proposal on how to display this to the user might be helpful.
- finding bugs / regressions: If you are closer to the development of IITC, it’s usually easier for you to spot misbehaviours or bugs that have been recently introduces. Opening tickets for those, ideally with a step by step guide to reproduce the issue is very helpful.
- hacking / sending patches: Of course, if you want to contribute source code to the project that’s fine as well. Please read HACKING.md for details.
So far, these people have contributed:
Bananeweizen, blakjakau, boombuler, cmrn, epf, integ3r, j16sdiz, JasonMillward, jonatkins, Merovius, mledoze, OshiHidra, phoenixsong6, Pirozek, saithis, Scrool, sorgo, tpenner, vita10gy, Xelio, ZauberNerd
This project is licensed under the permissive ISC license. Parts imported from other projects remain under their respective licenses:
- autolink-js by Bryan Woods; MIT
- load.js by Chris O'Hara; MIT
- leaflet.js; custom license (but appears free)
- leaflet.draw.js; by jacobtoye; MIT
leaflet_google.jsby Pavel Shramov; same as Leaftlet (modified, though)- jquery.qrcode.js by Jerome Etienne; MIT
- StackOverflow-CopyPasta is attributed in the source; CC-Wiki
- all Ingress/Niantic related stuff obviously remains non-free and is still copyrighted by Niantic/Google