Mention Optifine in Issue reporting section
This commit is contained in:
parent
ef2eace03c
commit
925a14476b
1 changed files with 1 additions and 0 deletions
|
@ -15,6 +15,7 @@ If you don't, we might assume that you are using latest-greatest and waste a bun
|
||||||
a problem that might have fixed been already. Such things makes for very grumpy devs. Grumpy devs spend
|
a problem that might have fixed been already. Such things makes for very grumpy devs. Grumpy devs spend
|
||||||
less time coding and more time doing stuff that makes them less grumpy.
|
less time coding and more time doing stuff that makes them less grumpy.
|
||||||
* If the issues occurs on a server, be sure it's a vanilla forge server and <b>not</b> a mcpc+ server.
|
* If the issues occurs on a server, be sure it's a vanilla forge server and <b>not</b> a mcpc+ server.
|
||||||
|
* Issues with any logs mentioning Optifine will be closed on sight! Remove Optifine before reporting any issue.
|
||||||
|
|
||||||
#### Frequently reported
|
#### Frequently reported
|
||||||
* java.lang.AbstractMethodError - Incompatibility between BC/Forge/Mod using BC API. Usually not a BC issue
|
* java.lang.AbstractMethodError - Incompatibility between BC/Forge/Mod using BC API. Usually not a BC issue
|
||||||
|
|
Loading…
Reference in a new issue