Are pinEvents triggered when using "FUT Auto Relist Expired Auctions"

[fifa2017player]

Expected behavior:

pinEvents are triggered when you switch between screens and perform certain actions. If I use this script, does it trigger the necessary pinEvents so that the server knows that we aren't relisting automatically?

I was reading this futapi/fut#287 (a separate Python API using the same Web app backend) which says that pinEvents should be triggered so as not to be detected as anomaly.

Current behavior:

This is more of a question, I am not sure whether pinEvents are triggered or not.

Metadata:

• Script name: FUT Auto Relist Unsold Transfers
• Script version:
• Browser:
• OS:

[Mardaneus86]

They are not triggered (yet). I will try to detect when and which pinEvents have to be sent when relisting auctions. Good point.

[debugman5]

I don't see any pinEvents triggered after relisting, only before, when entering the transfer list page

[Mardaneus86]

I've done some research, but didn't implement it yet. Code to be used is:

gPinManager.trigger(utils.PinFactory.createEvent(enums.PIN.EVENT.PAGE_VIEW, {
          type: PinManager.PAGEVIEW_EVT_TYPE,
          pgid: pageId
}));

pageId should be "Hub - Transfers" for the first call to the hub, then "Transfer List - List View" for navigating to the transfer list view.

This will be included in the single script version I'm working on.

[debugman5]

We should also trigger pinEvents when searching for min price, and its more complicated, because it depends in which screen you currently on.

Actually, its also necessary with auto relisting. I mean, lets say you in the club page and now its time to relist: so you first need to send pinEvent with "Hub - Transfers" and then a pinEvent with "Transfer List - List View" and then a pinEvent with "Hub - Club"

Question: is it possible to "click" on the actual buttons? I mean fire the click event

[Mardaneus86]

Yeah, that would be possible when we get the script in 1 single file. Every action could go through a queue so they don't interfere with each other.

It is possible to fake click events. Take a look at https://github.com/martellaj/shortfuts for an example of this.

[debugman5]

Wouldn't it be better to take this approach?

[Mardaneus86]

It's a different approach. If either one is better is open for discussion, but in the end all actions are sent through the communication delegates.

[debugman5]

I think its better in case they will decide to change something in the events

[debugman5]

I tested sending the pinEvents using the method you mentioned above and I noticed a difference between the pinEvents that are sent and the one I sent manually.

I attached two har files: originalPostPinEvent.har representing an original post pin event when entering the transfer search page and manualPostPinEvent.har representing the manual one.

Edit by Mardaneus86: (removed HAR files for security reasons)

[Mardaneus86]

Well that difference is an extra request to remoteConfig.json which might have been caused by another process. The rest is completely the same.

By the way, I've removed those HAR files for you because they contain your personal cookie information!

[debugman5]

So what causing the difference?

And thanks! I forgot to remove them

[Mardaneus86]

Like I said, the remoteConfig.json is called on specific intervals by the app. It has nothing to do with pinEvents. I see no difference for the pinEvents themselves... Please reach out on Gitter to discuss this further if you want to.

[debugman5]

I've joined Gitter

[Mardaneus86]

Fixed in v0.2.2.