Abracadabra

Abracadabra

Sounds like 8a.nu is for you.

But then why is fell/hung an option?

Why are you worried about how other people are using the tick function? Who cares? If people want to use it as a log that's fine, it has no impact on how you choose to use the tick function 

I use my ticks more to record my experiences and climbs i’ve gotten on for future returns, and my goldfish memory.

That said, it would be cool to have a “hide fell/hung” on the profile page to see only what i’ve sent. 

Seems like a very strange thing to care about. I tick attempts because I find it far more interesting and valuable to be able to go back and see a history of, more or less, everything I’ve ever climbed outside. Short of adhering to an archaic spirit of the term, I see no benefit to only ticking sends, aside from having the data visualizations served to you directly on the account page. A few minutes in Excel can get me the same visualizations, so why not track everything online?

I track multiple attempts on a climb via adding one tick for the day, then adjusting the pitch count to reflect the number of separate tie ins. So for example, if I fall on an onsight attempt, fall on the second go, then send on the third, I tick Lead - Redpoint (3 pitches). I settled on this format years ago. I find it’s a nice balance between not polluting the tick page with dozens of separate Lead - Fell/Hung entries, while also allowing me to keep a history of how many attempts I have on an individual climb. This makes the concept of a ‘tick’ for me personally more analogous to ‘number of sessions on this climb’. This is certainly not the traditional definition of the word, but as stated above I don’t care. I don’t claim this to be the best system, but it works for me.

I do think that the tick display could be changed to better handle multiple ticks by the same person, especially if they’re all in the same day. As referenced earlier, I do think that adding a separate tick for each individual attempt can make the list appear ‘noisy’, however I think that this is more of a data display issue than anything. A few remediations come to mind, but I think the simplest is this: If a person has multiple ticks on a climb, only show the most recent in the tick display. There could be some text that indicates the number of additional ticks they have on the climb. For example, with this change, the red strike through ticks wouldn’t be shown:

tldr ticking attempts is counterculture to climbing norms brah

I’ll put myself on blast.

Where’s my gold star? Putting in my request to start collapsing multiple entries from a single user into an expandable list for the 6th time like how Mountain Project used to do it. Sometimes I feel bad for clogging pages with attempts but then I remember that:

1. I like it
2. No further questions your honor

Cory B—I suppose it means I care since I posted this. It's a simple suggestion for a simple improvement: a separate list where folks can log route attempts instead of actual ascents of a route per the agreed-upon rules of route completion.  MP has always had a clean, user-friendly interface, and my concern is that an ever-expanding tick list awash with every attempt made on the route will become a chaotic mess. I disagree that it doesn't impact how people use the tick function if I have to sift through an ever-growing list of attempts to glean who did the route.

jakobiwrote:

I disagree that it doesn't impact how people use the tick function if I have to sift through an ever-growing list of attempts to glean who did the route.

Just use Command + F to search the tick list if you are looking for someone specific

jakobiwrote:

Cory B—I suppose it means I care since I posted this. It's a simple suggestion for a simple improvement: a separate list where folks can log route attempts instead of actual ascents of a route per the agreed-upon rules of route completion.  MP has always had a clean, user-friendly interface, and my concern is that an ever-expanding tick list awash with every attempt made on the route will become a chaotic mess. I disagree that it doesn't impact how people use the tick function if I have to sift through an ever-growing list of attempts to glean who did the route.

The disparaging title of your thread post would seem to indicate that your issue is beyond "a simple suggestion" Other people prefer to use the tick function as a log, you don't like that. The system can't be everything to everyone.  The current tick list does have a hang/fell, follow, TR etc. option already. A separate list for just redpoint sends is unneeded in my view.

jakobiwrote:

I disagree that it doesn't impact how people use the tick function if I have to sift through an ever-growing list of attempts to glean who did the route.

I'm sure there's a reason that I haven't thought of, but why do you need to see who has done the route vs who has attempted it? Genuine question. I'm sure we are just using the site in different ways. I've never needed to check to see who has ticked a route so it's not really clicking for me why this is important.