I’ve put together a pretty basic R script that generates portal attack simulations for Ingress. Ultimately I want to use this to generate some optimal resonator placement strategies for specific scenarios but for now it just generates cool simulation pics.
Grab the code on Github. I’d love a pull request if you have something useful to add. Details on how to use it are provided in the README.
Here are some sample scenarios where the attacker fires 3 level 8 bursters in 2 different firing strategies. The attacker is firing upon what I call a “lazily loaded” portal filled by a single L8 player. That is, a L8 res in the EAST slot, a L7 in NE, L6s in N & NW, L5s in W & SW and L4s in S and SE.
It’s kinda cool to see that the “fire in the center” strategy for L5 and higher bursters isn’t necessarily the best.
Fire straight from the center.
Fire closer to the more powerful resonators.
Nothing fired, just the lazy loading scenario prior to an attack.
I’ve often wondered if I could optimise resonator placement for a portal that sits on a street, prone to drive-bys. The case that came to mind was to put the heavier resonators facing the street (absorbing damage) but also bring them closer to the center, keeping them off the street. In these examples I’ve assumed traffic flows from the west to east, but it doesn’t make a huge difference.
Here’s the “streetside” resonator placement, no attack.
Here’s an attack on the street-side setup. Ouch.
Here’s a comparative attack on a standard “lazy” fill. There’s 27% more damage done in the street-side “optimised” scenario.