Balm (Fabric Edition)

Issues

• Crash on game startup (older version of Forge)

  #2 opened3 years ago by n0proxy
  1

• Crash upon start

  #3 opened3 years ago by efffauw
  1

• Mods for Minecraft 1.17.x require additional changes for compatibility

  #4 opened3 years ago by smmmadden
  1

• Crash on R-clicking on my Antique Atlas

  #5 opened3 years ago by tacogerbil
  0

• Game Disconnecting On Join For "Invalid Player Data"

  #6 opened3 years ago by AfkUserMC
  0

• Balm version 2.3.1 crashes server

  #11 opened3 years ago by royalcw
  1

• Idk how to fix this...

  #12 opened3 years ago by 64thParaDux
  0

• Events are not fired on Forge event bus

  #13 opened3 years ago by BlayTheNinth
  2

• Config does not reload on client when leaving multiplayer

  #7 opened3 years ago by BlayTheNinth
  0

• Config does not reload when changing while on the main menu

  #8 opened3 years ago by BlayTheNinth
  0

• issues on 1.18 forge

  #9 opened3 years ago by itsdinkd
  4

• Crash in mod setup phase

  #10 opened3 years ago by KhanhPham05
  5

• Balm crashes when only mod installed on Forge above v39.0.59

  #14 opened3 years ago by nanonestor
  1

• (Non-fatal) Error message in console

  #15 opened3 years ago by brnbrd
  2

• 1.18.2 Crash

  #17 opened3 years ago by mharbb
  2

• Balm Crash due to Possibly Being Outdated

  #16 opened3 years ago by ENTPRESTIGIOUS
  3

• Port to 1.18.2

  #18 opened3 years ago by kittech0
  0

• Server Error Log

  #19 opened3 years ago by NightSharp
  1

• IndexOutOfBoundsException in logs

  #20 opened2 years ago by spoorn
  1

• balm.mixins.json:ModelLayersAccessor No candidates were found matching ALL_MODELS:Ljava/util/Set;

  #23 opened2 years ago by CebbyS
  1

• 1.19 Request

  #21 opened3 years ago by Avakining
  1

• Replace Cloth Config

  #22 opened2 years ago by BlayTheNinth
  2

• useFluidTank is not implemented in Fabric version, causing CFB sink to not work right

  #25 opened3 years ago by BlayTheNinth
  0

• addFeatureToBiomes does not receive proper tags information

  #24 opened3 years ago by BlayTheNinth
  0

• Updating from v4.2.0 to v4.3.0 causes error

  #26 opened3 years ago by alad-1024
  2