-
Notifications
You must be signed in to change notification settings - Fork 70
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
feat(match2): properly attach participants to their playerid #4645
Conversation
needs rebase |
95a50dc
to
f7d9cd6
Compare
components/match2/commons/starcraft_starcraft2/match_group_input_starcraft.lua
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need any handling in case we do not find the player id?
(like in sc(2) custom i just append them to match2players)
LGTM modulo the above question
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this completely breaks sc(2) matches with team opponents
- missing data
- keys renamed
- faction processing doesn't work as intended
components/match2/commons/starcraft_starcraft2/match_group_input_starcraft.lua
Outdated
Show resolved
Hide resolved
components/match2/commons/starcraft_starcraft2/match_group_input_starcraft.lua
Outdated
Show resolved
Hide resolved
components/match2/commons/starcraft_starcraft2/match_group_input_starcraft.lua
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is the latest version tested?
i see 1 edge case that gets handled differently on sc(2): TBD player input in maps
currently it would add an tbd player in match2players for each TBD in maps
the new version only does so for the first map (or none at all if there already is a TBD player in match2players)
i think this should not cause any issues though and data wise might even be preferable
overall lgtm if tested
components/match2/commons/starcraft_starcraft2/match_group_input_starcraft.lua
Outdated
Show resolved
Hide resolved
components/match2/commons/starcraft_starcraft2/match_group_input_starcraft.lua
Outdated
Show resolved
Hide resolved
components/match2/commons/starcraft_starcraft2/match_group_input_starcraft.lua
Outdated
Show resolved
Hide resolved
components/match2/commons/starcraft_starcraft2/match_group_input_starcraft.lua
Outdated
Show resolved
Hide resolved
I've tested on dota2 match page, but that's it |
can test on sc2 later today or tomorrow (probably tomorrow) |
components/match2/commons/starcraft_starcraft2/match_group_input_starcraft.lua
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tested on sc2
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
did some more preview tests across the affected wikis
apart form some missing nil checks (see comments) no errors found so far
* matchsummary * a start * add hero stuff * not needed * assume 4608 gets merged * Update match_summary.lua * fix some stuff * fix player ext custom (same as on sc(2)) * linter: break line * fix legacy wrapper for `skip` score input * fix legacy wrapper if an solo opponent has unset name but set faction/flag use TBD as name to display the flag/faction data * legacy wrapper fixes - race , flag, link params - convert skip score to default loss as it seems more fitting according to usage .. * kick unused require * Update match_group_input_custom.lua * the skip shit again * skip fixing * Update match_group_input_custom.lua * Update components/match2/wikis/warcraft/match_group_input_custom.lua * Update components/match2/wikis/warcraft/match_group_input_custom.lua * as per review * use commons * assume maps in legacy matches are finished * Update components/match2/wikis/warcraft/match_group_input_custom.lua Co-authored-by: Rikard Blixt <[email protected]> * fix map handling * bold submatch scores on submatch draw * #4650 * #4645 * kick unused import * missing faction normalization * do it in the correct file...... --------- Co-authored-by: Rikard Blixt <[email protected]>
* ms adjusts * player ext adjusts * input processing * linter: line is too long * as per review in warcraft * from wc review that applies here but not there * double space fix * kick unused function * fix map handling * bold submatch scores on submatch draw * #4650 * #4645 * missing faction normalization * #4752 * Update components/match2/wikis/stormgate/match_group_input_custom.lua Co-authored-by: Rikard Blixt <[email protected]> * Update components/match2/wikis/stormgate/match_group_input_custom.lua Co-authored-by: Rikard Blixt <[email protected]> --------- Co-authored-by: Rikard Blixt <[email protected]>
Summary
Create a common's function to find the
match2playerid
of a player input. Use this function in wikis with refactored MGI'sHow did you test this change?
Some testing by me, some by hjp