Jump to content
View in the app

A better way to browse. Learn more.

Forge Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Leaderboard

Popular Content

Showing content with the highest reputation on 01/01/18 in all areas

  1. I would like to see the solution if you figure it out. I myself don't have such a good experience with NBT, but I would like to see what you ended up doing. Happy New Year to you as well. Here in New York, New Year is in 5 hours!
  2. Heh, well, thanks for your support anyways. If I figure out a solution to what I was looking for I'll post it here. (Btw, happy new year!)
  3. Yeah, I see that's why you used the UUID. I couldn't figure it out myself since I'm not that good at NBTs. Best of luck figuring out the solution!
  4. Enchantments are managed by a Forge registry, so the numeric IDs are automatically assigned per-save and shouldn't be used. Use the registry name in the JSON instead and store the Enchantment instance in the Ingredient for matching.
  5. There was short time after Forge was being upgraded to 1.8 where RenderPlayerEvent was NOT fired (because it was WIP). I am not sure if your version is in scope of said time, but: 1. You can find out in changelog - look for log saying that RenderPlayerEvent was reactivated. 2. You should update to 1.9+. Aside from that - why the hell are you registering same event class for 2 buses? Separate your FML and Forge events in 2 classes - otherwise it's waste of resources (okay, well - micro optimization). Next on plate: As of 1.9 (I think, maybe earlier) FML and Forge buses were merged into one - so basically no matter what you call - its same event bus - thus call it only once. Said that - update to 1.9+ and use one bus for all events (not mentioning decorator ones).

Important Information

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

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.