Paint_Ninja

We need more info to be able to help you - please read the FAQ and share links to your crash report and logs

Please share your crash report

This is the Forge forums, we don't usually support Fabric here as it's unrelated. In future, you may have better luck asking for help with Fabric on their support channels instead.

As part of stricter anti-spam measures, new posts that have large amounts of content similar to many other posts are automatically hidden. You'll know this because your entire post will be highlighted in red and only visible to you. Unfortunately, this means dumping crash reports or logs directly in your support thread will trigger it. To avoid this, please read the FAQ before posting and provide a link to your log or crash report on an external paste site (such as pastebin) instead. If your thread is automatically hidden, you'll need to create a new one or wait for a moderator to manually approve it and remove the log from your post. When creating a new thread, make sure you only provide a link to an external paste site and do not dump logs directly in your post again as doing so could risk your account getting banned.

Please edit your post to include links to your debug.log and crash report, as explained in the FAQ. Dumping it directly in the thread makes it hard to read on mobile

To be able to help you, we need a link to your debug.log on pastebin.com, as explained in the FAQ. Please do so in a new thread

We need a link to your debug.log on pastebin to be able to help you, as explained in the FAQ

Please share a link to your log on pastebin.com rather than dumping it in the thread directly, as explained in the FAQ

Please put your logs on pastebin.com and share the link to it rather than dumping it in the thread directly. Follow the instructions in the FAQ for how to do this as well as how to properly update your graphics drivers. Checking for driver updates with device manager or radeon software will fail to find updates when they're in a broken state, so it's important you follow the guide in the FAQ instead.

Please share your installer log. Instructions are in the FAQ

Please don't revive months old posts with unrelated questions. Please read the FAQ before posting.

Please share your crash report as a link to pastebin.com rather than dumping it in the thread directly, as explained in the FAQ

Your issue is caused by broken drivers. While you said you updated them, it sounds like they reverted to the broken state. It's important you follow the guide in the FAQ for updating instead, as it covers how to avoid this scenario and ensure that they stay updated

Please follow the guide for updating your drivers in the FAQ. Checking for updates in device manager or in radeon software won't work properly when you're on a broken driver.

Your crash report is lacking formatting - please try pasting it again

Please share a link to your debug.log on pastebin, as explained in the FAQ

Please put your debug.log and crash report as links to https://pastebin.com - instructions on how to do this are in the FAQ

Please share a link to your server's debug.log on pastebin.com, as explained in the FAQ

Optifine supports 47.1.43 if you use OptiFine HD U I6 pre6

We were recently hit with a significant amount of spam that included inappropriate or illegal content. Here's what happened, what we've done and the changes made to avoid this from happening again... --- Last month we noticed an massive uptick in spam, at one point approaching an alarming rate of multiple new accounts being made every couple of hours on a daily basis, across multiple time zones. This included things such as ads for online casinos, black market pharmaceuticals and sexual solicitations, among other things. In our early response to this, moderators monitored the forums more regularly, banned accounts and removed individual threads as and when they were seen or reported. We initially thought these were bots, but later discovered based on their behaviour that they were commissioned "workers" from a handful of third-world countries. Unfortunately, the spam got increasingly hard to keep up with our current approach. As part of Forge's new transparency efforts, we reached out to Lex about this publicly on the new Discord server, which he promptly responded to once awake (time zone differences) and performed a number of measures, including updating our week-old anti-spam and bot protection plugins, trained us on the spammer flagging feature and increased the sensitivity on restricting suspicious account sign-ups - any stricter and nobody could register. The spammer flagging feature allowed us to ban an account and have all of their posts automatically removed within a matter of minutes without needing to manually remove them. This was a great step in the right direction and significantly reduced the workload for moderators in situations like this. Overtime I worked with Lex to further refine and improve our measures to counter the ever-growing rate of spam on the forums. We quietly rolled out various efforts behind the scenes: promoting more moderators, IP bans, automated keyword blocking that notified moderators, registration blocking for certain email domains and more. Overall, we banned nearly 600 obvious spam accounts and removed tens of thousands of unacceptable threads, excluding automated measures. --- Part of the delay in completely solving this was two-fold - a lack of familiarity with the forum software (due to the scale of this spam attack not being seen here before so as to not warrant a need in the past) and wanting to avoid sudden disproportional actions that could affect real users. I would like to personally apologise on behalf of the team if you were affected by the spam and would like to thank those involved in mitigating it. We have a small but fantastic team on the forums and hope this helps convey our level of care and commitment to the forum community.

Please don't revive a year-old thread. Windows 11 and the MS Store version work flawlessly with MC Java edition and are not the cause of the issue.

Update Forge to 43.3.0+ Newer builds of Forge have improved errors and tell you exactly which jars are duplicates.

Sinytra Connector requires 47.1.3 - you're currently using 47.1.30

The EventBusSubscriber annotation only works for static methods annotated with SubscribeEvent

@Elizabeth Rae This is the Forge forums, we do not support Fabric as it is a completely separate thing. Please do not revive a year-old thread with an unrelated request for help - make a new thread instead.