Missing operator specific stats about rainbow-six-siege-player-stats-api HOT 17 CLOSED

Operator stats are different from user stats, you can print it by calling getOperators (starts with operatorpvp) and you don't need to know before...

Anyway i have a list used for my project:

ability_operatorpvp_phoneshacked
ability_operatorpvp_attackerdrone_diminishedrealitymode
ability_operatorpvp_caltrop_enemy_affected
ability_operatorpvp_cazador_assist_kill
ability_operatorpvp_tagger_tagdevice_spot
ability_operatorpvp_doc_selfrevive
ability_operatorpvp_doc_hostagerevive
ability_operatorpvp_doc_teammaterevive
ability_operatorpvp_mute_gadgetjammed
ability_operatorpvp_mute_jammerdeployed
ability_operatorpvp_ash_bonfirekill
ability_operatorpvp_ash_bonfirewallbreached
ability_operatorpvp_blackbeard_gunshieldblockdamage
ability_operatorpvp_valkyrie_camdeployed
ability_operatorpvp_dazzler_gadget_detonate
ability_operatorpvp_concussionmine_detonate
ability_operatorpvp_black_mirror_gadget_deployed
ability_operatorpvp_hibana_detonate_projectile
ability_operatorpvp_echo_enemy_sonicburst_affected
ability_operatorpvp_smoke_poisongaskill
ability_operatorpvp_rush_adrenalinerush
ability_operatorpvp_concussiongrenade_detonate
ability_operatorpvp_bandit_batterykill
ability_operatorpvp_caveira_interrogations
ability_operatorpvp_fuze_clusterchargekill
ability_operatorpvp_pulse_heartbeatspot
ability_operatorpvp_pulse_heartbeatassist
ability_operatorpvp_sledge_hammerhole
ability_operatorpvp_sledge_hammerkill
ability_operatorpvp_castle_kevlarbarricadedeployed
ability_operatorpvp_glaz_sniperkill
ability_operatorpvp_glaz_sniperpenetrationkill
ability_operatorpvp_montagne_shieldblockdamage
ability_operatorpvp_iq_gadgetspotbyef
ability_operatorpvp_twitch_shockdronekill
ability_operatorpvp_twitch_gadgetdestroybyshockdrone
ability_operatorpvp_thermite_chargekill
ability_operatorpvp_thermite_chargedeployed
ability_operatorpvp_thermite_reinforcementbreached
ability_operatorpvp_rook_armorboxdeployed
ability_operatorpvp_rook_armortakenourself
ability_operatorpvp_rook_armortakenteammate
ability_operatorpvp_capitao_lethaldartkills
ability_operatorpvp_buck_kill
ability_operatorpvp_frost_dbno
ability_operatorpvp_jager_gadgetdestroybycatcher
ability_operatorpvp_thatcher_gadgetdestroywithemp
ability_operatorpvp_blitz_flashedenemy
ability_operatorpvp_blitz_flashshieldassist
ability_operatorpvp_blitz_flashfollowupkills
ability_operatorpvp_kapkan_boobytrapkill
ability_operatorpvp_kapkan_boobytrapdeployed
ability_operatorpvp_tachanka_turretkill
ability_operatorpvp_deceiver_revealedattackers
ability_operatorpvp_maverick_wallbreached
ability_operatorpvp_clash_sloweddown
ability_operatorpvp_kaid_electroclawelectrify
ability_operatorpvp_nomad_airjabdetonate
ability_operatorpvp_mozzie_droneshacked
ability_operatorpvp_gridlock_traxdeployed
ability_operatorpvp_nokk_observationtooldeceived
ability_operatorpvp_warden_killswithglasses
ability_operatorpvp_goyo_volcandetonate
ability_operatorpvp_amaru_distancereeled
ability_operatorpvp_kali_gadgetdestroywithexplosivelance
ability_operatorpvp_wamai_gadgetdestroybymagnet

Use it with wisdom.

from rainbow-six-siege-player-stats-api.

Thank you very much, that helps a lot. Just out of curiosity: how did you find those keys in the first place?

from rainbow-six-siege-player-stats-api.

If you call api with getOperators method, example:
getOperators.php?name=Sidelux00&platform=uplay&season=12&appcode=xxx

You'll get operator list:
https://pastebin.com/ggAF3f9m

Then you noticed that operatorpvp different from standard stats:
"operatorpvp_smoke_poisongaskill":0

So done ;)

from rainbow-six-siege-player-stats-api.

Even before that though, when the api was first being built. How did you know which keys to add to the request to the Ubisoft api?

from rainbow-six-siege-player-stats-api.

There is an api for that, look at https://github.com/Seems2Legit/Rainbow-Six-Siege-Player-Stats-API/blob/master/UbiAPI.php#L144

from rainbow-six-siege-player-stats-api.

Ooooh that makes sense, thank you very much.

from rainbow-six-siege-player-stats-api.

I just realized that there are some keys that are missing in what you sent, including operatorpvp_tachanka_turretdeployed... Maybe you're missing some more?

from rainbow-six-siege-player-stats-api.

Where do you found that key? Ubi not provide in response :/

from rainbow-six-siege-player-stats-api.

I found it listed in the readme readme link, and I confirmed that the value exists by making a test request to Ubi's api. I'm trying to get as many values as possible for my project, so I'm trying to figure out the best way to get all of the keys.

from rainbow-six-siege-player-stats-api.

Here are the results of my test request: here.

from rainbow-six-siege-player-stats-api.

Uhm maybe Ubi prints it only if param is > 0, should be tested...

from rainbow-six-siege-player-stats-api.

I could test this out now; I have an account that has very few operators.

from rainbow-six-siege-player-stats-api.

I just confirmed this to be true, so the statistic is only returned if the value is not 0. In this case, how can we get every possible statistic?

from rainbow-six-siege-player-stats-api.

I think you can pick a player with very high number of played hours and use it to get all statistics :')

from rainbow-six-siege-player-stats-api.

Smart... Is there a way to get all statistics without having to explicitly set the keys?

from rainbow-six-siege-player-stats-api.

There is something broken... When i make a getOperators call for Pengu i have "operatorpvp_kali_gadgetdestroywithexplosivelance": 0 so is not true that previous assumption about it.

Sincerly idk, Ubi sometimes make some random things we can't understand.

from rainbow-six-siege-player-stats-api.

Weird... I tested it by checking operatorpvp_tachanka_turretdeployed on my main account, and it shows a seemingly correct number, but when I check it with another account of mine that doesn't own Tachanka they key doesn't even show up...

from rainbow-six-siege-player-stats-api.