History

vita10gy 195dc611b2 Weak Portal Plugin

At a glance high level indicator of portals in disrepair. Opacity is
used to denote how much it's hurting. (Bright means needs the most
attention.) Factors in current energy, missing shields, or missing
resonators. Red means it needs attention. Orange means the same thing,
except that it's down at least one resonator.

I realise this is in opposition to game convention where dim == almost
dead, but I tried it that way, and it just made no sense to me to do it
that way. The whole point is a high level way to quickly identify
portals that most need repairing. If opacity isn't done this way your
eyes are most drawn to the portals that least need your attention.

2013-02-12 00:21:49 -06:00

guess-player-levels.user.js

Player level label renamed to minimal player level

2013-02-10 00:22:24 +01:00

README.md

add hooks framework and add hook for portal added (fixes #87 )

2013-02-10 23:07:33 +01:00

show-portal-weakness.user.js

Weak Portal Plugin

2013-02-12 00:21:49 -06:00

README.md

Plugins

Install

Plugins are installed the same way the total conversion script is. Please see there for specific instructions for your browser.

Available Plugins

Guess Player Level looks for the highest placed resonator per player in the current view to guess the player level.

Hacking

Plugins may be developed in the same way as the total conversion script. Plugins may provide features tailored to specific needs and are allowed to change things as they see fit. You can provide them separately oder submit a pull request to have them managed in this repository. There are currently no hooks that allow integration with the main script, but I will add those if the need arises. Simply open a bug report.

You can use the guess player level script as an example to get you started. Just update the names and the part between // PLUGIN START and // PLUGIN END and you should be able to develop your plugin. The other code ensures your plugin is executed after the main script.

If you happen the write general purpose functions for your plugin, consider adding them to the main script instead. For example, if you write a getResoCountFromPortal(details) function it may be very well added to code/portal_info.js.

Available Hooks

Available hooks are documented in the code. Please refer to the boilerplate explanation in hooks.js to see which are available and how to listen for them. If you need additional hooks, open bug reports (preferably with patches attached).