Jump to content

N/A

Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

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

N/A's Achievements

Tree Puncher

Tree Puncher (2/8)

0

Reputation

  1. Ok, thanks for the help!
  2. Good idea. If I did that, would it fix the error?
  3. Sorry, that was outdated from last night. I pushed the most recent commit. Just refresh the page
  4. https://en.wikipedia.org/wiki/Don't_repeat_yourself
  5. Hmmm... Is there a way to break it up into multiple files or methods?
  6. Ok, the github repo is here: https://github.com/SimplyCmd/Terracraft Also, the only log is right here: > Task :compileJava C:\Blablabla\src\main\java\io\github\simplycmd\terracraft\ModEventSubscriber.java:13: error: code too large public static void onRegisterItems(RegistryEvent.Register<Item> event) { // Tells Forge that you want this method to be called when it is time for your mod to register its items. ^ 1 error > Task :compileJava FAILED
  7. I used Google Sheets to pull the item names from the wiki, replace the spaces with underscores, and convert all letters to lowercase. Then I used Sheets to add the register item thing around each one and pasted it into IntelliJ
  8. I am making a mod that adds Terraria into Minecraft. To start, I registered all 3991 items into the game. However, when I try and run the game, the build fails with this error: C:Myfilesandstuff\ModEventSubscriber.java:13: error: code too large public static void onRegisterItems(RegistryEvent.Register<Item> event) { Any idea for a workaround?
  9. I have no significant code to show. I was just trying to set up the workspace and check if it was all working. I should probably try setting up again.
  10. Whenever I try to run the client in Eclipse, the Minecraft tab opens for a split second before closing. I am fairly new to Forge, so I have no experience in locating and eliminating the errors. Crash report
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.