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.

Sign up for GitHub

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

Jump to bottom

rangerWhitelist(1) - use new 'whitelist' trace property #3082

Closed
Fasteroid opened this issue Jun 10, 2024 · 4 comments
Closed

rangerWhitelist(1) - use new 'whitelist' trace property #3082

Fasteroid opened this issue Jun 10, 2024 · 4 comments

Comments

@Fasteroid
Copy link
Contributor

When I added this back in #1985, there wasn't really a good way of implementing it, but now as of garrysmod.main/x86-64#9e093b, traces now have a whitelist property that's 1:1 with how this should have been implemented in the beginning. Now that it can be improved, it should be.

Tag this with "enhancement" or whatever, I'm just opening an issue so I get off my ass and fix it later.
@Fasteroid Fasteroid changed the title rangerWhitelist(1) optimizations rangerWhitelist(1) - use new 'whitelist' trace property Jun 10, 2024
@Fasteroid
Copy link
Contributor Author

1 month already, do it dumbass!

@Fasteroid
Copy link
Contributor Author

1 month already, do it dumbass!

okay okay fine, this weekend

@megascan
Copy link

okay okay today it is!

Fasteroid added a commit to Fasteroid/wire that referenced this issue Jul 13, 2024
@Fasteroid
fix rangerwhitelist wiremod#3082
2131449
Fasteroid added a commit to Fasteroid/wire that referenced this issue Jul 13, 2024
@Fasteroid
fix rangerwhitelist wiremod#3082
27cc2d5
@TeeMeeFe
Copy link

today perhaps?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Fasteroid @TeeMeeFe @megascan