Closed macrojames closed 9 years ago
IITC isn't intended to be hard to detect. Our most obvious difference is requesting more entries from COMM than the standard site does, due to our taller window and COMM filtering into separate tabs.
These odd extra parameters come from some daft attempts at request obsfucation in the standard site, where the code adds in extra dummy parameters to every request. Search the standard gen_dashboard.js for nemesis.dashboard.network.DataFetcher.normalizeParamCount
Given the recent set of user bans, where a trusted source has passed on reasons such as "Excessive Intel Use" and "3rd party Intel program" for being banned, I've decided to revisit this.
As of commit 47d453793c95fb1a68c45d800d0dd61ada7c6f97, and test builds dated after 2013-11-24 01:52:00 UTC, things have been changed to follow the standard intel site in request formats.
I'm still comparing the two, seeing if there's other changes that should be made. #656 is also relevant
Is there anything left to do for this issue?
I see different request payloads for stock and iitc. I think this could be an issue.
Please ignore the different tilesets. I have never seen "desiredNumItems" before in getThinnedEntities
Stock:
IITC: