ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Ingress Help: Tips and tricks

Updated on June 14, 2014

Basic Ingress strategy, learning the ropes

Ingress is a pretty daunting game to play when you first start, and some hints on the finer points of playing would have gone a long way into playing and being successful much easier for me. These are some very basic points that a LOT of people miss when they first start playing Ingress.

I am going to share with you how to improve your ability to deploy resonators and how and where to fire your XMPs for maximum effectiveness.

Keep reading!

Deploying resonators

How to deploy your resonators to make them harder to destroy

When you are deploying resonators, you can choose which slot they appear on by simply tapping the slot and then "deploy." Some people will simply tap "deploy, deploy, deploy" and get it done with quickly. But if you take just a little care, you can make your portals just a little bit tougher to destroy.

Place your highest level resonators on OPPOSITE sides of the portal. This will help diminish the power of XMPs that are fired by the enemy, and increase the longevity of your portal somewhat.

Consider deploying your resonators so they are harder to get close to, like in the middle of a pond, or on the other side of a fence or natural obstacle. Your opponent will be able to hit them, but he won't be able to stand on top of them. This will lessen the amount of damage he can do per shot.

Firing XMPs

The corollary to the above tip when placing resonators, is that firing XMPs is also location based. An XMP does the most damage at ground zero, where you fire it, then weakens as it expands. When you first start attacking a portal, attempt to stand on top of or close to the highest level resonator and fire from there. Try to move at least two spots away, or even opposite the strongest resonator and work that one down.

To state this a different way, start firing your XMPs at the 12 o'clock position, then move to 3,6, or 9 o'clock position (depending on where the strongest resonators are). Continue moving until you have destroyed the portal. You can take down much higher level portals fairly easily if you pay attention to when and how you are firing your XMPs.

The effects will trickle down and allow you to conserve XMPs, increasing your overall effectiveness.

Placing Resonators

Right now, Ingress is a very offensive sort of game. That is, being aggressive and destroying enemy control fields is the best way to be successful, overall. Destroying links and control fields is fairly easy.

However, a lot of people deploy their resonators clumped together, of making it too easy for the enemy team to destroy portals.

One of the biggest mistakes I made when I first started playing is that I deployed my resonators too close together. This makes them easier to destroy with XMPs. By spreading out your resonators, your opponent will have to fire more XMPs to destroy them.

How do you control the distance of the resonators to the portal? By how far away you are from the portal when you deploy them.

If you look at your scanner, if you move such that the portal is just inside the yellow circle, then deploy a resonator, you will see a resonator appear that is the same distance as you are from the portal appear.

If you are closer to the portal when you deploy the resonator, your resonator will appear closer to the portal (imagine that).

A cluster of resonators around a portal is very easy to destroy, because XMPs deal maximum damage where they are fired, and get weaker as they spread.

I never realized there was a book series for Ingress

Building links and control fields

When you first start out, you will be tempted to create as many links as possible. It actually pays to make lots of smaller links and control fields instead of much larger links.

1st - You get the same amount of AP for a large control field as a small one. Lots of small control fields will be easier to make that lots of larger control fields.

2nd - Lots of small control fields are more difficult to take down than larger control fields.

3rd - Large control fields are easier to spot, and quickly become a target by the enemy. They don't generally last longer.

4th - Making larger control fields will require more time and effort.

How to get a 20% more powerful XMP

The final tip I will share is how to increase the power for your XMPs by 20% every time. I didn't really understand this at first, and accidentally stumbled upon it, then questioned a senior player, who explained it to me.

When you are firing an XMP, HOLD DOWN THE FIRE BUTTON. You will see a mass of motes moving towards your position indicator (the blue arrow). Keep holding that fire button down and release when the motes are nearest to the smallest point on your scanner (before they reset and are a large circle again).

This will increase the power of your XMPs stepwise, from 1% at the least amount (and largest circle) up to 20% (at smallest point) if you time it just right.

Please share it below. I have found these tips over my time playing Ingress, but I am sure there are more. I would love to hear from you!

Do you have a tip or trick to share?

    0 of 8192 characters used
    Post Comment

    • Hairdresser007 profile image

      James Jordan 

      4 years ago from Burbank, CA

      I love ingress it is so fun!

    working

    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://hubpages.com/privacy-policy#gdpr

    Show Details
    Necessary
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
    Features
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Marketing
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Statistics
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)