What your asking for is timelinted caching. A specific number of caches (of different types) for a number of months. It doesn't matter if it's 7 caches per month or 700 caches per month. Quote Time-limited caching: as in some number of finds per day, week, month, or year. Examples: Busy Day, 50 finds in a day, 500 finds in a month, etc.by Matoran_Balta - ARCHIVE Checker requests (completed)
The concept you describe doesn't follow the guidelines so this sounds like a misunderstanding with your reviewer.by Matoran_Balta - ARCHIVE Checker requests (completed)
Well, that depends on what you feel that the problem is. If the challenge get published, its of course multiple people that caused that to happen. If I have to review and deny something that is clearly not allowed under the public guidelines because CO didnt bother to read them and just cloned something they think sounded cool, well... I dont feel that I as a revier could have done anything to avby Matoran_Balta - Miscellaneous
An other solution I could see, but that will bring more work to the volunteer scriptwriters, is of course to only let them clone tags of challenges and no other users. I dont really think it is a good solution, but it is something that would be very effective atleast.by Matoran_Balta - Miscellaneous
For example: This challenge could not be published today since it has two conditions that are very clear in the guidelines as not okay: https://project-gc.com/Challenges/GC13JHC/2339 Its a big red no on: "These cache page elements: cache titles, cache owner, GC Codes, publishing Reviewer, or cache page text." and "Restrictions on date of finds used for the challenge are notby Matoran_Balta - Miscellaneous
Well, a forum still does nothing for helping with the problem that cachers clone non-complying checkers without ever asking in the forum or talking to a moderator or scriptwriter, right? So it does not solve the problem that this thread is about... :)by Matoran_Balta - Miscellaneous
Well, a reviewer/scriptwriters-forum is not a bad idea, but I dont think it have that much to do with the actual topic. The topic posted by Rikitan is a sugesstion to block cloning of old non-complying challengecheckers, something that would be greatly appreciated from the reviewercommunity. Sure, the sugessted forum would also be a nice "tool" to have so to speak, but it would in nby Matoran_Balta - Miscellaneous
This would be much appreciated from the reviewer community! Having no idea how hard/easy this is to set up from Project-GCs perspective so this might be something that is not needed, but if it is hard because it can not be done automatically in an easy way I would suggest something like the voting system for the list of challenge checker exceptions and giving all the reviewers voting access inby Matoran_Balta - Miscellaneous