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

**READ BEFORE OPENING AN ISSUE** #146

Closed
Roadhog360 opened this issue Jul 8, 2022 · 0 comments
Closed

**READ BEFORE OPENING AN ISSUE** #146

Roadhog360 opened this issue Jul 8, 2022 · 0 comments

Comments

@Roadhog360
Copy link
Owner

Roadhog360 commented Jul 8, 2022

Hello! Due to the large influx of issues that do not use the template, any issue not following the issue templates or failing to provide any of the information it asks for will be CLOSED. If you choose to ignore the template, you should prove the information it asks for or else your issue will be considered invalid.

Please also read below to see if your issue is on the known issues list.

This is because we've gotten handfuls of issues where we have to fish the information out of the user because they neglected to use the template and then didn't provide anything which was asked for like logs, meaning there was basically nothing we can do but sit and wait. Please do not be that guy. Use the issue template and answer as many questions that apply to your report. Thanks. :)

Also, when the template asks a question, please answer it. The questions are there to be answered, either add your answer below, or replace the italicized text. If the question does not apply to your issue, you can erase it. Leaving them blank just makes it more confusing.

OptiFine, as well as issues caused by it no longer supported. Any issues caused by OptiFine usage will be closed. This is because it makes a lot of inconsiderate and invasive changes to the game that cause issues. If OptiFine classes are present in your crash report, we will assume the issue is caused by OptiFine and close it. Please make sure your issue happens WITHOUT OPTIFINE first.

Please consider trying modern optimization mods like ArchaicFix, Neodymium or FastCraft. Hopefully a shader replacement will happen in the future.

Known wontfix issues are currently:

  • TLauncher, TL Legacy, and any cracked launcher, is not supported as it may or may not break vanilla asset downloading due to overall suspicious/malicious behavior such as erroneously deleting the AssetDirector folder. They tend to mess with game assets in bizarre ways that often break the asset downloader, and supporting these risks a DMCA claim from Mojang Studios.
  • Crucible is unsupported, but is still recommended over Thermos/KCauldron due to being more up to date. This is because it makes various invasive game-breaking changes. It breaks many things in unfixable ways.
  • Mods that have a hardcoded check for the vanilla enchantment table, anvil, beacon or brewing stand do not detect the EFR replacement TEs (example Compatible error with ExtraUtilities‘s Division Sigil #311), solution here is to use the no-replace mode so you can have both vanilla versions and EFR versions of these blocks. A mixin alternative which mixes into the vanilla blocks will likely be added soon.
  • BetterFPS breaks elytras #375: BetterFPS breaks elytra behavior (don't use BetterFPS, or change the trig algorithms)
  • If asset downloads are failing (custom sounds are silent in game and the logs say unknown/empty sound event try checking your NonUpdate configs. EFR needs to be able to run these downloads to function, if you removed the default whitelist, please add minecraft.net and mojang.com back to the allowlist. Please be sure to also use a supported launcher like PolyMC, Prism or vanilla launcher, since other launchers tend to randomly delete assets they deem unused.
Repository owner locked and limited conversation to collaborators Jul 8, 2022
@Roadhog360 Roadhog360 pinned this issue Jul 8, 2022
@GregoriusT GregoriusT unpinned this issue Aug 9, 2023
@Roadhog360 Roadhog360 pinned this issue Sep 10, 2023
@Roadhog360 Roadhog360 changed the title READ BEFORE OPENING AN ISSUE! READ BEFORE OPENING AN ISSUE! (Issues that ignore the template will be CLOSED!) Oct 29, 2023
@Roadhog360 Roadhog360 changed the title READ BEFORE OPENING AN ISSUE! (Issues that ignore the template will be CLOSED!) READ BEFORE OPENING AN ISSUE! (AND USE THE TEMPLATE!!!) Oct 29, 2023
@Roadhog360 Roadhog360 changed the title READ BEFORE OPENING AN ISSUE! (AND USE THE TEMPLATE!!!) **READ BEFORE OPENING AN ISSUE** Dec 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant