Skip to content
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

Whether textscreens should have a tool whitelist or a blacklist? #91

Open
stepa2 opened this issue Mar 8, 2024 · 0 comments
Open

Whether textscreens should have a tool whitelist or a blacklist? #91

stepa2 opened this issue Mar 8, 2024 · 0 comments

Comments

@stepa2
Copy link

stepa2 commented Mar 8, 2024

(From discussion in #90.)

Whitelist (current state):

  • Pros:
    • New tools that are affected by ENT:CanTool are unable to break textscreens.
    • Less error reports.
  • Cons:
    • Allows tools that are not affected by ENT:CanTool to break textscreens.
      • E.g. anything with range-selection, like SmartWeld area selection, AdvDupe2 area copy and Multi-Parent area selection, I guess.
    • Disallows all tools that are compatible but not whitelisted.
    • More whitelist extension requests.

Blacklist:

  • Pros:
    • It is possible to block tools that cause errors.
    • New and existing tools that don't break textscreens will be allowed automatically.
  • Cons:
    • More error reports.

Blacklist and whitelist, switchable by convar:

  • Cons:
    • Will cause more error reports and whitelist extension requests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant