TX-Loader

5 merged pull requests.

Changes

#19 Moved resource injection point to occur immediately before user resource packs are applied. Replaced all File APIs with Path equivalents in Asset, ConfigHandler, MinecraftHook, RemoteHandler, ServerLangHelper, TXLoaderCore, and TXResourcePack classes. - @glowredman

#21 Added directory creation logic to ConfigHandler asset copying. Fixed RemoteHandler to use Files.walk() for recursive directory traversal instead of non-recursive Files.list(), restoring ResourceLoader compat. - @glowredman
- Fixed: Asset copy failures when target directory structure missing, ResourceLoader compatibility broken by Path migration

#29 TXResourcePack now pre-indexes all existing files into a Set and uses cheap .contains() checks instead of repeated File.exists() calls during resource lookup. - @boubou19
- Added: TX resource index built at pack startup
#23 TXResourcePack.resourceExists uses File.exists on the path's File instead of Files.exists, which was slower. - @tiffit
#18 Reworks RemoteHandler, JarHandler and TXLoaderCore to use thread pools and CompletableFuture, with on-demand indexing and caching of metadata files as well as jars. Asset version no longer defaults to the latest release but to a fixed 26.2, AssetBuilder takes a version and add() now calls fetch(), which returns a future. Pool sizes, keepalive and timeouts are set with JVM arguments listed in the README. - @glowredman
- Added: JVM arguments for thread pool size, keepalive and timeouts, AssetBuilder fetch method returning a CompletableFuture, metadata file caching
- Removed: default of the latest release for asset version, BetterLoadingScreen compile dependency

Everyone who authored, reviewed or co-authored a change on this page, with how many of them: