-
Notifications
You must be signed in to change notification settings - Fork 11
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
1.20.4 support #15
Comments
If it's not working for you, could you please post a log/crash report? |
@kb-1000 1.20.2 was working for me, however 1.20.4 doesn't start with:
It throws the 255 Exit Code with this error:
|
Minecraft 1.20.3 seems to have changed the way telemetry is disabled in dev builds.
private TelemetrySender computeSender() {
if (!this.client.isTelemetryEnabledByApi()) {
return TelemetrySender.NOOP;
}
...
} I believe the new mixin should be: @Mixin(targets = "net.minecraft.client.session.telemetry.TelemetryManager")
@Environment(EnvType.CLIENT)
public class TelemetryManagerMixin {
@Redirect(method = "Lnet/minecraft/client/session/telemetry/TelemetryManager;computeSender", at = @At(value = "INVOKE", target = "Lnet/minecraft/client/MinecraftClient;isTelemetryEnabledByApi()Z"), remap = true)
private boolean disableTelemetrySession(MinecraftClient instance) {
return false;
}
} I am not quite sure how to integrate this into the current system with the pre and post mixins, so leaving this as a comment instead of a PR for @kb-1000 |
The pre/post mixin split right now is because mojmap changed the package of TelemetryManager in 1.19.3, which breaks binary compatibility on Forge so I need a second mixin class to make a separate refmap entry. |
Is this getting a release tag on git or a publishing on modrinth etc? For now it can be installed from the workflow build: https://github.com/kb-1000/no-telemetry/actions/runs/7172504788 |
I was looking into adding NeoForge support as well before releasing 1.8.0, but maybe I should drop that idea for now. |
No description provided.
The text was updated successfully, but these errors were encountered: