-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ignore access=private for all quests #607
Comments
It's also a lot of work for me (though it seems that less than 100 quests have a private filter), and with questionable benefit. |
Yes, it would seem like too much work and maintenance to me too (unless it was some smart-regexp option which searched for What I'm more worried about is that removing private restrictions should not IMHO apply to all quests. Sure, I can often see Even more problematic are quests like |
Though maybe you know the right people and can thus legally visit some of those locations... But actually I think everything would be fine, as you have to explicitly enable the setting. So you should know that quests can be asked for places you're not allowed to access. |
Use case
I don't really get why the original SC ignores quests for things tagged access=private. In most cases it's e.g. a service road I can already see so I can map the surface and other quests without a problem and without tresspassing.
Proposed Solution
While SCEE allows to edit the overpass query for individual quests, with 216 quest types and counting it has become unfeasible to remove the access=private filters on all of them. It'd be nice if there was a toggle in the settings that did it for all of them simultaneously.
The text was updated successfully, but these errors were encountered: