You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 5, 2023. It is now read-only.
What?
If possible, not sure if SquadJS records the data necessary, but it would be cool to show wins/losses and the ratio. For some players, that is more important/relevant than KD, particularly those that squad lead or command often.
Details
Wins and losses and ratio for each player.
Issues?
How would you handle players that leave before the end (which represent a significant portion of the playerbase given the game's lengths) ?
Would it be possible to only record the win/loss if the player was present for more than, say, 60% of the match duration?
Also, if possible, I’d suggest requiring a player count for the match to be greater than at least 60 players to count towards the win/loss as you don’t want to count seeding matches.
Great to hear, how do you plan on handling early leaves? Is my first suggestion valid? (count if player was present during x percentage of the match)
How should we do that? (If any ideas)
see above or below the clone from old repo
What?
If possible, not sure if SquadJS records the data necessary, but it would be cool to show wins/losses and the ratio. For some players, that is more important/relevant than KD, particularly those that squad lead or command often.
Details
Wins and losses and ratio for each player.
Issues?
How should we do that? (If any ideas)
see above or below the clone from old repo
This is the clone of this issue;
LeventHAN/SquadStatJS#12
The text was updated successfully, but these errors were encountered: