Cannot change rating range in custom puzzles

Sort:
Avatar of BlueScreenRevenge

Yes, I cleared the cache (I really don't have to, but I did), it did not help. It made it even worse, because after clearing the cache it went to under 200 range (which is probably the default) and now I cannot change it at all, which makes custom puzzles completely useless.

Avatar of jojonoto

Same thing has happened to me. Not sure how to fix it other than reseting my puzzle rating completely

Avatar of categoriaopuesta

Same here

Avatar of DanielPolonsky

Same

Avatar of seawolfcommand

Mine is stuck on 200. It won't let me change it. Chess.com will not respond to inquiry,

Avatar of BlueScreenRevenge
seawolfcommand wrote:

Mine is stuck on 200. It won't let me change it. Chess.com will not respond to inquiry,

You are just a mere paying customer, why would they bother to respond to your inquiry? That would be at odds with their time-tested strategy of disregarding complains of their customers, pretending everything's fine as long as possible, waiting for problems to blow over and only acknowledging something is wrong when the outcry is impossible to ignore.

Way easier to manage your expectations, once you understand this.

Avatar of norm1234567

same

Avatar of celtictiger2020

I'm having the same problem. It started a couple days ago.

Avatar of BlueScreenRevenge

The issue is still there. Anyone who represents chess.com wants to give an update? Is it looked into? Investigated? Payed any attention to at all?

It is about puzzles, one of the basic payed for features of this site.

Avatar of blahblahblah877

Same. Super Annoying, it's a critical practice component

Avatar of categoriaopuesta

I just reported the bug using the help tool. Let's see if it gets to their dev backlog. Will post here if any news. It really makes the custom puzzles useless..

Avatar of blahblahblah877

Also reported it

Avatar of Martin_Stahl

Staff are aware and looking into it.

Avatar of seawolfcommand

My help tools aren't working either.

Avatar of Martin_Stahl

This was fixed as of earlier today.