Links
Tags
Creators
Details
1.0.1
Compatibility
Changes
This release adds new error-handling features, improves mod compatibility, and fixes several bugs introduced in previous versions and release candidates.
New Features:
- The client can now ignore custom feature flags when connecting to a vanilla server (fixes: #1) (introduced in v1.0.1-rc1)
- The client can now ignore packet decoding errors when connecting to a server (fixes: #1 (comment 3011626189)) (introduced in v1.0.1-rc2)
- Automated release pipelines for GitHub and Modrinth have been set up (introduced in v1.0.1-rc2)
- The client now ignores packets larger than expected (fixes: #1 (comment 3067088739)) (introduced in v1.0.1-rc6)
- Client side packet handling errors are now ignored when connecting to a vanilla server, allowing the client to connect without issues. (fixes: : #1 (comment 3067399173)) (introduced in v1.0.1-rc7)
Bug Fixes and Changes:
- Patches are now disabled when connecting to NeoForge servers to prevent compatibility issues (introduced in v1.0.1-rc2)
- Fixed all occurrences of the typo "Quite" (should have been "Quiet") across the codebase (introduced in v1.0.1-rc2)
- Fixed a crash caused by invalid access transformer syntax despite Architectury Loom successfully applying the access transformer (fixes: #2) (introduced in v1.0.1-rc3)
- Fixed an issue where
isConnectedToVanillaServerwas not set early enough, causingCheckFeatureFlags.handleVanillaServerConnectionto behave incorrectly (fixes: #1 (comment 3065956489)) (introduced in v1.0.1-rc4) - Improved the implementation for ignoring packet decoding errors to be more robust (properly fixes: #1 (comment 3011626189)) (introduced in v1.0.1-rc5)
NetworkRegistryMixinnow checksClientConfig.bypassCustomFeatureFlags()before callingCheckFeatureFlags.handleVanillaServerConnectionto ensure custom feature flags are ignored when connecting to servers that do not support them (fixes: #1 (comment 3066014192)) (introduced in v1.0.1-rc5)- Renamed
acceptVanillaServertobypassNegotiationErrorsto better reflect its purpose (introduced in v1.0.1-rc7)
Removed Features:
- Unsupported server-side patches have been removed from the Be Quiet Negotiator codebase (introduced in v1.0.1-rc7)
Full Changelog: compare v1.0.0 with v1.0.1
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| be_quiet_negotiator-1.0.1-sources.jar | Unknown | 9.93 KiB |
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:38x4KgoC:XgDkgRhr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:38x4KgoC:XgDkgRhr"
}
