Helium314

I don't know why I haven't thought about this earlier, but: how about option 1 or 3 (might be much more work though) with an additional per-quest parameter that defines...

Implementing 3. would either be some sort of hard-to-discover clickable _never shown in country_ text that opens a setting, or would require "more properly" implemented quest settings, which is much...

> So something like adding override val isCountryRestrictionOverrideEnabled = true to only those quests having enabledInCountries Or a simple `override val enabledInCountries = if (prefs.getBoolean("that override setting", false)) AllCountries else...

You can also add whatever letters you're missing by editing the layout you're using.

If implemented, this change _must_ be customizable. I remember the default settings were seen as not restrictive enough by other people. But instead of having potentially convoluted logic I'd suggest...

> was this seen as not restrictive enough in SC or SCEE? In SCEE, SC doesn't even have that quest.

-7. seems reasonable, but might also require quite a bit of work for documeting how it's used, and probably for a discussion in the OSM forum. -1. could be a...

Just the ability to add user-defined quests would be a lot of effort, considering that the quest list is currently hardcoded in [`QuestsModule`](https://github.com/Helium314/SCEE/blob/modified/app/src/main/java/de/westnordost/streetcomplete/quests/QuestsModule.kt). Customizable quest forms instead of just showing...

I also find it a weird value that requires clarification. See also the [second image on wikipedia](https://en.wikipedia.org/wiki/Patio), which does not work at all with "_A ‘patio’ is an open inner...

I don't think this is possible. A quest form requires an existing/valid quest type or will crash upon creation. Further the answers from a quest form can basically be _anything_,...