Logging matches without setting a placement SR #95
Comments
Hmm, I like the approach my buddy Rob took to start using Competiwatch mid-season: just log your current SR as your placement SR and go from there; he explains this in his tutorial video. I could rename 'Log placement SR' to something more open-ended that encourages this usage, like 'Log starting SR' or even 'Log SR'.
Can you clarify what you mean? Are you saying after you've finished your ten placements, you went to 'Log placement SR' and put the SR where you placed, then wanted to log the ten placements individually? The idea is to either log them individually as you go, or if you don't intend to log any placements, log only the placement SR.
❤️ I'm glad you like it! |
Essentially I took the following steps:
Essentially, I wanted to add my placement matches after I'd set my placement SR but I'm not able to because the option is no longer available once I set my placement SR. Does that make sense? |
Oh! Yeah, that makes sense. I think you could go to the edit page (via clicking the pencil icon) for the placement SR line and click 'Delete match', then log your placements individually. However, I haven't tested doing this after you've logged some regular matches in the season, so I'm not sure if it would mess something up. I'll try this out and make sure it can be done smoothly. |
I just tested a local version of the app.
So right now it'll add placement matches after normal matches if they're added in that order. For comparison here's my table on live: |
I happened to have a screenshot of my placement SR for Season 9, but if I hadn't I wouldn't be able to add matches.
For people that start using the site mid-season, it's not really possible to start tracking matches since currently only "Log placement match" and "Log placement SR" are available.
Similarly, if you input your Placement Match SR you're unable to add placement matches, as only "Log a match" is available (should this be a separate issue?).
This is a really neat tool, thanks for making it! :)
The text was updated successfully, but these errors were encountered: