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

Allow loading configs from a specified override path #48

Merged
merged 1 commit into from
Dec 12, 2023

Conversation

pupnewfster
Copy link
Member

Use case is to switch NeoForge server configs from being in the serverconfig folder by default to being generated in the config folder, but allowing them to be copy pasted to the serverconfig folder in the cases users want to have per save overrides for certain values.

This PR also simplifies the logic for removing the file watch so that we don't have to determine which location we initially loaded the file from.

@Technici4n Technici4n self-requested a review December 12, 2023 00:15
@Technici4n Technici4n merged commit 19d6326 into neoforged:main Dec 12, 2023
1 check passed
@pupnewfster pupnewfster deleted the better_configs branch December 12, 2023 18:13
shartte pushed a commit that referenced this pull request Dec 22, 2024
In old startup profiles from 1.19/1.20, `ModuleClassLoader` often takes
at least a second or two to be constructed in large modpacks. This
likely boils down to the high amounts of iteration being done over the
module list - in particular, constructing `parentLoaders` would have
O(n^2) runtime in a scenario where every module reads the other modules.

This PR makes some changes to the constructor to avoid redundant
iteration. I have not profiled the changes, but I don't see a reason why
they could be slower than the status quo. In particular, the
`parentLoaders` loop has been heavily optimized to cache data for each
module, which should provide noticeable speedup to the automatic module
case.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants