Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

shadowfacts

Forge Modder
  • Content Count

    588
  • Joined

  • Last visited

Community Reputation

100 Excellent

About shadowfacts

  • Rank
    Dragon Slayer

Converted

  • Gender
    Male
  • URL
    https://shadowfacts.net
  • Personal Text
    Programmer, Forge modder, Capability enthusiast.

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. It's possible for some libraries, but not for CTM as it has its own @Mod class.
  2. You go to minecraft.curseforge.com, create an account, create your project, and then upload the built mod jar.
  3. Show where you registered your event handler.
  4. You'll need to use a custom model and Forge's SimpleModelFontRenderer.
  5. Forge doesn't automatically create a config GUI for you. In your @Mod annotation, you need to provide a value for the guiFactory property. It should be the fully-qualified name of a class that implements IModGuiFactory. In your GUI factory, you'll need to make sure that hasConfigGui returns true and that you've implemented createConfigGui. This is my GUIConfig class which is a small wrapper around FML's GuiConfig class that makes it a bit easier to use.
  6. You need to be connected to the internet for Gradle to download dependencies. Are you sure you're computer's connected to the internet when you run the Gradle task and is there any program (e.g. anti-virus) that could be blocking the connection?
  7. That doesn't work for Forge mods, you need to run the gradlew build command.
  8. You can have ModelRegistryEvent handlers on the server side, because the ModelRegistryEvent class does exist on the server but won't be fired there and nothing else in the method signature uses client only classes, however, it's best practice to keep your client-side code entirely separated from common code so it's harder to accidentally introduce client sided-ness bugs.
  9. In your @SidedProxy annotation, you've specified a fully qualified name for the client proxy that's different than the actual class name.
  10. 1) Wrong section, this should be under Support & Bug Reports. 2) 1.7.10 is no longer supported here.
  11. What client-only methods are you using? How to fix it will depend on which ones you're using.
  12. Don't necro threads, this one is more than a year old.
  13. Bytecode version 52.0 corresponds to Java 8.
  14. Yes... It's your code, you can do whatever you want with it... If the class isn't doing anything, then by all means remove it.
×
×
  • Create New...

Important Information

By using this site, you agree to our Privacy Policy.