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
Optional autoload extensions #1718
Conversation
What is your use case where those extensions cause you trouble? Some extensions provide passive game fixes like fixing precaching issues in |
The game support extensions are actually autoloaded by core explicitly: Lines 477 to 484 in c3e6428
|
Just make them as optinal. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not being able to load more than X extensions seems to be a bug, could you file a bug with as much info about that as you can please?
Adding the AUTOLOAD_EXTENSIONS
guard for clientprefs seems fine, eventhough the clientprefs plugin strongly depends on the extension, so if you have that plugin loaded the extension will be loaded anyways. Since the game extensions are autoloaded automatically as asherkin pointed out, adding the guard to the cstrike and tf2 includes does nothing. Could you switch this up to only change the clientprefs include file, please?
The problem has nothing to do with the extension itself, but the 40th cannot be loaded. |
* Optional autoload extensions * revert autoload for cstrike/tf2
sometimes, we don't need auto load that extension.