Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simulate shield destruction #33

Open
tonyndory opened this issue Jun 19, 2013 · 11 comments
Open

Simulate shield destruction #33

tonyndory opened this issue Jun 19, 2013 · 11 comments
Assignees

Comments

@tonyndory
Copy link

When attacking a portal in game, there is a chance of destroying the shields with each XMP used. Is it possible to incorporate this into the simulator? Testing would need to be done to discover the percentage chance bursters have for destroying shields, but this would be incredibly useful.

@ghost ghost assigned xosofox Jun 20, 2013
@xosofox
Copy link
Owner

xosofox commented Jun 20, 2013

Gathering data like hell to find out what is the logic behind...

@tonyndory
Copy link
Author

May I assist? It feels like a 10% chance with L6s from the edge.
On Jun 20, 2013 3:27 AM, "Peter Dietrich" [email protected] wrote:

Gathering data like hell to find out what is the logic behind...


Reply to this email directly or view it on GitHubhttps://github.com//issues/33#issuecomment-19734911
.

@xosofox
Copy link
Owner

xosofox commented Jun 26, 2013

"It feels like" is unfortunately not really enough. I need to find a way to
really graph it and deduce a percentage...

2013/6/20 tonyndory [email protected]

May I assist? It feels like a 10% chance with L6s from the edge.
On Jun 20, 2013 3:27 AM, "Peter Dietrich" [email protected]
wrote:

Gathering data like hell to find out what is the logic behind...


Reply to this email directly or view it on GitHub<
https://github.com/Xosofox/IPAS/issues/33#issuecomment-19734911>
.


Reply to this email directly or view it on GitHubhttps://github.com//issues/33#issuecomment-19750073
.

@tonyndory
Copy link
Author

I will try to record some data.
On Jun 26, 2013 7:25 AM, "Peter Dietrich" [email protected] wrote:

"It feels like" is unfortunately not really enough. I need to find a way
to
really graph it and deduce a percentage...

2013/6/20 tonyndory [email protected]

May I assist? It feels like a 10% chance with L6s from the edge.
On Jun 20, 2013 3:27 AM, "Peter Dietrich" [email protected]
wrote:

Gathering data like hell to find out what is the logic behind...


Reply to this email directly or view it on GitHub<
https://github.com/Xosofox/IPAS/issues/33#issuecomment-19734911>
.


Reply to this email directly or view it on GitHub<
https://github.com/Xosofox/IPAS/issues/33#issuecomment-19750073>
.


Reply to this email directly or view it on GitHubhttps://github.com//issues/33#issuecomment-20040634
.

@Hackswell
Copy link

Any progress on data collection for XMPs and US?

@tonyndory
Copy link
Author

No, I have basically been using my subjective experience as my guide.
On Apr 1, 2015 9:53 AM, "Sir Woody Hackswell" [email protected]
wrote:

Any progress on data collection for XMPs and US?


Reply to this email directly or view it on GitHub
#33 (comment).

@Hackswell
Copy link

Xosofox, how does one get accurate numbers in order to help you with this?

@xosofox
Copy link
Owner

xosofox commented Jun 9, 2015

The only "reliable" way is to intercept the traffic between client and
server and store and then evaluate the results - which of course nobody
would do as this most likely violates the ToS

2015-04-01 19:00 GMT+02:00 Sir Woody Hackswell [email protected]:

Xosofox, how does one get accurate numbers in order to help you with this?


Reply to this email directly or view it on GitHub
#33 (comment).

@lablua
Copy link

lablua commented Jun 9, 2015

It's really not that hard to do - configure your Android device to talk to a common SSL MITM proxy like Charles, and you can spy on the client/server communication. It'll somewhat increase your server lag, but otherwise have no negative effects.

I'm not sure it would violate the ToS - at least reading it, I cannot see any paragraph it would clearly violate, but IANAL. It doesn't seem like the needed information is within the definition of "Content", but if it is then you would run afoul of paragraph 2(d).

Paragraph 2(c) is hard to say either way, as it is phrased so broadly one could argue Project Loon is the only compliant way to use Ingress, since all the cell networks involve access through technology not provided by Google. I don't see how using a proxy server you own is any worse than using your own wifi hotspot.

@xosofox
Copy link
Owner

xosofox commented Jun 9, 2015

It's really not that hard to do
I never said it would be. Collecting the data is not the problem if you have time and determination.

But reverse-engineering the algorithm that calculates the shield-pop-probability is another story

@lablua
Copy link

lablua commented Jun 9, 2015

Hard to know how tough that is until you have the data, and run it through some statistical analysis. Unless someone has tried and failed, we just don't know. If they have, I'd like to see the anonymized data published so more people can try to analyze it.

It could be a simple probability calculated in an obvious manner from the "stickiness" property of a shield, or it could be something far more complex like shields accumulating damage over the lifetime the mod is on the portal. If it's the former, a few hundred samples per weapon and shield combination could be enough to figure it out. If it's the latter, it might require controlled experiments with viruses and multiple agents firing to get the necessary data.

P.S. I did try collecting the data myself manually for awhile, but I discovered I'm a little too lazy to write it down often enough to be useful, and then they changed the stickiness rules in the middle of my data collection, so I gave up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants