Agent Science Log

When Ingress first came out, agents around the world had to figure out its features themselves. Over time, that led to the community amassing a sizable amount of knowledge concerning the mechanics of the game. However, I find that there are some questions that are still unanswered. My list can be found below, but I want to know what questions you all have. Hopefully, getting all the questions in one place will allow us to design experiments that will help us find the answers.

My Quesions:

  • Do inbound links provide damage mitigation, or is it just outbound links?
  • Can two ito-ens be applied to the same portal if they have opposite spins? What would happen if they could?
  • how are 24 hour cycles counted in terms of sojourner streaks and hack streaks?
  • Does link crossing still exist, and does it violate TOS?

Comments

  • LynoocsLynoocs ✭✭✭

    1. Both inbound and outbound links provide mitigation

    2. You can apply the + and - spin mods at the same time, they cancel out each other and the resulting spin is 0 (like a portal without these mods)

    3. hack streaks is based on local time, so you can get 2 days quickly if you do it before and after midnight. Sojourner is mostly cooldown based (a 24h countdown resets each time you hack), but it's widwly recommended to hack twice a day

    4. Link crossing is still a thing, but rare due to timing. It's not punishable, but good luck trying to do it

  • Sojourner is based on the time your first-ever portal hack. So if you did your first hack at 9.48, Sojourner will increment at that time every day.

  • HosetteHosette ✭✭✭✭✭

    @saarstahl First hack, first sojourner hack, or first hack of the current streak?

  • This is actually really helpful! I’m also wondering if it’s possible to use link crossing to break Homogenous fielding records. Recently, an H12 field was made using collocated portals. With link crossing, it’s possible to reduce the ratio of portals:fields, perhaps allowing one to bypass the softbank-enhanced outbound link limit. It would probably take a graph theorist to come up with a general theory, but it could be possible!

  • liyu1liyu1 ✭✭✭

    should be the time of the first hack of ur current streak, if u lost ur previous streak.

  • LcfpLcfp ✭✭
    edited July 5

    You are indeed correct! Crosslinks are absolutely awesome!

    On paper it's way easier than you might think: to make a HCFn (where "n" is the level of homogeneity) you just need a triangle (3 portals) with n-1 portals within. Each of the internal portals should be linked to the three vertices, but not linked to each other. The placement of the internal portals is not important for achieving homogeneity, but is important because it dictates how many links cross each other and thus how many people you need for making the whole field.

    What I just described is the maximal use of crosslinks in HCfs (i.e. minimal number of portals needed (without colocated portals)), but you can also create "standard" HCFs with some links which are crosslinks.

    Moreover crosslinks may also be used if you can't find a suitable collection of portals to build an HCF (e.g. imagine spending hours planning a H6 in your town just to discover that a single portal is out of place).

  • Right, but remember that the code only allows for 2 fields to be created per link. Meaning that certain linking sequences will create null fields. Currently, I dont know how to predict which fields will be null. Anyone know how?

  • The largest field on each side will be made, all smaller ones will be null

  • LcfpLcfp ✭✭
    edited July 6

    Regarding the first type of HCFs with crosslinks that I described, only the links in the outer triangle could create null-fields. To be sure to avoid null-fields you can just create the outer field first, and then (cross)link all the internal portals from the vertices of the outer field.

  • What i meant was that certain linking orders would create more than 2 fields when certain links were thrown, which would lead to the creation of null fields due to this two-field-per-link limit.

  • LcfpLcfp ✭✭
    edited July 7

    I understood what you meant, and I'm saying that, with the first configuration described in my post, if you create the outer field first then you are guaranteed to not create null-fields in the successive steps of the linking order, regardless of the actual order.

    The three outer links (the "perimeter" of the HCF) are the only links which are part of more than two fields, and thus they are the only links which are at risk of creating null-fields. Creating them first avoids this problem.

    Remember that internal portals are NOT linked to each other, and thus any "internal link" (i.e. a link between one of the three vertices and one of the internal portals) is part of at most two fields.

Sign In or Register to comment.